One gateway for the models in your catalog
Use one account and one API key across the language and video models published by OTRouter. Switch between stable model IDs without managing provider routes.
OTRouter · Model infrastructure
OTRouter gives your product one dependable path to models, with usage and cost for every request kept in view.
Choose a stable OTRouter model ID, then use one of the language protocols advertised for that model with your Team API key.
Explore the API{
"model": "claude-fable-5",
"input": "Summarize this update for the team.",
"max_output_tokens": 240,
"store": false,
"stream": true
}Model
claude-fable-5
Protocol
Responses
Request ID
x-request-id
Why OTRouter
Bring model access, intelligent routing, billing, and Team controls together behind one dependable gateway.
Use one account and one API key across the language and video models published by OTRouter. Switch between stable model IDs without managing provider routes.
OTRouter selects an eligible, cost-effective endpoint for each request. Eligible text requests can fall back once before any output is committed.
See the public model, measured usage, and amount for every request. Every charge maps to one traceable request.
Compare stable model IDs, protocols, capabilities, and public tariffs for language and video generation in one place.
Use the Responses, Chat Completions or Messages contract only where the selected model advertises it. Unsupported fields fail clearly instead of being silently ignored.
Manage keys and balances per account. Set spending limits, revoke credentials and trace each call and charge.
Review language token rates and video resolution and duration rates before you integrate, then inspect the exact charge after each request.
Claude Fable 5
claude-fable-5
Cached input / M
$1.00
Uncached input / M
$10.00
Output / M
$50.00
A single Request ID connects ownership, model, measured usage and the final charge.
Every request belongs to the Team and API key that initiated it.
One model ID stays unchanged while Router handles execution.
Input, cached input and output tokens stay distinct.
Verifiable usage with a determinable price is settled under the applicable billing rules. If the amount cannot be determined, it remains unknown.
Open Console to choose a model, create an API key and inspect every request.