Receive the request
Your application sends a compatible request with a CostRouter API Key. The model name, message payload, and client workflow stay close to the SDK patterns you already use.
One Balance. One API Key. Every Connected Model.
CostRouter replaces separate provider subscriptions with cost-aware routing and usage-based billing. Fund one balance, access every connected model through one API key, and pay only for actual usage.
- One top-up
- One API key
- Every connected model
- Pay per use
How to use
Connect your app or coding agent
01
AI app API integration
Use one API for GPT, Claude, Gemini, DeepSeek, and more with transparent usage-based pricing and cost-aware routing.
Apps
Backends
Workflows
One Base URL, existing SDKs, routed models
View guide
02
Start with coding agents
Route Codex, Claude Code, Gemini CLI, Cursor, and custom coding agents through your CostRouter API key.
CodexClaude CodeGemini CLICursor
View guide
How CostRouter Handles Each Request
CostRouter receives a compatible API request, matches available model routes, selects a qualified path by price, latency, and availability, then returns a standard response with usage records.
Match available routes
CostRouter checks the requested model, endpoint capability, account configuration, and live channel status to find routes that can handle the request.
Select the qualified path
Among eligible routes, CostRouter weighs price, latency, and availability, then prioritizes a lower-cost path only when it meets the required reliability conditions.
Return and record
The response is returned in a compatible format, while request status, token usage, and cost are recorded for usage logs, billing review, and later optimization.
Built for Production API Workloads
CostRouter keeps routing, billing, and access rules visible so cost optimization stays auditable and controllable.
Traceable usage and billing
Review request logs, token usage, final charges, refunds, and billing records from the dashboard.
API Key-level controls
Set quotas, expiration, model limits, IP allowlists, and group routing rules for each API Key.
Route quality safeguards
Routing decisions consider cost, latency, and availability, with account controls for advanced routing behavior.
Clear operating limits
Review supported models, live prices, route availability, and regional restrictions before production use.
Frequently Asked Questions
Answers for pricing, compatibility, model routing, partner supply and production use.
Is CostRouter compatible with OpenAI SDKs?
Yes. OpenAI-compatible routes use familiar OpenAI-style request formats. In most cases, you point your existing SDK or HTTP client to the CostRouter base URL and use your CostRouter API Key.
Why can CostRouter be cheaper than official prices?
CostRouter compares qualified routes in real time. When a lower-cost route is available and meets reliability requirements, requests can be sent through that route.
Do I need separate keys for GPT, Claude, Gemini and DeepSeek?
No. A single CostRouter API Key can access multiple supported models. Request formats stay close to the relevant provider style, depending on model capability, account permissions, and route availability.
Can I choose a specific model?
Yes. You can request a specific model by name, or use routing rules that balance price, speed and availability for your workload.
Where can I see all supported models?
Open Models to browse current model availability, provider details, endpoints, groups and pricing information.
Is CostRouter only for developers?
No. It is useful for indie builders, startups, enterprise teams, agent workflows, and route providers that want to publish reliable model capacity.
Can route providers publish their own capacity?
CostRouter is designed so qualified route providers can expose supported models, route availability, pricing, and capacity rules.
Will I need to rewrite my application?
Most SDK or HTTP integrations only need configuration changes: update the base URL and use a CostRouter API Key. More complex workflows can keep existing tools while gradually adopting routing controls.