Glossary
Model profile: a named, priced route
A model profile is what clients call a model: a public name with a published price. The actual upstream model stays hidden behind the gateway.
Updated
Public name, private upstream
You send the profile name in the model field. The gateway maps it to an upstream model and provider behind the scenes.
Only published profiles are for sale. The upstream identity and supplier cost are not exposed to clients.
Price is a profile property
Each published profile has input, output and cache prices per 1M tokens. The sale price in the catalog is what you pay.
A plan can attach its own price to a profile for a specific key, overriding the catalog price for that key only.
Choosing a profile
Pick by task and budget: a cheap profile for routine work, a stronger one for hard prompts and review.
The catalog at /models lists the published profiles, their descriptions and their current prices.
Published model prices
USD per 1M tokens. The numbers come from the public catalog on every page rebuild — this is the sale price, not an estimate.
| Model | Input | Output | Cache |
|---|---|---|---|
| Claude Opus 5.5 | $2.70 | $8.00 | $0.14 |
| DeepSeek Flash | $0.50 | $2.00 | $0.01 |
| Claude Sonnet 5.5 | $1.33 | $6.67 | $0.07 |
| DeepSeek V4 Pro | $2.20 | $6.60 | $0.07 |
Top-up from $10, balance in USD. 1 USD = 1,000,000 UT. No subscription and no auto-charge.
Questions
Is a profile the same as an upstream model?
No. It is a public route to a model the operator sources upstream. The mapping is not exposed.
Can a profile change price?
Yes, but the price applied to a request is snapshotted in its journal entry; past spend is never rewritten.
How do I list profiles?
Call GET /v1/models with your key, or open /models in the browser.
Do all profiles stream?
Chat and messages streaming is supported where the model allows it. Responses streaming is not available in this version.