Blog
BlogAllocate API costs accurately by assigning separate keys to each team and workload.
Concentrate.ai
A shared provider key can tell you which account was billed without telling you which team created the cost. Concentrate gives teams a shared way to buy model inference and inspect spend by organization, team, project, key, model and provider. Useful attribution starts with assigning requests to the right owner.
Separate customer-facing traffic, internal experiments and coding agents into appropriate projects and keys. Assign an owner to each. Avoid distributing one application key across unrelated teams if you need their spending separated later.
For example, support and engineering may both use the same model. Separate keys let you distinguish support-ticket traffic from coding-agent usage without trying to infer ownership from the prompt text. Treat keys as secrets, and rotate any that have been copied into shared files or logs.
Concentrate’s spend tracking groups usage across the owners and model routes behind the calls. Use one date window and currency when comparing totals. Keep input, output and applicable cached-token charges distinct.
For an illustrative workload, suppose the month includes $800 of OpenAI usage and $1,200 of Anthropic usage. The $2,000 total is useful only if the team-level records explain it. If $1,500 belongs to support and $500 to engineering, those are ownership allocations, not separate additional charges.
When buying inference through Concentrate, compare usage with the account statement and credit movements. When bringing your own provider key, the provider bills the tokens under your agreement. Do not count both a usage estimate and the provider invoice as two separate costs.
Also separate prepaid deposits from consumed tokens. A top-up adds balance; it is not evidence that an application spent that amount on the day of payment. Include promotional credits and negotiated rates explicitly when reconciling the final bill.
A spend chart reports usage. An alert tells someone to act. A hard limit blocks requests under a defined rule. Confirm the supported scope and behavior of any limit before promising a team that it cannot overspend.
If your finance process needs allocation by a custom business dimension, such as customer or feature, confirm that the current integration records that dimension. Do not assume a gateway reconstructs missing historical ownership or requires arbitrary metadata fields automatically.
Use Concentrate to move one workload to managed model access, assign its key to an owner and review a full billing period. Standard purchases have no token markup under the published pricing. Expand once engineering and finance can explain the same total from the same request records.
LLM Gateway
Change models, providers, add fallbacks, and more by running all AI usage through one platform.