Migration
Migrate from Merge Gateway to Concentrate
Keep one API in front of your providers, and access all models through Concentrate with spend views, request logs, fallbacks, redaction, and team controls.
Code change
Base URL + key
Keep your SDK, prompts, and parsing in place.
Rollout
By workload
Move low-risk traffic first, then the rest.
Testing
Compare first
Check output, latency, tokens, and fallback paths before cutover.
New capabilities
What your team gains with Concentrate
01
Keep one API
Reach current models across providers through one endpoint.
02
Add management
Get spend, request logs, API keys, and fallbacks.
03
Keep review ready
Use redaction, SSO, RBAC, and audit logs.
Migration basics
Frequently asked questions
When should a team move from Merge Gateway to Concentrate?
Move when model access is no longer the only need. Teams usually switch when they want spend by team or key, request logs, provider fallbacks, API keys, redaction, and audit logs in one managed request path.
What changes in code during the migration?
Most teams change the base URL, API key, and model route, then check response shape, latency, token counts, and error behavior. App logic and prompts usually stay in place.
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 paths are tested.