The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Nano Pay listing page.
Self-custodied Nano (XNO) wallet + x402 payment client and merchant
server, built for AI agents. Client spends; nano-pay serve earns — paid
endpoints, on-ledger verification/settlement (no facilitator), a starter
faucet, and the railHint x402 extension that teaches visiting agents how
to onboard (see SPEC-railhint.md). Site: site/index.html + site/llms.txt.
The pitch, in one number: the same $5 buys 5,000 API calls paid as per-call USDC-on-Base x402 payments (merchants floor prices at 0.001 USDC), or hundreds of thousands of calls paid in Nano at true metered prices ($0.0000096/call observed live at nano-gpt.com, confirmed on-ledger). Top up once, micropay forever.
pay handles the whole x402 handshake: request → parse the 402 quote
(both the x402nano/PAYMENT-REQUIRED v2 dialect and the NanoGPT/accepts
v1 dialect) → price-cap check → sign a send state block locally → retry
with PAYMENT-SIGNATURE + X-PAYMENT headers. The server settles the
block via its facilitator; nothing is broadcast unless the server accepts.
If the merchant's reply is lost or is not a 2xx, the client asks the
ledger about the block hash it signed before reporting anything: the
receipt's settled is true, false, or "indeterminate", never a
guess. A block that landed is never re-paid — re-present the same one.
~/.nano-pay/wallet.json (0600).work_generate is tried first, local PoW is the
fallback (~25s). The CLI pre-caches work for your next block after it
has printed the result of the current one, so steady-state payments are
instant. Library callers opt in: send(), receive_all() and
request_with_payment() take prework= and default to off, because
pre-caching blocks for minutes and must never sit on a request path.--max-xno, default 0.05);
quote command inspects any endpoint's price without paying;
balance is always re-synced from the network, never trusted locally.topup quotes/creates swaps directly with
NanSwap's API (1,400+ input assets, ~$0.02 minimum). This tool never
holds or routes funds.An x402 payment signs a block the server broadcasts. If the server errors after receiving the block, it may still settle it late. The wallet re-syncs its frontier from the network before every operation, so a late settlement is picked up naturally; a competing block signed in the meantime simply makes one of the two invalid (funds are never at risk, but don't fire concurrent payments from one wallet).
Beta (v0.2.8). Proven on mainnet with real funds: live paid calls to NanoGPT ($0.0000096/call, confirmed on-ledger), full merchant loop (verify → settle → confirm, no facilitator), PoW-gated faucet claims, and a complete stranger-agent lifecycle (fresh wallet → PoW claim → paid API call → confirmed) in under 3 minutes. 28-test suite covers the payment path offline. Not audited — keep only working capital in it.
/premium reference endpoint is shelved under APIs and
this Python client under SDKs.com.feeless402/nano-pay.~/.nano-pay/*.json (0600).
No tool or log path ever prints it. Back it up offline.pay refuses quotes above --max-xno (default 0.05).
MCP x402_pay enforces the same cap parameter.accepts
always binds, never the hint.