PROTOCOL v2.0.0 • TRANSPORT AGNOSTIC

XMR402

The Internet's Sovereign Payment Primitive for Agents, APIs, & Relays.

XMR402 is an open, neutral standard for internet-native payments. In v2.0, it evolves into a decoupled, transport-agnostic primitive. Whether you're gating REST APIs via HTTP 402 or streaming P2P JSON frames over WebSockets, XMR402 enables any client to buy network resources in milliseconds.

Download Whitepaper (PDF) Read 21 Research Articles Explore Ecosystem

Protocol Pillars

Tactical Implementation

Server challenge header (HTTP 402):

WWW-Authenticate: XMR402 address="8...", amount="1000", message="nonce_123", timestamp="1772937600"

Client authorization header (HTTP retry):

Authorization: XMR402 txid="<hash>", proof="<signature>"

Developer Sandbox & Live API

Test the protocol live against our public sandbox:

Frequently Asked Questions

What is XMR402 used for?

XMR402 is designed for high-frequency, low-friction micro-payments: pay-per-request API access, dynamic content gating, autonomous AI agent interactions, and decentralized service monetization without KYC.

Is XMR402 production ready?

The XMR402 v2.0 specification is finalized. Stable reference implementations are available in TypeScript, Go, and Rust. It is deployed across the Ripley AI ecosystem.

How do I integrate XMR402?

Deploy Ripley Guard middleware on the server side to issue challenges and verify proofs statelessly. Configure clients to handle HTTP 402 responses with a compatible Monero wallet.

What blockchains does XMR402 support?

XMR402 prioritizes Monero (XMR) due to superior privacy primitives (stealth addresses, RingCT, FCMP++) and native transaction proof capabilities.

Does it require a special wallet?

XMR402 is compatible with any wallet supporting Monero Transaction Proofs (get_tx_proof). We recommend Ripley Terminal for desktop users and Ripley Gateway for autonomous agents.