Use case
How to allocate AI cost to teams or cost centres
Finance wants AI spend broken out by cost centre like every other line. That needs a label on each call.
Send x-spendline-tags with a cost-centre key (cost_center, costCenter, department or team) on routed calls. Spend then rolls up by that dimension the same way it rolls up by customer.
How it works
Tags work alongside customer attribution: one call can carry both x-customer-id and a cost-centre tag, so the same ledger entry answers "which customer" and "which internal team".
x-customer-id: cust_4f21a
x-spendline-tags: {"cost_center":"support","env":"prod"}What to know before relying on it
Tags supply allocation inputs; they do not decide the accounting. Which P&L line a cost centre maps to, and whether that treatment is acceptable, is your finance team's policy and your auditor's question.
Why it matters
AI spend that arrives as one line on a card statement cannot be charged back to the budget that owns it. A label at the point of the call makes the split possible.
Frequently asked questions
What are the accepted tag keys?
cost_center, costCenter, department or team in x-spendline-tags. Use whichever matches how your finance system names the dimension.
Can a call be allocated to more than one dimension?
Yes. Customer attribution and cost-centre tagging are independent and can both be on the same call.
See what this would look like in your product.
Start with a guided 30-day free pilot on live production traffic. The 30 days start when your traffic flows through Spendline, not at sign-up. We agree the scope, success criteria and paid terms before you start. There is no Spendline subscription fee during the pilot; your model-provider charges still apply.
Prefer email? fida@spendline.ai