
Time to first token, against other providers of the same model.













The models consumer apps run on, optimized from weights to kernels.












Time to first token, against other providers of the same model.

Median time to first token, at the same eval scores.

Of more than 20 million requests.



03 Make it yoursYour weights, fine-tuned on your traffic, on capacity reserved for you.
Low time to first token on every turn.
// a companion reply, one short sentence
{"messages": [
{"role": "system", "content": "You are a warm companion. Reply in one short sentence."},
{"role": "user", "content": "Long day. I finally finished the report my boss kept pushing back."}]}{"content": "I'm so proud of you for getting that done; now it's time to truly relax!"}Gemma 4 31B's time to first token is up to 3.3× faster than the median provider's.
2.8× faster median time to first token at production load, 943 to 336 ms after one week of optimization, at the same eval scores.
Nearly 40% lower input price than the median provider. Up to 90% cache hits on repeated prompts.
Text, image and audio in, with 1M tokens of context. Cached input at $0.0036 per 1M tokens.
Cached input at $0.006 per 1M tokens, 96% below its $0.16 input price.
Inworld fastest other provider of the same model median other provider
Set the service tier per request, API key or workspace. It sets the latency target and the price.
"service_tier": "flex"The lowest price, for work that can wait. A call that cannot start fails fast, unbilled.
"service_tier": "default"Our standard serving: a published speed range per model and no rate limits.
"service_tier": "priority"Priority scheduling, an uptime commitment and a latency target for your busiest hour.
"service_tier": "fast"Realtime decoding and our tightest latency target.
Words that flash arrived together in one decoding step.
Realtime decoding drafts several tokens ahead and the full model verifies them in one pass.
We rewrote the attention in that verify pass. It has run on our Gemma 4 26B serving since 1 Oct, so the saving reaches every reply.
A draft trained on your own requests predicts your users' replies better, so more drafted tokens are accepted in each verify pass and replies stream faster.
The full model verifies every drafted token, so Fast returns exactly the tokens Default would.
Start with five minutes of brisk walking to warm up.
Same tokens in bothWe host your weights, fine-tune on your requests and optimize decoding and kernels for them.
Reserved capacity and your own model ID, with no queueing behind other customers.
Upload weights or point us at a repo. Same engine, same API.
Fine-tune open models on your production conversations.
Draft models trained on your requests.
When a stock engine is the limit, we write the attention kernel, KV-cache router or serving backend.
US, Europe, India or Asia Pacific, with zero data retention on the models we host.
Every week, a model we serve gets faster or cheaper.
One patched attention kernel, about four times the tokens a second at full load.
One fix in our KV-cache router nearly doubled cache hits on repeated prefixes.
Peaks 35% busier on about a fifth less capacity, with a faster time to first token.
Median time to first token 2.8× faster at production load (943 to 336 ms), each token after it 2.4× faster.
A rewritten verify step, up to 7.5 times faster on the global layers, so Gemma 4 26B replies arrive several tokens at a time.
The full realtime decoding build: median time to first token 154 to 117 ms and each token after it 6.4 to 5.2 ms, at the same eval scores.
The same build in production: median time to first token 1.3× faster, while traffic rose 26%.
Every model on this page runs on a fleet we operate, so a patch reaches production traffic in days.
Inference built for people runs on Inworld. Who are you building for?
Inworld Inference is the LLM inference API from Inworld AI, serving the open models consumer apps run on a fleet we operate. We optimize each model from the weights to the kernels on real traffic, so the models we serve keep getting faster or less expensive. The fleet serves tens of trillions of tokens a month, in four regions: the US, Europe, India and Asia Pacific.
Inworld AI's Inference API serves open models on our own fleet, including Gemma 4, GLM 5.3 Flash, MiMo 2.6 Pro, DeepSeek V4.1 Flash and the Clef decision model. Open models start from $0.07 per million input tokens and $0.34 per million output tokens, for Gemma 4 26B. You can also bring your own weights and run them on a dedicated deployment.
Yes, Inworld AI's LLM inference API is compatible with the OpenAI API. Send Chat Completions requests to https://api.inworld.ai/v1/chat/completions, or set the OpenAI SDK's base URL to https://api.inworld.ai/v1, with your Inworld API key. Name the model by its ID, such as deepseek-v4.1-flash, and the rest of your code stays the same.
Fast mode on Inworld AI's Inference API runs a model with realtime decoding for lower latency, and it is available on request today. Once it is on for your account, send "service_tier": "fast" in the request. Realtime decoding drafts several tokens ahead and has the full model verify them in one pass, and the model you call stays the same.
Inworld AI's Inference API is built for low time to first token, and we optimize each open model on real traffic to keep it low. On Gemma 4 31B, median time to first token fell from 943 ms to 336 ms, 2.8× faster (64% lower), with the same eval scores. Fast mode, available on request, adds realtime decoding on top.
Yes, Inworld AI's Inference API uses cache-aware routing, which sends a repeated prompt to a server that already holds it, and reached up to 90% cache hits on repeated prompts on Gemma 4 26B. Cached input tokens cost less than fresh ones, up to 99% less on MiMo 2.6 Pro, at $0.0036 against $0.425 per million. Chat apps resend the system prompt and the conversation so far on every turn, which is why prompts repeat.
Yes, you can run your own model on Inworld AI's Inference API, on a dedicated deployment with capacity reserved for your traffic and your own model ID. We host your weights, fine-tune on your requests, and optimize decoding and kernels for them. Dedicated deployments run in the US, Europe, India or Asia Pacific, with zero data retention available on the models we host.
Over 30 days, 99.999% of more than 20 million GLM 5.3 Flash requests on Inworld AI's Inference API succeeded, counting server errors, timeouts and capacity rejections as failures. Requests run on a fleet we operate in four regions, the US, Europe, India and Asia Pacific, so a fix we make reaches your traffic in days.