What you are billed for

How a unit of usage becomes a line on your invoice

The seven meters

Billing at Future AGI is usage-based. A meter is a dimension of usage Future AGI counts for you over a billing period, and there are seven of them:

Storage, measured in GB. Everything you keep: trace and observation payloads, voice recordings, and knowledge base documents
AI credits, the managed AI work you trigger. Evaluations, Protect checks, synthetic data generation, auto annotation, prompt creation and improvement, Falcon AI chat, and gateway traffic. Some actions cost a flat 1 credit; an evaluation run costs credits in proportion to the model work it does, with a floor of 1 credit
Gateway requests, one unit per request through the Agent Command Center gateway
Gateway cache hits, a gateway response served from cache, priced well below a full request
Text simulation tokens, the tokens consumed by text Simulation runs
Voice simulation minutes, the call duration on voice simulation runs
Tracing events, the spans ingested into Observe

There is no eighth meter hiding behind a feature, though a single gateway call can land on two: the request itself on gateway requests, and the AI work behind it on AI credits.

Your free allowance

Each meter carries a free allowance. Usage inside the allowance costs nothing, and only what you spend above it can ever reach a rate.

Meter	Included each period
Storage	50 GB
AI credits	2,000 credits
Gateway requests	100,000 requests
Gateway cache hits	100,000 hits
Text simulation tokens	1,000,000 tokens
Voice simulation minutes	60 minutes
Tracing events	50,000 events

The allowance is the same on every plan. Paying more does not buy you a bigger one. It resets with each billing period and it does not roll over, so an unused 40 GB this month is gone next month rather than added on top.

What the allowance means when you hit it does depend on the plan. On Free it’s a hard cap: once a meter’s allowance is spent, calls on that meter are refused. On every paid plan it’s a soft cap: usage keeps running and the excess is billed.

How a tier is charged

Above the allowance, each meter is priced on a ladder of bands, and the ladder is graduated. Each band is charged at its own rate, so crossing a boundary reprices only the units above it and never the ones below. Moving into a cheaper band cannot make your earlier units more expensive, and moving into a new band cannot retroactively raise the price of what you already used.

Storage is the easiest one to see it on. Say you keep 600 GB in a month. The first 50 GB are free. The next 450 GB fall in the $2.00 band, which is $900.00. The remaining 100 GB fall in the $1.50 band, which is $150.00. The month comes to $1,050.00, not 600 GB priced at a single rate.

The ladders are the same on every plan, so the only thing a plan changes about price is the platform fee. Full ladders for all seven meters, plus a calculator, live on Plans & pricing.

What a plan changes

Platform fee, the fixed amount your plan costs per period before any usage
Entitlement limits, how many monitors, alerts, annotation queues, shadow experiments and automation rules you can have, the concurrency you can run at, and how many gateway email alerts and gateway webhooks you can configure
Rate limits, the API requests per minute and ingestion events per minute you’re allowed to sustain
Retention, how long traces, gateway logs, evaluation results and simulation recordings are kept before they’re removed

A plan does not change the free allowance and it does not change the per-unit rate. Limits take effect the moment the plan changes, in both directions. The numbers behind each of these live on Plans & pricing.

What lands on an invoice

An invoice covers one billing period and is built out of line items, so you can see exactly which part of the bill came from where.

The platform fee for your plan
One usage line per meter that went past its allowance, with the tier breakdown behind it
Any credit applied
Any discount
Any one-off charge

Two things about the timing surprise people:

The invoice for a period carries that period’s platform fee in advance together with the previous period’s usage in arrears, so the fee and the usage on one invoice are not from the same month
If a plan started part way through a month, the platform fee line is prorated and says so on the line itself

Whatever the credits and discounts add up to, the total is never negative.

Two things called credits

Note

The word “credit” does double duty in billing, and the two meanings are unrelated.

AI credits are a meter. You consume them by running evaluations, Protect checks, Falcon AI chat and the rest, and they’re billed above the free allowance
Credit balances are money off an invoice. Future AGI staff grant them, they can carry an expiry, and they apply automatically before your card is charged, in type order (startup, referral, goodwill, prepaid) and oldest first within each type, skipping any that have expired. They are not self-serve

When usage stops

On Free, once a meter’s allowance is spent, calls on that meter are refused and the response points you at upgrading to Pay-as-you-go. Other meters keep working until they hit their own allowance, so a Free organization can be blocked on storage while tracing still flows.

A budget set to pause blocks further usage on the meter it is scoped to as soon as its threshold is crossed. It stays blocked until the next billing period or until you change the budget.

A failed payment does not block usage right away. See If a payment fails for what happens and when.

Mental model

flowchart TD
accTitle: How a unit of usage becomes an amount charged
accDescr: A usage event lands on one of the seven meters. Each meter has a free allowance. Usage within the allowance is free and usage above it is priced on the tier ladder, giving a usage cost. The plan contributes a platform fee. Usage cost and platform fee together form the invoice, credit balances reduce it, and what remains is the amount charged.
EVENT["A unit of usage"] --> METER["One of the seven meters"]
METER --> ALLOW["Free allowance for that meter"]
ALLOW -->|"within allowance"| FREE["No charge"]
ALLOW -->|"above allowance"| LADDER["Tier ladder for that meter"]
LADDER --> USAGE["Usage cost"]
PLAN["Your plan"] --> FEE["Platform fee"]
USAGE --> INVOICE["Invoice"]
FEE --> INVOICE
CREDITS["Credit balances"] --> INVOICE
INVOICE --> CHARGED["Amount charged"]

Why it matters

Usage-based billing means the bill follows your traffic rather than a seat count, so it moves when your agents move. The useful habit is watching which meters climb fastest for your workload, because it’s rarely all seven, and putting a budget on the one that could run away while you’re not looking.

Questions & Discussion