Updated 2026-10-04: token allocation, status and wording.
Machine identities already outnumber human ones by roughly 50 to 1 in enterprise environments (Omdia, 2024), and IDC expects more than a billion active AI agents by 2029. Point that curve at today’s per-check verification economics and the problem becomes arithmetic. If every agent of every human must re-pay identity verification at every counterparty, the cost of trust scales with the product of agents and relationships, and the only rational responses are the two bad ones: skip verification, or centralise it into a surveillance platform. Amortisation is the third answer, and it changes the cost structure of trust itself.
Per-check KYC re-pays the same verification at every counterparty
The verification industry’s unit economics were built for humans, who onboard rarely. Each check is billed per instance, and the same person is re-verified at every institution that needs assurance — an accepted overhead when a person opens a handful of accounts in a lifetime. Agents break the arithmetic in both directions at once: one human deploys many agents, and each agent transacts with many counterparties, at machine speed. Fifty machine identities per human (Omdia, 2024) is the ratio before the agent wave; Gartner projects that by the end of 2026, 40% of enterprise applications will embed task-specific agents, up from under 5% in 2025. Re-paying a human-grade verification for every agent-counterparty pair does not scale. (Sources for every figure here: where the numbers come from.)
Verify once, mint many
Amortisation restructures the cost around what is actually expensive. The costly, human-grade act — a KYC verification with an approved issuer — happens once. From that single verified backing, the issuer mints one agent credential per agent the human deploys — derived from the human’s credential in zero knowledge — each carrying its own scope, each revocable, each unlinkable from its siblings. One human verification backs every agent that human deploys.
The marginal cost of the Nth accountable agent is therefore a mint fee and a lease fee — well below the cost of a KYC — and the Nth verification of that agent carries no protocol fee. As the fleet grows, the cost of accountability per agent tends toward the mint cost, not the KYC cost. That is the entire economic argument, and everything else is its consequences.
Where a public network’s revenue would come from
A public, sovereign rail would still have to sustain itself: validators, issuers and arbiters do real work. Everything such a network would earn fits in five flows, the structure the tokenomics page publishes:
- Mint fee and lease fee. Each agent credential would pay a mint fee when issued and a small recurring lease fee while it lives, with a protocol cut whose allocation is under review. Costs scale with the agent population — never with how often agents prove things.
- Issuer economics. KYC organisations pay registry admission and renewal, and post a slashable bond that makes misbehaviour expensive. Issuers charge their own clients for KYC and issuance — an issuer that joins can offer the rail to its whole portfolio.
- Disclosure brokerage. On the consented commercial disclosure rail, specified for a later stage, a relying party that pays to identify an agent would pay the bid to the principal — the person whose privacy is at stake — while the issuer earns a brokerage fee for operating the consent machinery. Identification becomes a metered, priced event with the privacy-holder collecting.
- Dispute & arbiter market. In the funded-recourse stage, disputes would run on slashable bonds and a paid, registered arbiter market, with the accumulated cost borne by the eventual loser — off-chain service revenue for ecosystem roles, never consensus rewards, which stay reserved for validators.
- Premium verification services. Verifying itself carries no fee; what would be paid is the optional layer around it — mirrors, archives, SLAs, dashboards.
Presentations carry no fee because the design has nowhere to collect one
The fifth flow rests on a claim that deserves scrutiny: a presentation carries no fee. That is a property of the architecture. A verifier checks a zero-knowledge presentation statelessly and off-chain against a recent signed status root. No transaction is written, no per-check state is touched, no metered service sits in the path — there is no meter to run and no toll booth to place one in. The design gives a network no way to collect a fee per presentation. That is why the flows above are shaped the way they are: a network would charge where costs accrue — credentials existing — and has no way to charge where they do not — credentials being checked.
Why there are no numbers in this article
You will notice what is missing: no mint fee, no lease amount, no bond size, no point figure for any cut. That is policy. The mechanism of each flow is committed in the specifications, the protocol cut and its allocation are governed parameters under review, and the bands the other numbers must fall inside are ratified and published in the whitepaper; the points are versioned parameters, fixed only by an independent pre-genesis economic simulation. Publishing point figures before the simulation would be marketing dressed as engineering — the same failure mode as publishing unverifiable market claims. Structure and bands now; point figures only from the simulation. Every market figure this article does use carries a primary source on the sources page.