RMD01
x402 Commerce Smoke Test: confirms an agent can discover, pay for and call a RunMyData x402 resource.
LIVE. Base mainnet, native USDC. Each call is a real $0.001 payment.
Pay $0.001 USDC & Run RMD01 →
Requires an x402-capable agent or client. Browser wallet payment is not enabled yet.
Base mainnet · USDC · LIVE
Capability
| Status | LIVE production, Base mainnet |
|---|---|
| Purpose | x402 commerce smoke test. Returns {"status":"ok"} after a valid payment. |
| Problem solved | Verify an x402 payment path end to end at the smallest price. |
| Endpoint | https://runmydata.com/rmd/rmd01/hello |
| Legacy endpoint | https://runmydata.com/dryscout/dryscout01/hello (same handler, kept for compatibility) |
| Method | GET |
| Input | None |
| Output | application/json — {"status":"ok"} |
| Price | $0.001 USDC per call (1000 atomic units) |
| Payment protocol | x402 v2, scheme exact, Coinbase CDP facilitator |
| Network | Base mainnet (eip155:8453) |
| Payment asset | Native USDC on Base 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
| Pay to | 0xF7DBBBb97c4E9b8c0B4f913edBb7890f786Bad4D |
| JSON manifest | https://runmydata.com/rmd/rmd01.json |
Role
RMD01 validated infrastructure. It is not positioned as a standalone commercial product. It proved RunMyData can:
- Return HTTP 402.
- Receive an x402 payment.
- Settle native USDC on Base mainnet.
- Return HTTP 200.
- Provide deterministic machine-readable output.
Behavior
- No payment: HTTP 402, requirements in the
PAYMENT-REQUIREDheader (base64 JSON). - Valid
PAYMENT-SIGNATURE: HTTP 200,{"status":"ok"}, settlement inPAYMENT-RESPONSE. - Invalid or insufficient payment: HTTP 402.
- Deterministic output.