--- title: "OpenCode Zen free inference" description: "A limited-duration free promotion with no permanence guarantee." canonical_url: "https://freeinferencing.com/provider/opencode_zen/" md_url: "https://freeinferencing.com/provider/opencode_zen.md" last_updated: "2026-09-19" --- # OpenCode Zen > A limited-duration free promotion with no permanence guarantee. ## Classification - **Directory:** Current - **Free access:** Limited promotion - **Status:** Limited promotion - **Confidence:** Medium High - **Payment card:** Unknown - **Account:** Not documented - **Equivalent paid value:** Not quantifiable - **API endpoint:** `https://opencode.ai/zen/v1` ## Models mentioned - `big-pickle` - `mimo-v2.5-free` - `ling-3.0-flash-fin-free` - `nemotron-3-ultra-free` - `nemotron-3.5-lightning-free` - `muse-spark-1.3-contributor-free` - `jev-1.13-free` ## Limits and terms ```yaml published_numeric_limits: false duration: Limited-time free models with no common public expiration stated. ``` ## What happens to your prompts? **Not private.** Named free routes may collect prompts and completions for model improvement or training, with route-specific retention. 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: OpenCode Zen gateway; data handling varies by selected model and upstream provider. prompt_retention: Most listed providers are described as zero retention, but OpenAI and Anthropic routes retain requests for 30 days and named free routes have separate collection terms. response_retention: Follows the selected upstream route's policy. ordinary_logging: OpenCode's public Zen documentation does not provide one universal metadata-retention period for every route. model_training: Most routes are described as no-training, with explicit exceptions for free models whose prompts and completions may be collected for model improvement or training. product_improvement: Named free routes may exchange discounted or free access for improvement use; NVIDIA trial routes log data for security and product or service improvement. human_or_operator_access: Depends on the selected upstream provider and route; the gateway documentation does not establish universal operator-blind processing. subprocessors_and_routing: Requests are routed to model providers. Their data policies and any model-specific trial terms apply in addition to OpenCode's terms. deletion_controls: Not documented as a single gateway-wide control for upstream retention; users can disable data-collecting models in team workspaces. caveat: Privacy is model-specific and can change with the live catalog. Free routes are among the explicit exceptions to the default zero-retention and no-training description. agreements: terms_of_service: https://opencode.ai/legal/terms-of-service privacy_policy: https://opencode.ai/legal/privacy-policy ``` ## Eligibility No structured eligibility block was recorded. ## API compatibility and modalities - **Compatibility:** OpenAI Chat Completions - **Modalities:** Text generation ## Before you build with OpenCode Zen ### 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. “Limited promotion” should be interpreted together with the Current directory placement, Medium High confidence, Unknown payment-card status, and the plan-specific sources below. ### Resolve the live model route The snapshot records 7 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 Unknown, and account access is not documented. 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 **Not private** because Named free routes may collect prompts and completions for model improvement or training, with route-specific retention. 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 8 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 - [Zen documentation](https://opencode.ai/docs/zen): Official Docs - [Zen models API](https://opencode.ai/zen/v1/models): Live Catalog - [Terms of Service](https://opencode.ai/legal/terms-of-service): Official Terms - [Privacy Policy](https://opencode.ai/legal/privacy-policy): Official Privacy - [OpenCode Zen privacy disclosures](https://opencode.ai/docs/zen/): Official Docs - [OpenCode home page citing 16M monthly developers and 195K GitHub stars](https://opencode.ai/): Official Product - [npm download stats for opencode-ai](https://www.npmjs.com/package/opencode-ai): Package Registry Stats - [OpenCode primary repository](https://github.com/anomalyco/opencode): Official Repository ## Sitemap See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.