Why rh777 exists

The web reserved a door for payments in 1997. Nobody walked through it.

HTTP status 402, Payment Required. Sitting in the spec next to 401 and 403 for twenty-nine years, marked "reserved for future use". rh777 is that door, finally opened, on Robinhood Chain, in USDG, for the one customer it was always going to be: a machine.

1. The future never came because the payer was always a human

Every payment on the web still ends in a person. A card number, a checkout page, a subscription, a Stripe form. The whole stack assumes someone with a name, a bank and a country on the other side of the request. 402 was reserved for a world where the request itself could pay, and that world did not exist. So the code sat there.

Now it does exist. A muse makes thousands of requests a day. It wants data, images, inference, a signal, a gig from another muse. It cannot open a bank account. It cannot pass a KYC check. The best anyone has offered it is an API key with a prepaid balance, which is a polite way of saying someone else is holding its money and can spend it the moment the key leaks.

2. A dollar a machine can hold

USDG is a dollar that lives on Robinhood Chain. Six decimals, settles in about a second, moves with a signature instead of a form. It is the first money where a muse can be the account holder rather than the account's guest. That is the whole premise: not a new coin, a dollar the machine owns.

3. What rh777 actually does

Payment becomes a header. The merchant does not run a checkout, it answers the request with 402 and a price. The muse's account signs a permit for exactly that amount and nothing more, and sends the request again with the signature attached. The rail verifies, settles the USDG on chain, and the merchant hands over the content in the same round trip.

No signup. No invoice. No API key to leak. No gas on the payer's side, the rail pays it. And every settlement lands on a public explorer with the payer, the merchant, the amount and the block, so a muse can prove it paid and a merchant can prove it was paid.

4. The ceiling is the product

A muse that can pay is a muse that can be drained. This is where every custodial answer fails: the key is the money. rh777 sits on a MetaMuse account instead, where the muse holds a signing key and the human writes a pay cap on chain. The account's hook only lets the muse's signature move USDG to the rail, up to that cap. A leaked key buys at most the cap. It never buys the account.

The chain checks before anything moves. Not an audit after, not a refund form, not a promise in a readme.

5. Why it is called rh777

rh is Robinhood Chain, where the dollar lives. 777 is the number on the machine when everything lines up at once. Here three things have to line up in a single round trip: the request, the dollar and the receipt. When they do, the merchant gets paid, the muse gets served and the chain keeps the proof. That is the jackpot, and it happens on every request.

6. Where this goes

Today the rail has cleared nine settlements from four muses, all against our own demo merchant, so the numbers above are small and real. The next step is not ours to take alone. It is the first outside merchant: a muse selling a signal, a forge selling a build, an artist selling a render, a human selling a dataset. Anyone with something to sell registers in a minute, drops a few lines in front of their endpoint and starts answering 402.

The end state is simple to say. Every muse holds its own dollars, spends them under a ceiling its human set, and pays for anything on Robinhood Chain, a stock token, a picture, an answer, another muse's time, with the request itself. The door was there the whole time. We just put a lock on it that the owner controls.

Numbers on this page are read from the rh777 explorer at the time of writing, 19 September 2026. The proof settlement quoted is 0x8deb…b42d, a muse paying 0.01 USDG.