Pricing pages that hide the price
You should not need a spreadsheet and three tabs to know what a call will cost.
Model catalog
Filter the catalog by capability, sort by price, and see exactly what a model costs per token before you send it a single prompt. Switching is one field in your request.
per-token pricing per model
chat, code, vision, reasoning and more
change model_id, keep your code
The problem
You should not need a spreadsheet and three tabs to know what a call will cost.
A better or cheaper model ships and switching means a rewrite.
Capabilities are buried in docs, so you find out by trial and error.
Capabilities
See which models handle chat, code, vision, reasoning and the other capabilities in the catalog.
Compare input and output token prices side by side.
Pin a model with model_id, or ask for a capability and let the router choose the lowest-priced fit.
Choose an account default in settings, or leave it unset and let the router decide per request.
When a routed request's first choice is busy, another eligible model picks it up.
Every catalog model is one click away in the playground.
Use cases
Move routine traffic to lower-priced models without code changes.
Run the same prompt against several models in the playground.
Add vision or code features by changing the capability you request.
Lock a sensitive workflow to one named model.
How it works
Filter by capability and sort by price in the console.
Compare outputs, tokens, latency and price.
Name a model_id, set a default, or route by capability.
Control
API keys are shown once at creation and stored only as a hash. Revoke any key instantly from Settings.
Every request carries its own receipt: tokens in, tokens out, latency and price. Nothing is billed that you cannot trace.
Per-account rate limits and a free monthly allowance keep experiments safe before they become production.
You choose exactly what you send. Repeat prompts can be served from your cache, and cache hits are never billed.
For developers
Send a prompt and a capability, or name a model. One bearer key, one small JSON body, and a full receipt on every response.
curl https://YOUR-DOMAIN/api/ainf/inference \
-H "Authorization: Bearer $AI_INFERENCE_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: order-1042" \
-d '{"prompt":"Summarise this ticket in one line","capability":"chat"}'The catalog lists per-token input and output prices for every model, and each response reports its exact price.
Yes. Change the model_id or capability in your request. The endpoint and response shape stay the same.
Your account default is used if you set one. Otherwise the router picks the lowest-priced enabled model with the requested capability, which is chat if you do not specify.
A model can be disabled in the catalog. Routed requests simply use another eligible model; a request naming a disabled model returns a clear error.
Browse the catalog, compare prices, and try any model free.