What is AI Token Economics

A token is a chunk of text the model reads or writes. You pay per chunk. Different models cost different amounts. Input, output, and sometimes tools all meter differently. OpenAI and Anthropic publish those ladders. Finance still cannot run the business on “12 million tokens of vendor A’s flagship.”

AI token economics is treating that usage like a real budget: measuring, allocating, controlling, and attributing spend so operators can quote before a run, cap during it, and attribute after it — instead of a slide that says “unlimited AI.”

Without it, organisations either freeze (no production AI) or send every small task to the most expensive model until the bill becomes a board slide.

The unit problem is the same one cloud had in its first decade: a metered resource sold with a headcount story. Seat licences predict people. Inference predicts work. When those two are collapsed into “unlimited,” the next chunk feels free, so people pick the flagship every time. The ladder did not disappear. It hid.

Words you’ll hear

• Token. A piece of text the model processes. Not a business unit. At work, a long wiki dump and a short field extract are wildly different token counts for the same “question.”
• Seat licence. Predictable cost per person. Often marketed as “unlimited.” The underlying work is still metered.
• Pass-through API bill. Each team has keys. Simple. Invites key sprawl and shadow AI on personal keys. At work, the invoice lands in engineering while go-to-market did the looping.
• Quote. A number before they run. At work, this is what makes a brief a decision rather than a surprise.
• Cap / ceiling. A hard stop. The loop cannot spend past it. At work, weekend agent loops die here instead of in next month’s cloud bill.
• Pool. Organisation-level allowance. At work, one department should not be able to burn the company pool on a vanity run.
• Attribution. Chargeback by job, not “the AI bill.” At work, finance can ask which workstream consumed the units.
• NTU (Nimbus Token Unit). Nimbus’s normalised work credit for completed AI activity — analysis, tools, runs, writes — sitting above raw provider tokens. Everyday questions can be included; heavier work consumes pool credits. Finance gets one tape measure across vendors and steps.
• Model routing. Cheaper model for simple steps, stronger only when needed. See What is model routing. At work, classify-this-ticket should not pay flagship rates.
• Context window. How much text the model can see at once. Dumping the whole Drive into context is an economic choice, not a quality strategy.
• Stop condition. Budget hit, empty result, human cancel. Agent loops can dominate the bill without improving the artefact. See What is an agentic workflow.

The point is value per unit, not minimum units regardless of outcome. Caching, wiki citations, and memory should make the same outcome cheaper over time. If unit cost of an approved update never falls, you are re-deriving folklore every run.

Why you should care

It affects you if you:

• Own the budget. Surprise invoices arrive after agents looped all weekend.
• Run the work. You should see a number before you commit, not a lecture after.
• Are tempted to shame people for using AI. Shame drives personal keys. Cap the official path so it is safe to use.

Practical rhythm:

• Name the run. Unnamed chats cannot be attributed. That is what a workstream is for.
• Separate exploration from production. Sandboxes can have tighter caps and cheaper default routes.
• Review unit cost of outcomes — approved updates per unit — not tokens in the abstract.

Anti-pattern: a single corporate API key in a wiki, no per-job cap, monthly surprise. That is an unmetered utility.

What changes by role

Finance. You need a quote, a ceiling, and a chargeback dimension that matches how the business already thinks — by job, department, or cost centre — not by vendor token type. Multi-vendor ladders are incomparable until you normalise. NTU is that normalisation in Nimbus. Finance should also see stops: a cap that fired is a successful control, not a failed project.

Legal. Spend logs are not only money. They are a map of which data classes went to which provider. Uncapped personal keys are a processing-agreement gap. Legal will also ask whether you can stop a run, not only whether you can pay for it.

Operations. Caps are operational stops, like a queue limit. Ops needs to know whether a paused run is waiting on a person or waiting on budget. Mixing those two in one “it failed” status is how you get the wrong pager.

Go-to-market. GTM feels the quality-versus-cost trade first. A compact model that extracts fields is usually enough. A flagship model that argues a clause may be worth it. Without routing and quotes, GTM either hoards “the best model” or gets blamed for the bill. Neither produces better pipeline hygiene.

Security. API keys are credentials. Personal keys in browser plugins are shadow AI. A pooled official path with per-workstream ceilings reduces key sprawl. Spend spikes can also be an anomaly signal — a loop that never stops is sometimes a bug, sometimes a prompt-injection success.

What people get wrong

“Unlimited” as a strategy. Seats hide the ladder. They do not delete it. Heavy agentic work will still surface as a true-up, a throttle, or a degraded model.

Punishing usage. Chargeback without a sanctioned path recreates personal keys. Celebrate lower units per artefact as playbooks and memory compound.

Tokens as the KPI. Tokens measure consumption. Outcomes measure value. A cheap run that produces a rejected write is still waste. A dearer run that produces one approved journal may be fine.

One model for everything. That is a routing failure dressed as quality culture. See What is model routing.

No stop on loops. Anthropic’s note on building effective agents treats workflows with stop conditions as the grown-up shape. Economics is one of those stops.

Good looks like: named jobs, quotes before commit, hard ceilings, routing policy, attribution, and falling unit cost as the wiki and lifecycle graph reduce re-derivation. Failure looks like a shared key, a flagship default, and a board slide titled “AI spend.”

How this shows up in Nimbus

Workstreams show quotes and ceilings before runs. Orgs draw from a pooled NTU allowance. Routing is a policy, not a dropdown labelled “best.” Memory and wiki reduce re-derivation, which is how unit cost of an outcome should fall over time.

Everyday questions can sit inside the allowance; heavier analysis, tools, and writes consume pool credits. The Lifecycle Graph can record spend as part of the chain, so “the run stopped because the ceiling was hit” is a causal fact.

See Models and What is model routing. Product context: Workstreams.

Questions people actually ask

Why can’t we just pay seats and call it unlimited?

Seats predict headcount. Production AI spend is inference, tools, and writes. “Unlimited” hides the ladder; it does not delete it.

What should finance actually see?

A quote before commit, a cap during the run, and attribution by job afterwards — in one unit they can compare across vendors and steps.

Won’t cheaper models get worse answers?

For extract and classify, often no. For hard judgment, often yes. That is a routing policy, not a religion. Measure reject rates on the job, not vibes.

Do we punish teams for using AI?

No. Punishing usage revives shadow AI. Celebrate lower units per artefact as playbooks and memory compound.

What is an NTU in plain language?

A normalised work credit above raw provider tokens, so a finance partner is not asked to compare “vendor A input tokens” with “vendor B output tokens” plus tool calls. In Nimbus, completed activity — analysis, tools, runs, writes — is what consumes the unit.

Should every chat be billed to a cost centre?

Named production jobs, yes. Tiny sanctioned copilots for personal drafting can live on a lighter path. The failure is mixing them so neither can be capped.

How do agent loops blow the budget?

They call tools, re-read context, and retry without a finish line. Without a ceiling and a stop condition, “being thorough” is an unbounded loop. See What is an agentic workflow.

Is caching the same as token economics?

Caching is a tactic. Economics is the management system: quote, cap, attribute, route. Caching without attribution still leaves you unable to explain the bill.

Do we need a data warehouse to do this?

You need events at run time. A warehouse can hold copies for reporting. It cannot quote a run that has not emitted a number yet.

How does this relate to write-back?

Writes are usually a small number of tokens and a large operational risk. Do not use spend as a substitute for a named signer. Do use spend as a stop so a looping agent cannot keep proposing writes all weekend. See What is write-back governance.

Can we lock one vendor to simplify pricing?

You can. You will pay for it in price, outages, and lock-in. A normalised unit plus routing is how finance keeps a second tape measure. See What is model routing.

Why not just set a monthly company cap?

A company cap without per-job attribution is a shared kitchen. The loudest workflow starves the others, and nobody can say which job did it.

Related reading

What is model routing and What is an AI workstream.

Sources

• OpenAI API pricing
• Anthropic pricing
• Anthropic, Building effective agents