One gateway to every leading model
Skip separate accounts for DeepSeek, GLM, Qwen, and other providers. Use one account and one API key across leading domestic and global models, and switch models without changing your code.
PAI · Model infrastructure
PAI Router gives your product one dependable path to models, with usage and cost for every request kept in view.
The model infrastructure layer for stable access, usage and charges.
Available
The Agent work platform for planning, running and continuing meaningful work.
Coming soon
Use Responses, Chat Completions or Messages with the same PAI model IDs and Team API key.
Explore the API{
"model": "claude-fable-5",
"input": "Summarize this update for the team.",
"max_output_tokens": 240,
"stream": true
}Model
claude-fable-5
Protocol
Responses
Request ID
x-request-id
Why PAI
Bring model access, intelligent routing, billing, and Team controls together behind one dependable gateway.
Skip separate accounts for DeepSeek, GLM, Qwen, and other providers. Use one account and one API key across leading domestic and global models, and switch models without changing your code.
PAI automatically selects a capable, cost-effective provider. If one service fails, traffic moves to another available route so your product stays online.
See the model, token usage, and cost for every request, itemized and fully traceable. Every charge maps to a specific request.
Top up directly with cryptocurrency—no overseas credit card required, removing the friction from cross-border access.
Works with the OpenAI and Anthropic protocols and official SDKs. Change one Base URL and keep the rest of your existing code.
Manage keys and credits independently for each Team. Set key limits, revoke access at any time, and see exactly who used what.
Review official model token 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.
A request with measured usage produces one precise charge.
Open Console to choose a model, create an API key and inspect every request.