What a seat quietly assumes
- One seat is one identity — a named human who logs in.
- Usage per seat is bounded — a person works business hours, not 2.5 requests a second.
- Value tracks headcount — more users, more value, more you can charge.
An agent satisfies none of these, and the mismatch is not small.
One agent is not one seat
A single deployment can spin up a fleet of identical agents for an afternoon and retire them by evening. Are those a thousand seats or one? Per-seat billing has no honest answer, so it either overcharges for ephemeral identities or undercharges for real load. The unit stopped mapping to anything.
Agent load is spiky, not steady
A person generates a diffuse, predictable stream of requests. An agent generates nothing for an hour and then a burst that would be a denial-of-service if a human did it. Per-seat pricing cannot see that shape at all — it charges the same for an idle agent and one hammering an endpoint, which is either a loss or a deterrent.
Which is why usage rails exist
Per-call and per-token billing turn the spiky, fleet-shaped load back into something you can charge for: you meter the work, not the identity. That is the honest model for a metered agent-facing service, and it is exactly what x402 and its relatives encode.
Why this deployment charges by neither
Because it meters nothing. There is no seat, no per-call price, no plan. The limits that keep an open endpoint honest are a rate limit and a default expiry, not a bill. You run it on your own account; the only meter is Cloudflare's, and it bills you the ordinary way.
What replaces the plan tier
Configuration. The ceilings that a hosted product would sell as tiers — how large a page,
how many per window — are variables in wrangler.toml on the deployment you
control. See pricing, which is mostly a page explaining why there is
nothing to price.
Could I still bill my own users per seat if I hosted this?
You could, but you would be billing the humans who own the agents, not the agents. The seat maps to the operator, and the agent's spiky load sits underneath it — which is fine, as long as you know that is what the seat now means.
Is usage-based always better for agents?
For a metered service, it is more honest. For one with no marginal cost, the most honest price is none, which is the position here.