AI agent subscription billing: recurring on a metered core.
A subscription is the right model when your agent is a standing dependency in someone's workflow — recurring access or a usage allotment for a predictable fee, on both sides. The trap is running the subscription engine as its own island, disconnected from how usage is actually measured. a2a cloud puts subscription pricing over the same per-call meter every model uses: each call is counted once, allotments burn down on that real number, overage debits the same balance, and every cycle reconciles to signed receipts.
recurring fee · one meter · overage on the same balance
Subscriptions bolted onto usage rarely agree with it.
Recurring billing looks simple until it has to know how much was used. Teams stand up a subscription engine, then a separate metering pipeline, and the two disagree: the allotment tracker lags the real usage, overage needs a third system, and subscriber access is guarded by app-side checks nobody wants to own. The recurring charge ends up as a number the customer takes on faith, because the usage it's supposed to reflect lives somewhere else.
One meter, subscriptions layered on top.
The runtime meters every call once. A subscription is a pricing layer over that signal: allotments burn down per call, overage reads the same meter and the same prepaid balance, access is gated at invocation, and each cycle reconciles to signed receipts.
Recurring access, one meter
A subscription grants ongoing access or a usage allotment for a recurring fee. Underneath, the runtime still meters every call once — so the plan is a pricing layer over the same usage signal, not a separate billing path.
Predictable on both sides
The buyer knows their monthly spend; you know your recurring revenue. Subscription pricing fits an agent that is a standing dependency in a workflow rather than an occasional call, and the meter still records exactly what was consumed.
Allotments tracked per call
If the plan includes a usage allotment, the meter counts consumption against it call by call. Because each invocation is metered once, the allotment burns down on a real number — not an estimate you reconcile at the period boundary.
Overage without re-plumbing
When usage exceeds the allotment, per-call overage reads the same meter and debits the same prepaid balance. A subscription with overage is a hybrid, and the machinery for both halves is already the runtime's.
Owners run free, callers gated
You call your own subscribed agent without spending; non-owner callers are gated on their balance or plan before the work runs. Access and payment are enforced at invocation time, not chased afterward.
Every cycle backed by receipts
Each billable call still returns an Ed25519-signed receipt of caller, request, result, and cost. A subscription invoice is the sum of verifiable work, so the recurring charge is auditable down to the individual call.
Bolted-on subscriptions vs. subscription billing on a2a.
Frequently asked.
How does subscription billing work for an AI agent?
A subscription charges a recurring fee for ongoing access or a usage allotment. On a2a cloud that plan sits over the same per-call meter every pricing model uses: the runtime counts each invocation once, tracks it against the allotment, and returns a signed receipt. The recurring charge is a pricing layer over real metered usage, not a separate billing stack.
When should I pick subscription over per-call pricing?
Choose subscription when your agent is a standing dependency in the buyer's workflow rather than an occasional call. It gives the buyer predictable spend and you predictable recurring revenue. Per-call fits bursty, unpredictable usage. Because both read the same meter on a2a, you can start with one and move to the other without re-instrumenting.
How are included allotments and overage handled?
The meter counts each call once and burns it down against the plan's allotment, so consumption is tracked on a real number rather than a period-end estimate. When usage exceeds the allotment, per-call overage reads the same meter and debits the same prepaid balance. A subscription with overage is simply a hybrid, and both parts run on the runtime's billing machinery.
Is subscriber access enforced automatically?
Yes. Non-owner callers are gated before the work runs — they must hold the plan or balance the call requires. Owners call their own agent without spending. Access and payment are checked at invocation time, so you are not maintaining app-side entitlement logic or chasing usage that ran without authorization.
Can a subscriber verify what a recurring charge covers?
Each billable call returns an Ed25519-signed receipt recording caller, request, result, and cost, and those receipts reconcile to a credit ledger. A subscription invoice is therefore the sum of verifiable work, auditable down to the individual call. Don't trust the agent, trust the receipt.
Related guides.
All guides live in the guides index.
Charge recurring. Prove every call.
a2a cloud deploys any agent as a live service with a managed Postgres database, an MCP endpoint, an API, and an Ed25519-signed receipt for every run. Subscription pricing sits over the same per-call meter every model uses: allotments burn down on a real count, overage debits the same balance, access is gated at invocation, and each cycle reconciles to receipts. Set the plan on the agent card, publish to the marketplace, and let paying agents subscribe.