--- title: "Sail Research free inference" description: "$5 in credits refresh on a published schedule. See verified limits, model IDs, privacy terms, and primary sources for Sail Research." canonical_url: "https://freeinferencing.com/provider/sail_research/" md_url: "https://freeinferencing.com/provider/sail_research.md" last_updated: "2026-09-19" --- # Sail Research > $5 in credits refresh on a published schedule. ## Classification - **Directory:** Current - **Free access:** Monthly credits - **Status:** Available now - **Confidence:** High - **Payment card:** Yes - **Account:** Required - **Equivalent paid value:** $5.00/mo - **API endpoint:** `https://api.sailresearch.com/v1` ## Models mentioned - `Kimi K3` - `GLM 5.3` - `DeepSeek V4 Flash 0731` - `Kimi K2.6` - `GLM 5.3 Flash` - `DeepSeek V4 Pro 0813` - `Gemma 4 31B` - `Gemma 4 12B` - `Gemma 4 31B NVFP4` - `gpt-oss-120b` - `Qwen3.6 35B A3B` - `Nemotron 3 Super 120B A12B` ## Limits and terms ```yaml included_credit_usd_per_month: 5 reset: monthly rate_limits: No strict public limits; service priority depends on completion window. ``` ## What happens to your prompts? **Private.** Sail limits persistent content storage to 48 hours and excludes content from training and service improvement. Privacy is audited separately from price. Review the current governing terms before sending sensitive or regulated data. ## Data governance and agreements ```yaml data_governance: review_status: reviewed plan_scope: Sail Research inference jobs for all customers, including its distributed compute infrastructure and optional customer-owned storage. prompt_retention: Customer Content is persistently stored only in Sail's S3 buckets and automatically deleted shortly after processing, never later than 48 hours. Other processing is transient in memory. response_retention: Outputs are Customer Content under the same maximum 48-hour retention; customer-owned buckets follow customer configuration. ordinary_logging: Job identifiers, timestamps, status, routing, and state metadata are retained as needed to operate and track jobs without prompt content. model_training: Sail says it does not use Customer Content to train, fine-tune, or improve Sail or third-party machine-learning models. product_improvement: Customer Content is excluded from service improvement and marketing; ordinary operational metadata supports routing and job delivery. human_or_operator_access: Sail restricts customer-data access, and compute providers are not permitted to access Customer Content or store it unencrypted. subprocessors_and_routing: Multiple compute providers may execute jobs, while Amazon S3 stores encrypted content. Compute subprocessors are contractually restricted from accessing content. deletion_controls: Sail production buckets enforce a lifecycle policy with a 48-hour maximum; customers can instead use their own S3 bucket and retention policy. caveat: The 48-hour maximum permits longer-than-normal storage for retries, failures, and operational conditions, so this is not immediate zero retention. agreements: terms_of_service: https://www.sailresearch.com/terms privacy_policy: https://www.sailresearch.com/privacy data_processing_agreement: https://docs.sailresearch.com/dpa ``` ## Eligibility ```yaml account_required: true payment_method_required_for_monthly_refresh: true ``` ## API compatibility and modalities - **Compatibility:** OpenAI Responses, OpenAI Chat Completions, Anthropic Messages - **Modalities:** Text generation ## Before you build with Sail Research ### Read the classification narrowly This record describes the bounded offer supported by evidence on 2026-09-19; it does not guarantee permanence, production suitability, uptime, latency, model quality, or access from every account and region. “Monthly credits” should be interpreted together with the Current directory placement, High confidence, Yes payment-card status, and the plan-specific sources below. ### Resolve the live model route The snapshot records 12 model IDs. Match the exact ID against the provider's current catalog before using it in code because zero-price routes, aliases, context limits, and feature support can rotate while an older documentation page remains online. ### Match the quota to the workload shape Translate the allowance into peak requests per minute, input and output tokens, concurrency, retries, and every daily or monthly ceiling that applies to the intended account. The first limit reached by the workload is the practical ceiling. A large token pool can still fail interactive bursts, and a high request limit can still fail long-context work. Include tool calls and retry traffic, test the largest realistic payload, and treat research, experimental, and community access as conditional on their eligibility and fair-use terms. ### Preserve billing and privacy boundaries The recorded payment-card requirement is Yes, and account access is required. Confirm both in the live signup flow, set provider-side budgets when charges are possible, and observe the balance or usage fields after a complete request. The prompt-handling classification is **Private** because Sail limits persistent content storage to 48 hours and excludes content from training and service improvement. Re-read the terms for the exact route and plan before sending sensitive, regulated, or proprietary content. ### Follow the evidence, then re-check it This record links 7 first-party sources covering the offer, catalog, limits, pricing, terms, privacy, or adoption evidence available to the audit. Prefer the newest and most specific governing document or live catalog when sources disagree. A dated finding can become stale even when the page remains online, so retain the source and snapshot that supported the decision and submit a correction when a provider changes a material term. ### Plan fallback without policy drift A fallback should preserve modality, context length, streaming, structured output, tools, safety controls, and data terms, not only API syntax. Decide which errors may retry, cap retry storms, and prevent an exhausted free route from silently switching to a billable model. Rotating aliases and free pools can change behavior without changing the endpoint, so retain the response model field and test at least one substitute route before the primary offer becomes unavailable. ### Monitor the offer as a dependency Capture the model ID, response model, rate-limit headers, usage fields, latency, HTTP status, and provider request identifier. Watch authorization failure, quota exhaustion, catalog removal, policy revision, and balance movement as separate failure modes. Re-check the live catalog and governing sources on a schedule proportionate to the workload's importance, and keep an owner and exit path for any production dependency on volatile free capacity. ### Test one complete request before scaling Start with the smallest permitted request using the exact credential, model ID, endpoint, region, and account type intended for deployment. Record the status, headers, usage fields, response model, latency, and dashboard balance movement. Then exercise an invalid model, quota exhaustion, or rate limit so failure is explicit and cannot silently switch to a paid route. Validate streaming, structured output, and tool calls separately because a free model can expose fewer features than its paid counterpart. Keep a budget ceiling outside the application whenever billing is possible, and do not send sensitive data until the observed route matches the reviewed agreement. ## Primary sources - [Sail Research pricing and API overview](https://www.sailresearch.com/): Official Pricing - [Sail Research documentation](https://docs.sailresearch.com/): Official Docs - [Sail Research Terms](https://www.sailresearch.com/terms): Official Terms - [Sail Research Privacy Policy](https://www.sailresearch.com/privacy): Official Privacy - [Sail Research Data Processing Agreement](https://docs.sailresearch.com/dpa): Official Dpa - [sail PyPI project (Python SDK for the Sail platform, docs.sailresearch.com)](https://pypi.org/project/sail/): Package Registry - [PyPI download stats for sail](https://pypistats.org/api/packages/sail/recent): Package Registry Stats ## Sitemap See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.