API, routing, model access, and dashboard updates for LLM Gateway.
Gateway API keys are now stored only as keyed HMAC-SHA-256 fingerprints and provider credentials only as AES-256-GCM ciphertext. Every plaintext read path is gone, so a key's secret is visible exactly once per issuance — at creation or roll.
Read more about Hash-Only API Key Storage →
Provider keys now take a description that follows them through key lists and request drilldowns, the master API returns each key's creator and project by name, and the catalogue picks up Grok 4.6 on AWS Bedrock and Vertex AI plus GLM-5.2 Turbo and an Australian region on SCX.ai.
Read more about Provider Key Descriptions, Grok 4.6 & More →
Every organization now has a fleet-wide budget of concurrent in-flight requests that scales with your trust tier — bounding the long-running streams a per-minute limit can't see. Over-budget requests get a retryable 429, and a momentarily saturated gateway sheds load with a 529 instead of queueing until it degrades.
Read more about Concurrent Request Limits and Overload Protection →
Provider cache writes is now a three-way setting. The new Client-managed mode forwards the cache markers your client sends and never adds any of its own, so one API key can serve a coding agent that manages its own caching alongside traffic that should not pay the cache-write premium.
Read more about Client-Managed Prompt Caching →
Every organization now has transparent per-endpoint rate limits, daily/monthly spend caps, and top-up allowances that scale automatically with account age or lifetime usage — all visible on the new Settings → Limits page. Enterprise organizations have no limits at all.
Read more about Trust Tiers: Limits That Grow With Your Account →
LLM Gateway now speaks the AI SDK's own gateway protocol, so an app built on the Vercel AI Gateway runs here with one line changed. Bare model strings, provider-native web search with citations, and the model picker all keep working.
Read more about Drop-In For The Vercel AI Gateway →
You can now top up your credits balance with crypto. Open the top-up dialog, take the checkout option below the amount, and pick crypto on the Stripe Checkout page — the credits land on your account exactly like a card payment.
Read more about Pay For Credits With Crypto →
Define named, versioned routing flows — conditions, A/B splits, and model targets with provider fallback — and invoke them by putting dynamic/<name> in the model field. Build them visually or in JSON, publish immutable versions, and roll back instantly. Available on the Enterprise plan.
Read more about Dynamic Routes →
Starting Friday, August 7, 2026, the /v1/moderations endpoint is billed at a flat $0.00001 per successful request — no token metering, no per-model rates, and no charge for failed or retried attempts. Because it becomes paid, it also starts requiring a credit balance: top up before August 7 or moderation stops working for organizations with no credits.
Read more about Moderations Pricing From August 7 →
The dashboard's Custom Models page is now a full Models directory: every catalog model plus your organization's custom models in one searchable table, with per-model compliance eligibility so your team sees exactly what they can route to.
Read more about Org Models Directory →
Showing 10 of 98 updates
Load more