x402 payments for Hono
Hono's edge-first design pairs naturally with x402: stateless paid requests, no session infrastructure, and settlement handled by an external facilitator. `paygate init` generates a runnable Hono seller.
Scaffold the seller
The template wires the 402 challenge, facilitator verification, and settlement into a Hono handler you can extend.
npx paygate init --framework hono --wallet 0xYourAddress --price 1
Production settlement
The default network is Base Sepolia for safe testing. Pass `--network base` to settle real USDC or EURC on Base mainnet through facilitator.arispay.app (no facilitator fee).
On the buyer side, any AI agent can pay your endpoint with `npx payagent pay <url>` or the payagent SDK — the 402 challenge your route now returns is the whole integration contract.
Pricing guidance
- Edge endpoints tend to be cheap to serve — that is an argument for volume pricing at 1–2 cents, not for giving the response away.
FAQ
- Does x402 add latency to paid requests?
- One facilitator verification round-trip before the handler and an async settlement after it. Unpaid requests short-circuit at the 402 challenge with no external calls.
Is your service agent-ready?
Run the free readiness scan — it inspects your live endpoint's discoverability, machine-readable contracts, and payment support, then tells you the highest-impact fix.