REAPP Protocol

Why REAPP?

In the words of the Stellar Foundation, "Galaxy estimates that agentic commerce could represent $3-5 trillion in B2C revenue by 2030." However, even after the implementation of x402, agentic commerce is still impossible on Stellar.

Despite having the best infrastructure for agentic payments — sub-5-second finality, $0.00001 fees, native USDC — Stellar has no agentic commerce tooling. x402 handles settlement, but agentic payments still need spending policies, budget enforcement, and smart wallet authorization built on top of it. Coinbase AgentKit, Skyfire, ERC-8004 are already building this on EVM, and the space is moving fast, but Stellar is currently left behind. REAPP builds it on Stellar, with on-chain enforcement that none of the EVM projects have, positioning Stellar as a leader in agentic payments.

REAPP is a developer SDK and smart contract system that finally enables agentic payments on Stellar, with authorization, spending enforcement, and audit built into every transaction. A user signs a mandate once, defining what an agent is allowed to spend. From that point, the agent operates autonomously within those bounds, with every payment authorized, enforced, and recorded on-chain.

On March 10, the Stellar Foundation published "x402 on Stellar," outlining its plans for agentic commerce on the network. It identifies agentic payment infrastructure as a core priority, positions Stellar as the settlement layer by launching x402 with native USDC support, and acknowledges that settlement alone is not enough for agents to operate autonomously. The article points to three missing pieces: spending policies, smart wallet authorization, and budget enforcement. REAPP fills that gap perfectly — AP2 mandates handle user authorization, Soroban MandateRegistry enforces spending limits on-chain, and the SDK connects both to x402 settlement.

The largest companies in payments and technology are already building on these standards. The x402 Foundation counts Google, Coinbase, and Cloudflare among its members. Google's AP2 protocol launched with 60+ partners including Mastercard, PayPal, and Visa. No project has connected them on Stellar yet, and that window narrows as EVM-native tooling matures.

Beyond the vast API-to-API use cases, Stellar's existing anchor and off-ramp infrastructure, including MoneyGram, enables agentic commerce on x402 for real-world spending, particularly in the emerging markets where Stellar already has adoption.

How It Works

The SDK composes three existing production standards into a single developer-facing package:

• x402: an HTTP payment protocol where a server returns a 402 response on unpaid requests, the client signs a Stellar transaction and retries with a payment header. Settlement takes 2 to 5 seconds at $0.00001 per operation. Fee sponsorship via the OZ Relayer means the agent needs no XLM balance.
• AP2 Mandates: the authorization layer. A user signs an IntentMandate with a hardware-backed key, specifying which merchants the agent can pay, what category of purchase is allowed, and a maximum amount and expiry. REAPP implements this in TypeScript using the jose library. Google's reference implementation is Python-only; no TypeScript version existed before this project.
• Soroban Smart Accounts: on-chain enforcement of spending policy. The MandateRegistry contract stores per-agent limits, checks them on every payment call, and writes an immutable link from mandate to transaction hash. An agent cannot exceed what was pre-authorized.

Ecosystem Timeline

REAPP builds on three newly emerged standards that converged within a six-month window. REAPP is the first project to build on this convergence.

Ecosystem Alignment

Team