Integration
Use Claude Code with model access and spend tracking
Connect Claude Code through Concentrate to manage coding-agent spend, model choices, keys, and logs.
Agent
Claude Code
Traffic grouped under one Universal API key.
Owner
Engineering
Team-level spend attribution.
Logs
Request-level
Debug status, latency, and model usage.
New capabilities
What your team gains with Concentrate
01
Track agent spend
See Claude Code usage by team, key, model, and provider.
02
Keep access scoped
Issue a dedicated Universal API key for coding agents.
03
Switch model routes
Use the model route that fits the coding workflow.
Integration basics
Frequently asked questions
Can finance see Claude Code spend separately from app traffic?
Yes. Give Claude Code its own Universal API key or project key. Concentrate can then separate coding-agent spend from product traffic by key, team, model, provider, and time window.
Can we use Claude Code without handing separate provider accounts to every engineer?
Yes. Use a Concentrate Universal API key for Claude Code and keep provider secrets out of your environment entirely — engineers reach every model through Concentrate. The team gets model access while access, spend limits, and logs stay in one place.
What should we monitor for coding-agent usage?
Track model, provider route, token count, latency, status, user or team key, and daily spend. Coding agents can create large bursts of token usage, so separate keys and limits make reviews easier.