DocsCost & finance
Cost centers
Book estimated provider spend to the teams and products that caused it, with ordered rules, shared-cost allocation and rule history kept by period.
INFRO is in private early access. Running these examples requires an early-access account, an active trial or subscription entitlement, and your own provider connection. Self-serve purchasing is not generally open. See Early access.
A cost center is a name your finance team charges back to: Product, Research, CC-210. Rules decide which requests belong to which center. Monthly statements total each center. Cost centers are included from the Team plan and are managed in the console by owners, admins and the Finance role.
Rules
Each rule has an order, a match and a destination. A request is booked by the first rule it matches, lowest order first. Anything no rule matches is booked to Unallocated, which is always shown on statements rather than hidden or spread across the other centers.
| Match field | Matches when |
|---|---|
project_id | The request ran under that project. |
api_key_id | It used that gateway key. |
member_id | The key belongs to that member. |
environment | The key's environment had this identifier (production, staging, development, or one your organization added). |
workflow | metadata.workflow equals the value. |
feature | metadata.feature equals the value. |
tag | A promoted tag has that key and value. |
end_user_prefix | metadata.user_id starts with the value. |
Every filled field must agree. Rule values are compared as data and never interpreted, so a value with SQL or pattern characters matches only itself. The console previews a rule before you save it: how many requests and how much estimated cost it would match over the last 30 days on its own, and how much it would book once earlier rules have taken theirs.
Shared costs
A rule can split what it matches instead of booking it to one center:
- Fixed weights — for example 70 / 30 between Product and Research.
- Proportional to direct spend — in the same period, in proportion to what each named center was booked directly. A shared retrieval index used by three teams is the usual case.
Splits are exact in micro-dollars: the parts are rounded by largest remainder, so they always add up to the cost being split. Split lines are labelled allocated on statements, never presented as a team's own usage.
Rules change by period
Editing a rule does not rewrite it. It closes the current version and starts a new one from now. A statement always uses the rules that were in force during its period, so a reorganisation in October does not change what September said. Old versions cannot be edited or deleted.
Reading them with a key
GET /v1/cost-centers returns the centers and their current rules. It needs a key with organization-wide observability access; a key scoped to a project, key or environment is refused with 403 organization_scope_required, because a cost center is an organization document. Writing centers and rules is in the console only for now.