--- title: "Vercel AI Gateway free inference" description: "$5 in credits refresh on a published schedule. See verified limits, model IDs, privacy terms, and primary sources for Vercel AI Gateway." canonical_url: "https://freeinferencing.com/provider/vercel_ai_gateway/" md_url: "https://freeinferencing.com/provider/vercel_ai_gateway.md" last_updated: "2026-09-19" --- # Vercel AI Gateway > $5 in credits refresh on a published schedule. ## Classification - **Directory:** Current - **Free access:** Monthly credits - **Status:** Available now - **Confidence:** High - **Payment card:** No - **Account:** Required - **Equivalent paid value:** $5.00/mo - **API endpoint:** `https://ai-gateway.vercel.sh/v1` ## Models mentioned - `inclusionai/ling-3.0-flash-fin` - `inclusionai/ling-3.0-flash-fin-free` - `inclusionai/ling-3.0-flash-sante` - `inclusionai/ling-3.0-flash-sante-free` - `inclusionai/ling-3.0-flash-vl` - `inclusionai/ling-3.0-flash-vl-free` - `poolside/laguna-s-2.1-free` - `fish-audio/s1` - `fish-audio/s1-free` - `fish-audio/s2-pro` - `fish-audio/s2-pro-free` - `fish-audio/s2.1-pro` - `fish-audio/s2.1-pro-free` - `fish-audio/transcribe-1` - `fish-audio/transcribe-1-free` ## Limits and terms ```yaml recurring_free_credit_usd: 5 recurrence: monthly scope: team starts: On the team's first AI Gateway request. important_transition: After a team purchases credits it moves to paid status and no longer receives the monthly free credit. ``` ## What happens to your prompts? **Partially private.** The gateway deletes content after each request, but upstream retention and non-enterprise protections depend on route controls and provider terms. 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: Vercel AI Gateway; provider-side retention and training depend on routing controls, provider agreements, plan, and BYOK configuration. prompt_retention: Vercel states the gateway layer deletes prompts, outputs, and sensitive data after a request completes. Provider-side retention is separate unless zero-data-retention routing is enabled. response_retention: Same gateway-layer deletion policy as prompts; final providers may apply separate retention. ordinary_logging: Usage, spend, request volume, model, provider, project, token counts, and performance metadata are available for observability; prompt-content logging is not described as part of ordinary gateway telemetry. model_training: A no-prompt-training routing control is available on all plans. Enterprise terms separately warrant that AI Gateway Customer Content is not used to train or improve Vercel AI products; other plans must enforce provider controls. product_improvement: Enterprise AI Gateway content receives an express no-training and no-improvement commitment. Non-enterprise handling depends on AI Product Terms and configured provider-routing controls. human_or_operator_access: The gateway claims immediate content deletion after request completion; the selected provider still processes content under its own terms. subprocessors_and_routing: Requests go to selected third-party AI providers. Team or request-level ZDR routes only to providers covered by negotiated ZDR agreements; BYOK agreements remain the customer's responsibility. deletion_controls: Gateway content is described as deleted after completion. Provider-side ZDR is available per request on Pro and Enterprise or team-wide as a paid control; no-training filtering is available on all plans. caveat: Enabling ZDR or no-training is not the same as the default behavior of every provider route. BYOK credentials are skipped under ZDR unless the customer marks its own contract compliant. agreements: terms_of_service: https://vercel.com/legal/terms privacy_policy: https://vercel.com/legal/privacy-policy ai_product_terms: https://vercel.com/legal/ai-product-terms data_processing_addendum: https://vercel.com/legal/dpa ``` ## Eligibility ```yaml account_required: true payment_method_required: false ``` ## API compatibility and modalities - **Compatibility:** OpenAI Chat Completions, OpenAI Responses, Anthropic And Provider Sdks - **Modalities:** Text generation, Speech / audio ## Before you build with Vercel AI Gateway ### 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, No payment-card status, and the plan-specific sources below. ### Resolve the live model route The snapshot records 15 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 No, 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 **Partially private** because The gateway deletes content after each request, but upstream retention and non-enterprise protections depend on route controls and provider terms. 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 13 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 - [AI Gateway pricing](https://vercel.com/docs/ai-gateway/pricing): Official Pricing - [Models API](https://ai-gateway.vercel.sh/v1/models): Live Catalog - [AI Gateway models](https://vercel.com/ai-gateway/models): Official Catalog - [AI Gateway general availability](https://vercel.com/changelog/ai-gateway-is-now-generally-available): Announcement - [Terms of Service](https://vercel.com/legal/terms): Official Terms - [Privacy Notice](https://vercel.com/legal/privacy-policy): Official Privacy - [AI Product Terms](https://vercel.com/legal/ai-product-terms): Official Terms - [Data Processing Addendum](https://vercel.com/legal/dpa): Official Dpa - [AI Gateway security and data routing](https://vercel.com/i/secure-ai-gateway): Official Docs - [Zero Data Retention and no-prompt-training controls](https://vercel.com/changelog/zero-data-retention-no-prompt-training-on-ai-gateway): Official Changelog - [npm download stats for ai (Vercel AI SDK)](https://www.npmjs.com/package/ai): Package Registry Stats - [2025 Stack Overflow Developer Survey technology section](https://survey.stackoverflow.co/2025/technology): Independent Survey - [Next.js by Vercel](https://nextjs.org/): Official Product ## Sitemap See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.