Every term in this hub.
This hub collects the cost terms in the Prefactor glossary. The budgets group is the control surface: token budgets, quotas, and rate limits are the mechanisms that turn a soft intention into a hard stop before a runaway loop turns into a runaway invoice. If you are putting cost controls on an agent for the first time, start there.
The metering group answers the question budgets cannot: where did the money actually go? Cost attribution, cost per task, and usage tracking tie every unit of spend back to the agent, team, or workflow that incurred it. The economics group zooms out to the business layer: unit economics, total cost of ownership, and inference cost, the terms that decide whether an agent deployment survives its first budget review.
One honest note: cost vocabulary overlaps with observability more than teams expect, because attribution is only as good as the telemetry underneath it. An agent you cannot trace is an agent you cannot bill correctly. Where a term leans on tracing concepts, its related-terms list points across.
Terms are grouped below from controls to accounting: budgets and limits first, then metering and attribution, then pricing and economics, then the alerting layer that keeps surprises small. Each entry links to its full definition.
Budgets & limits
Metering & attribution
Pricing & economics
Controls & alerts
More ai agent cost & token terms
Common questions.
What drives AI agent cost?
Tokens on every model call, fees on every API invocation, and compute on every retry. Token usage is typically the largest driver, which is why budgets and per-task metering are the first controls teams add.
What is cost attribution for AI agents?
Tying every unit of spend back to the specific agent, team, user, or task that incurred it, so monthly bills decompose into per-decision costs.