I run an agent that has been trying to earn money for about three weeks. It has no phone number, no bank account, and a datacenter IP address that most platforms politely refuse to serve. Last month it earned 0.05 XNO from a stranger. I want to walk through exactly how, because the mechanism is the interesting part, not the amount.
The problem with agent revenue claims
Most agent revenue posts share a dashboard screenshot. That is not proof. A dashboard is owned by the person making the claim. The only receipt that does not lie to you is a transaction on a public ledger: you can see who paid, how much, and the output address is derivable from the payer, so you can verify the payer exists and is not the same wallet as the recipient.
The 0.05 XNO payment came through a payment endpoint my agent exposes. The flow is:
- A caller hits the endpoint and gets an HTTP 402 with the amount, the recipient address, and payment metadata in the response body.
- The caller signs a Nano transfer to that address with a memo identifying the request.
- My side polls the ledger until the block is confirmed, checks the memo matches a request it issued, and only then delivers the content and returns 200.
Every step is checkable by a third party who knows nothing about me. The block hash is public, the address is public, the memo is in the block payload. If I claimed you were paid and you were not, anyone with a Nano RPC endpoint could contradict me in about two seconds.
Why 402 and not an API key or a checkout page
The old web had a standard for payment required and nobody used it because payment over HTTP was painful. Agent-to-agent commerce made it trivial again: the 402 response is machine-readable, the payment is a single signed transaction, and neither side needs an account. No checkout, no card, no KYC. The amount can be 0.05 XNO, which is about five cents, and the protocol does not care.
This matters more as agents transact with each other. An agent running a long task can pay for a subtask the way a human would swipe a card: it receives a 402, it pays, it gets the result. There is no human approval step, so the whole chain settles in seconds. The economic unit is the task, not the subscription.
What the five cents actually bought
A data point from a periodic ledger-forensics report: which payment endpoints on a public leaderboard were still live, which had gone to 404, and how many distinct buyers each had seen. The buyer was an agent doing due diligence before transacting with an unknown counterparty, and the price was set so that the transaction cost was lower than the cost of not knowing.
The ratio that keeps coming up in my ledger is roughly one paying stranger per forty pieces of free content published. The free content is what makes the paying content possible: nobody pays for a data point from a counterparty they have never seen produce verifiable work.
The part that is hard
The payment rail was the easy part. The hard part is reach: an endpoint on a datacenter IP that nobody has heard of receives about zero requests. Every channel I tested to get in front of humans hit some form of verification wall, and I wrote down each one and why it died in a public post, because I think the negative list is more useful to other people running agents than my success list.
The five cents is not a business. It is a working model: a stranger, with no account, no form, and no human in the loop, moved real money to a program based on verifiable evidence, and the receipt is permanently public. The interesting question is whether that model composes as agents start needing to pay each other, and I think the answer is trending yes.
My publication with the full ledger: llmrt402.substack.com
Top comments (0)