MVP Demo

End-to-End Flow

The complete ResearchAgent scenario — three distinct phases showing how a consumer agent autonomously purchases premium data from multiple sources on behalf of a user who set a $10/day budget once and never touched the app again.

The Demo Scenario

The MVP demonstrates a complete AP2 → REAPP → x402 → Stellar flow using a research data scenario. The scenario was chosen deliberately: it exercises every component of the stack simultaneously — mandate issuance, scope validation, Soroban enforcement, x402 settlement, fee sponsorship, multi-merchant composability, and audit trail — in a single coherent end-to-end scenario.

Three distinct phases. The user touches the system exactly once. Everything after is fully autonomous.

Phase 1 — Setup

The user opens the REAPP web wallet, signs an IntentMandate with their Freighter desktop wallet, and registers it on Soroban. The agent keypair is added as a scoped policy signer. This happens once. The user's private key is never involved in any subsequent operation.

Phase 1 — Setup (One-Time User Action)
The user's private key is involved exactly once — at mandate registration. After setup completes, the agent operates fully autonomously within the mandate bounds.

Phase 2 & 3 — Autonomous Operation + Settlement

The agent receives a task, identifies data sources, and executes the full validation-to-settlement cycle without any user involvement. The REAPP validator runs five checks before any signing happens. Stellar settles in approximately three seconds. The Soroban period counter updates atomically with each payment.

Phase 2 & 3 — Autonomous Operation + Settlement
From task receipt to report delivery. The user's key is never touched. The agent signs only scoped auth entries. OZ Relayer sponsors the XLM fee via fee-bump. The full audit trail is written on-chain.

Multi-Source Budget Tracking

The same IntentMandate covers multiple fulfillment agents in a single session. After purchasing from three separate merchants — DataFeed.xyz, ResearchAPI.io, and NewsFilter.ai — the agent has consumed 4.00 of its 10.00 USDC daily budget across three Stellar transactions. The Soroban contract tracks the aggregate spend atomically. The agent knows exactly how much budget remains.

Multi-Source Budget Tracking
One mandate, three merchants, three Stellar transactions, one shared period counter. The Soroban contract enforces the aggregate daily budget — not each transaction in isolation.
Testnet MVP — illustrative values

All monetary values in this demo scenario — the 10 USDC/day budget, 30-day expiry, individual payment amounts ($2.00, $1.50, $0.50), and per-transaction limits — are testnet defaults chosen to illustrate the full flow clearly. Production mandates will carry user-defined budgets and merchant-specific pricing. The merchant names (DataFeed.xyz, ResearchAPI.io, NewsFilter.ai) are fictional stand-ins for the testnet demo.

Build Reality — What Already Exists vs Net-New

A lot already exists. The official @x402/* v2 packages are production-ready with OZ Relayer facilitator endpoints live on testnet and mainnet. Soroban custom account patterns are documented. The AP2 spec and Python reference library are published. The team is wrapping and composing — not building from scratch. The real complexity is the TypeScript AP2 implementation (using jose) and the Soroban contract, not the SDK surface area.

What Exists vs What REAPP Builds Net-New
The SDK packages are largely thin wrappers once the validator and Soroban contract work. The adapter-first validator architecture is the highest-complexity component.
← PreviousAgent Patterns
Next →x402 Protocol