Integration
Use the Anthropic SDK with Concentrate
Point the Anthropic SDK or Claude Code at Concentrate with a base URL and key change. Keep Claude, and add fallback routes, spend tracking, logs, redaction, and team controls.
Base URL
Concentrate
Route the Anthropic SDK through one endpoint.
Backup
Azure
Route Claude-family workloads elsewhere when needed.
Security
Redaction
Filter sensitive fields before model calls.
New capabilities
What your team gains with Concentrate
01
Keep the Anthropic client
Set the base URL to Concentrate and use a Concentrate key. Messages requests keep their shape.
02
Add fallbacks
Prepare alternate provider routes for important Claude workloads.
03
Show the trail
Use logs, spend views, redaction, and audit logs for review.
Integration basics
Frequently asked questions
Does the Anthropic SDK work without code changes?
Mostly. Set the base URL to Concentrate and use a Concentrate key. The Messages API shape stays the same, so existing Claude calls keep working.
Can we review Claude spend by team or app?
Yes. Use Universal API keys for each team, app, or environment, then group Claude spend by key, project, model, provider route, and time window.
How do we add fallbacks without changing app code?
Keep the app pointed at one model route and configure the backup path in Concentrate. If the primary route fails or times out, the fallback policy can send traffic to the approved backup route.