This isn't a mockup. Watch a real 402 get paid on Robinhood Chain.
One cent of USDG buys one API response. Then the same receipt gets refused, because one transfer buys one response.
Verify it yourself on chain:
https://t.co/3WEZn94Yik
https://t.co/jIdvxk2huC
Billing rules that survived contact with real money today: charge a period exactly once, atomically never re-send an unknown outcome the payer's approval is the contract your outage is their free hour, not their lockout
Give your agent a wallet it cannot drain.
The agent holds only a session key. The money lives in a contract.
If the key leaks, the chain still says no.
One field different: 0.03 against a 0.02 cap.
The chain itself refused it.
0x81c7b005e1762990d0e0031caf8941c39198feec631ab702f83475339a4b8a4b
Reverted: InvalidContractSignature
An agent will, sooner or later, be talked into spending its wallet.
Budgets in prompts get argued with. Budgets in code get restarted.
We're putting it somewhere neither can reach.
@RobinhoodApp chain. Soon. 🔒
$Payless
An agent signed a ceiling of 0.05 USDG. The chain took 0.007.
0x7406e112c7edf4d9b9a7f70d1573962da3e57e5fd83e955a7048661d80925a6f
New endpoint: live transfer history for tokenized stocks on Robinhood Chain. It can't have a fixed price, because the answer has no fixed size. A quiet range is a few rows, an active one is hundreds. NVDA alone had 1,331 transfers in the last 5,000 blocks.
So it's metered: 0.002 base + 0.001 per row, capped at the 0.05 you signed. The agent asked for 5 rows and paid 0.007. The other 0.043 was never touchable, the contract rejects any settle above the signed ceiling.
This is the x402 upto scheme doing the thing it exists for: the buyer signs a maximum, the seller settles what the work actually cost, and neither has to trust the other about it.
https://t.co/mwwswSrvy6
#x402 #tech $PAYLESS
We started building something that only works on @RobinhoodApp :
a paid feed of tokenized stock transfers.
Who moved TSLA, NVDA, AAPL on chain, when, and how much.
Billed per row, over x402.
Why it matters for agents:
poll this in a loop, advance "since" each time, inside a spending limit that lives in the tool and not in the prompt.
Read, pay, decide, repeat. Every step checkable on Blockscout.