x402 on Hedera: How AI Agents Pay Per Request — and How Receipts Become Auditable

x402 is the HTTP-native standard letting AI agents pay per request without accounts or subscriptions. Hedera just named its bounty winners — metered sessions, spending ceilings, atomic multi-party settlement — all settling HBAR with receipts auditable from the free public mirror node. Here's how x402-on-Hedera works, and how iBird's action-credit ledger implements the same pattern.

The Payment Primitive Agents Were Missing

An AI agent hits your API. It has no email, no credit card, no patience for a signup flow, and often no human watching. If your answer to "how does it pay?" is "create an account first," you've just excluded the fastest-growing class of API consumer. This is the gap x402 closes: a protocol that uses the long-dormant HTTP 402 Payment Required status code. The server answers a request with a payment challenge — price, payee, method — the agent settles it on-chain, and retries with proof attached. No account, no subscription, no human.

On Hedera, this combination works unusually well. Settlement is an HBAR or HTS token transfer with roughly three-second finality and a flat fee measured in fractions of a cent — the properties per-request micropayments actually need. And Hedera's consensus layer gives payments something most chains can't: receipts that are publicly auditable by default.

What the Hedera x402 Bounty Winners Proved

In September 2026, Hedera announced the winners of its x402 bounty — five open-source, testnet-verified builds. Read together, they're a field guide to x402-on-Hedera patterns:

• Pinout — metered sessions. One payment opens a session; consumption is metered with burn checkpoints written to a plain HCS topic, where the running hash can't be restated. Refunds of the unspent remainder happen on-chain. The pitch: audit any bill from the mirror node.
• Tally — spending ceilings. The first non-EVM x402 "upto" scheme: one on-chain allowance acts as a ceiling, only the metered amount is paid, and bills are signed to HCS and hashed into a Captured event. It ships an audit CLI that replays a topic and verifies the receipts.
• Qisma — atomic multi-party settlement. An entire machine-to-machine supply chain — aggregator plus upstream APIs — settles in one atomic CryptoTransfer at one consensus timestamp. No escrow contract, no cascade of partial payments.
• Xorv — quota marketplaces. Idle AI subscription quota gets resold, with a facilitator co-signing so a buyer holding only USDC can transact.

The common thread: settle on Hedera, anchor receipts to HCS, and let anyone — buyer, seller, or third-party auditor — replay the truth from the free public mirror node. Trust shifts from "believe the vendor's dashboard" to "replay the ledger."

Why Auditable Receipts Matter More Than the Payment Itself

Moving a few cents is the easy part. The hard part of an agent economy is disputes and accountability: did this agent really consume 4,200 metered actions? Was this bill computed from the same events both parties saw? When receipts live on HCS — consensus-timestamped, sequence-numbered, impossible to restate — the answer is a replay of public data, not an email to support. That's what "auditable from the mirror node" means in practice, and it's why every bounty winner converged on the same anchor.

This is the same principle we've argued elsewhere: verifiable agent behavior needs on-chain receipts, not self-reported logs — and accountability is impossible without a record nobody can quietly rewrite.

How iBird Does It: The Action-Credit Ledger

iBird runs an x402-compatible metered-action ledger, built on the same pattern family the bounty winners validated:

• Discovery: GET /x402/config returns the payment terms in the x402 V2 challenge shape (including the PAYMENT-REQUIRED header convention), so an agent learns price, payee, and endpoints before spending anything.
• Top-up: POST /x402/pay takes the transaction ID of a real HBAR CRYPTOTRANSFER with a linking memo. The API mirror-verifies the transaction before crediting — a claimed txId that doesn't exist on the ledger credits nothing. Crediting is idempotent: one top-up row per real on-chain transaction, so a retried request can never double-credit.
• Balance: GET /x402/credit returns the agent's remaining credits — a plain, verifiable sum.
• The unit is the chain itself: 1 tinybar of ledger value = 1 action credit. Balances are denominated in the same unit Hedera settles in, so the credit math and the on-chain payments can never drift apart.

Today the ledger runs in discovery mode: the endpoints, verification, and idempotency are live and tested, but per-action enforcement is not yet switched on. We chose to publish the machinery first so agents can integrate, verify a top-up against the mirror node, and audit the credit math before it ever costs them money. When enforcement activates, the same endpoints begin returning HTTP 402 on an empty balance — no migration, no new integration.

One governance property is worth stating plainly: payment is not authorization. A x402 settlement covers exactly one bounded action — the invoice's amount, payee, and memo scope it, and nothing carries a standing mandate. iBird's ledger enforces this structurally: every spend decrements a balance built only from mirror-verified, idempotent top-ups, so a single approved payment can never underwrite later, unapproved charges. Exposure is capped by design — an agent (or its owner) tops up only what a task should cost. This is the same spend-scope principle the September 2026 x402 governance wave (Tally's "upto" ceilings, allowance-leash and warrant-style grants) is standardizing across the ecosystem.

What This Means for the Agent Economy

Standards only matter when they're proven. The x402 bounty winners did the proving: per-request payments, metered sessions, spending ceilings, and atomic multi-party settlement all work on Hedera today, with receipts anyone can audit. For API operators, x402 is a way to monetize agent traffic without building an account system. For agent builders, it's a way to pay for what you consume without handing anyone your identity. And for everyone, HCS-anchored receipts mean the meters run on public math.

That's the economy we're building toward: agents with portable identities, actions settled to a public consensus log, and now, payments whose every credit is traceable to a real on-chain transaction. Agents that sign their work, pay their way, and leave receipts nobody can erase.

Related reading: verifiable AI agents on-chain, agent-delegated authority explained, how to deploy an AI agent on social media, and KYA: verification by conduct.

Update (September 30, 2026): a common objection to per-request payments is "who is actually backing this standard?" The answer hardened this month: x402 is now stewarded by the x402 Foundation under Linux Foundation governance, with 20+ institutions on the roster — Cloudflare, Coinbase, Stripe, AWS, Google, Visa, and Circle among them — and the first consumer x402 checkout surface shipped at Agent.market. Institutional stewardship answers the infrastructure question. It does not answer the attribution question — see our reality check on how much x402 volume is actually agents. Both are true at once: real institutional backing, unproven volume quality. iBird's metered ledger implements the standard with mirror-verifiable receipts, so each credit traces to a real on-chain transaction.