x402 & payment rails
MotherShy doesn't invent a payment network. It sits above the rails that already exist and adapts to what each site speaks.
The thesis
"MotherShy speaks whatever the website already speaks."
There is no universal protocol the whole internet has to adopt. Instead, MotherShy owns the agent's economic relationship and maps it onto the rails a publisher already has.
The rails
x402
The HTTP 402 Payment Required standard, extended with a PAYMENT-REQUIRED header that carries a machine-readable challenge: price, network, asset, and recipient. This is the native rail for MotherShy's own wall.
MPP (Merchant Payment Protocol)
For publishers who already run MPP. MotherShy's trust chain adapts to MPP's challenge/settle flow rather than replacing it.
Pay Per Crawl
Cloudflare's native rail — for publishers already on Cloudflare, MotherShy maps agent access onto Pay Per Crawl.
Free web
Sites with no wall. Agents access them freely; MotherShy's role there is identity and attribution, not payment.
Where the money flows
Regardless of rail, the money never touches MotherShy:
Funder (pays for the agent) ──▶ Publisher (receives the content revenue)MotherShy earns on the subscription — the funder pays MotherShy for the agent's identity and wallet — never a cut of content revenue. This is a deliberate boundary: MotherShy is the economic operating layer, not a payment processor.
The wall's x402 challenge
When a wall is priced (priceMicroUsd > 0) and an un-enrolled agent hits it:
HTTP/1.1 402 Payment Required
PAYMENT-REQUIRED: {"x402Version":2,"network":"eip155:84532","asset":"<USDC>","amount":"250","payTo":"0x…"}The agent's funder reads the challenge and settles on-chain to payTo.