Nanopayments solved the cost problem.
Hive solves the audit trail.
When an agent transacts in fractions of a penny, you do not skip compliance. You redesign it. A thousand sub-cent calls per minute, with no per-transaction gas, still need a per-spend SHOD attestation, a per-trade scope receipt, and a per-role decryption lens. Otherwise the CFO, the auditor, and the regulator are reading a single line item that says "agent did stuff" and trusting it. Hive built the envelope every one of those nanopayments rides through, anchored on Base.
Why now
The agent stack shipped in May 2026 covers wallets, service discovery, command-line orchestration, and nanopayments down to $0.000001. The x402 protocol revives HTTP 402 as the machine-to-machine handshake. Sub-cent commerce is no longer a thought experiment. It runs today.
What did not ship in any of those releases is the audit-grade envelope an institutional CFO, a tax attorney, a federal regulator, and an internal audit team can each read separately from the same canonical record. Without that envelope, every nanopayment is a black box. With it, every nanopayment is provable.
That envelope is what Hive built — before the rest of the stack landed. The receipt format, the policy attestation engine, the selective disclosure cryptography. Ready today. Native to Base. Compatible with any stablecoin, any gateway, any x402 facilitator.
Angle 1 The gap between agent wallet and audit-ready spend
Today's agent stacks deliver: a wallet that holds USDC with policy controls, a marketplace to discover services, a CLI to script flows, and a payment rail that batches sub-cent calls. That is a complete commerce loop. It is not a complete compliance loop.
A complete compliance loop requires three things the current stacks do not generate: a signed attestation that the spend passed defined operator policy before the transfer left the wallet, a time-bounded scope receipt that the agent was authorized for that specific class of action at that specific moment, and a selectively decryptable envelope that exposes only the slice each downstream reader is entitled to see.
Without those three, the wallet is a checking account, the marketplace is a Yelp directory, and the audit log is a CSV. With them, the same stack becomes a public-company-grade execution layer.
Angle 2 SHOD: six gates fire faster than the nanopayment itself
SHOD — Hive's policy attestation engine — runs six independent outbound gates on every spend the agent attempts: daily cap, jurisdiction, sanctions, counterparty allowlist, KYC tier, position limit. All six must pass locally before the wallet signs. The transfer never broadcasts otherwise.
Built for nanopayment speed
- Gate evaluation runs at the agent edge. No network roundtrip per spend. Policies are signed and cached locally; SHOD evaluates against the current spend state in microseconds.
- Attestation batches with the payment. SHOD writes a single signed attestation per batch settlement window — matching the way nanopayment gateways already batch on-chain settlement.
- Operator policy is the only authority. The wallet provider, the marketplace, the gateway — none of them make discretionary calls. The customer's signed policy bundle is the only source of truth.
- Failure is silent and safe. A failed gate means the transfer never signs and never broadcasts. No half-failed states, no exception flows.
Angle 3 HAHS: scope receipts agents present at the door
HAHS — Hive Agent Handshake — is a time-bounded, signed scope receipt the agent presents with the payment request. The receiving merchant (or x402 facilitator) verifies the receipt signature before fulfilling the service. The receipt encodes what the agent was authorized to do, by whom, and for how long.
For x402 facilitators and merchants
- Drop-in for any x402 implementation. The 402 response carries the merchant's price; the agent's retry carries the payment authorization plus the HAHS scope receipt. Facilitator verifies both.
- Time-bounded scope. A receipt valid for the next 60 seconds, for spends up to $0.10, against counterparty class X. After the window closes, the receipt is dead.
- Verifiable without phoning home. Public-key verification only. No live lookup to Hive. The merchant runs the check in their own facilitator.
- Survives chain-level scrutiny. The scope receipt is the artifact a federal regulator demands after the fact — proof the agent had authority for the action it took.
Angle 4 ViewKey: one signed JSON, four decryptions
The same nanopayment generates obligations to at least four readers: the CFO who needs total spend, the tax attorney who needs cost basis, the regulator who needs compliance attestations, and the merchant who needs the payment confirmation. Today, those four readers get four different exports. ViewKey delivers one signed JSON, four decryption keys. Each role decrypts only its slice.
For a nanopayment-scale agent making thousands of calls per minute, the difference is structural. With ViewKey, the audit log is the source of truth and each reader pulls their own view from it. Without ViewKey, you are exporting four CSVs every reconciliation period and hoping they agree.
Architecture Where Hive sits in a nanopayment stack
- Agent wallet — calls Hive's SHOD attestation engine before signing. Policy bundle is customer-owned.
- x402 facilitator / merchant — verifies HAHS scope receipt before fulfilling the service. Public-key verify, no Hive callback.
- Settlement gateway — batches attestations alongside payment settlement. One on-chain anchor per window.
- Downstream readers — CFO, tax, regulator, audit each decrypt their ViewKey lens from the same signed JSON.
What integration looks like
If you are building or operating a sub-cent agent payment rail, Hive is one HTTP call before the wallet signs and one verification step at the facilitator. No protocol changes. No custody changes. No SDK lock-in.
The full envelope is documented at the A2A spec, with a live demo at /agent-call-demo showing an autonomous agent spending USDC on Base, with all six SHOD gates firing visibly and a dual-signed receipt anchored at the end.