cd /news/ai-infrastructure/ai-gateway-now-supports-private-infe… · home › topics › ai-infrastructure › article
[ARTICLE · art-171265] src=vercel.com ↗ pub= topic=ai-infrastructure verified=true sentiment=↑ positive

AI Gateway now supports Private Inference

Vercel added Private Inference to AI Gateway, letting enterprises connect fine-tuned, self-hosted or prerelease model endpoints so those models run through the same authentication, SDKs, APIs and observability as catalog models. Private models are callable via Chat Completions, Responses or Messages using a `private/<slug>` ID, are scoped to the owning Vercel team and excluded from the public catalog, with encrypted credentials and optional per-provider Zero Data Retention. Teams can register a provider and model through the Private Inference page or Vercel CLI version 65.16.0 or later, and can optionally fall back to a catalog model if a private endpoint fails.

key takeaway

Private models are called with a `private/<slug>` model ID through Chat Completions, Responses or Messages, and registering a provider requires Vercel CLI 65.16.0 or later.

by read1 min views1 publishedNov 16, 2026

Private Inference connects your own model endpoints to AI Gateway. Enterprises running fine-tuned, self-hosted, or prerelease models used to need separate keys, client code, and logs for them. Those models can now run through the same authentication, SDKs and APIs, and observability as catalog models, so every model your team uses is managed in one place.

Use Private Inference to: Switch between private and catalog models: Call private models through Chat Completions, Responses, or Messages. AI Gateway translates each request to your endpoint's format, so switching only changes the model ID.

Keep models scoped to your team: Only your Vercel team can view or call private models, and they aren't listed in the public catalog. Credentials are stored encrypted, and you can enable Zero Data Retention per provider.

Connect coding agents: Use private models in Claude Code, Codex, Cursor, and other coding agents connected to AI Gateway.

Monitor traffic together: View private model requests alongside catalog traffic in logs, trace drains, and custom reporting. Observability charts break down requests, tokens, and time to first token by private model.

Configure fallbacks: Optionally fall back to a catalog model if your private endpoint fails. To get started, open the Private Inference page and add your endpoint as a private provider. Enter its base URL, select its API format, and add its credentials. Then add the models it serves.

You can also register the provider and model with the Vercel CLI, version 65.16.0 or later: Call the model using its private/<slug> ID:

Private model requests appear in [AI Gateway logs](https://vercel.com/docs/ai-gateway/observability-and-spend/logs) alongside requests to catalog models.

type: embedded-entry-inline id: 1GzjEiRrj3NaTriLhtBYIX

Read the Private Inference documentation for supported model types, requirements, and billing details.

── more in #ai-infrastructure 4 stories · sorted by recency
── more on @vercel 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/ai-gateway-now-suppo…] indexed:0 read:1min 2026-11-16 · —