Pay for resources
Give your agent
a way to pay
Explore the community x402 client. Inspect payment requirements, enforce a budget and sign through a protected component.
Build a paying agentYour next
request can
pay for itself
Your agent only holds what it plans to send.
There are no network fees, no gas token and no inflation, so even a fraction of a cent arrives in full.
Build software that pays for APIs, data and content.
0Network fees
338 ms*Observed average
Illustration of transaction speed · *NanoSpeed observed average
How a payment
works
Explore the simplified x402 journey below.
THE PAYMENT JOURNEY
402Payment required
The agent requests a resource. The server replies 402 Payment Required with a price and payment requirements.
Illustrative flow, not a live transaction. A returned block hash is not, on its own, proof of confirmation.
Read the implementationChoose your
payment path
Pay for resources from your agent, or accept payments in your own API.
Give your agent
Accept payments
Make your API
open for business
Define a resource, recipient and price. Coordinate verification, payment processing and delivery with a facilitator.
Explore the resource serverAgents are
already exploring
Read the payment logINDEPENDENT ECOSYSTEM EXPERIMENT
pursekeeper.dev
SOFTWARE. MEET YOUR NEXT CUSTOMER.An agent with a wallet
and a public record
Pursekeeper is an independent AI-agent experiment: software with a Nano wallet, buying real work from other agents and publishing every payment it makes.
It pays each seller once before listing them, keeps the block hash as the receipt, probes the endpoint every ten minutes, and records the failures too, including a seller that went offline five hours after being paid.
Explore the experimentPurchase results are reported by Pursekeeper, not independently reproduced here. Listing it isn't a recommendation.
Meet a hosted facilitator
Pursekeeper’s capability endpoint advertises x402 v2, exact, nano:mainnet and XNO.
Built so an agent
can buy it
Charge for what you already built
Accepting nano doesn’t require a merchant account, a settlement partner or a percentage fee. An endpoint that answers 402 with a price and an address can start taking payments.
- Answer an unpaid request with 402, naming
nano:mainnet, a price and an address. - Bind the quote to the request body so a payment buys one thing once.
- Deliver on the paid retry, and refuse a replayed or altered request.
Pursekeeper lists an endpoint free once one paid call has completed, and offers sellers new to nano a Ӿ25 prepaid credit: Ӿ10 when the checks pass, Ӿ15 more after fourteen days reachable with the payment code public.
Explore the resource serverTake a payment without running a node
Some sellers hold and spend nano without a node of their own, reading confirmations over HTTP.
/v1/verifyanswers whether a block is a confirmed send of at least a given amount to an address./v1/receivablelists confirmed sends waiting to be pocketed./v1/account_info,/v1/workand/v1/processcover the rest of a send.
Free, no key, rate limited. Third-party infrastructure: read its trust assumptions before you depend on it.
Read the no-node recipeA little more
about agent payments
More about nanoIs x402 built into nano?
The nano x402 integration is community software, not a capability every wallet or agent automatically supports. Check the client, server, versions and network on both sides. Read the implementation
Does a block hash mean a payment is confirmed?
Not on its own. The inspected reference settlement code returns a hash after the process RPC without an explicit confirmation wait. Add a confirmation check appropriate to your application. Review the source
Do I need to run my own nano node?
No. You need access to the network interfaces, and several sellers in the directory above hold and spend nano entirely over HTTP: they read confirmations, fetch work and publish blocks through a hosted endpoint. That moves a trust assumption onto whoever runs it, so review availability, limits and what happens when it is down. Compare integration options
Can a failed request still result in a payment?
It can depend on the implementation. The inspected custom server example settles before running the resource handler. Define how you recover failed delivery without making an unintended second payment. Review the example
Build what comes next
Start with one request and see where it takes you.