Migration
Migrate from OpenRouter to Concentrate
OpenRouter charges a 3% service fee on top of the standard credit card processing fee. Concentrate has no service fee and no credit card fees. Keep broad model access, then add spend views, logs, fallbacks, redaction, and team controls.
Pricing
No service or card fees
OpenRouter adds 3% on top of standard card processing. Concentrate charges neither.
Code change
Base URL + key
Keep your SDK, prompts, and parsing in place.
Rollout
By workload
Move low-risk traffic first, then chat and agents.
New capabilities
What your team gains with Concentrate
01
Keep model access
Use one API to reach current models across providers.
02
Add management
Get spend, request logs, API keys, fallbacks, and audit logs.
03
Use volume terms
Move meaningful usage toward pricing based on volume instead of per-token markup.
Migration basics
Frequently asked questions
When should a team migrate from OpenRouter to Concentrate?
Migrate when model access is no longer the only problem. Teams usually move when they need spend by team or key, request logs, provider fallbacks, API keys, redaction, audit logs, and security review in one managed request path.
How does pricing compare to OpenRouter?
OpenRouter charges a 3% service fee on top of the standard credit card processing fee. Concentrate has no service fee and no credit card fees. High-volume usage can move to volume-based terms.
What changes in code during an OpenRouter migration?
Most teams change the base URL, API key, and model route, then test response shape, latency, token counts, and error behavior. Keep app logic, prompts, and parsing in place unless a workload depends on provider-specific behavior.
Should we migrate all traffic at once?
No. Start with a low-risk internal or batch workload, compare outputs and logs, then move higher-risk chat or agent traffic after the fallback and failure paths are tested.