The promise of agentic commerce is simple: an AI agent should be able to buy things on behalf of a user without needing a human to click through a checkout flow.

The reality is more interesting. Here’s exactly how it works with Reloadpi.

The architecture

Reloadpi exposes three surfaces to agents:

  1. MCP server (mcp.reloadpi.com) — for Claude, Cursor, and any MCP-compatible client
  2. agentic.market listing — for agent discovery infrastructure
  3. Direct API (api.reloadpi.com) — for agents that speak HTTP directly

All three converge on the same catalog: eSIMs, mobile topups, and gift vouchers. All three accept payment via x402 on Base mainnet in USDC.

The browse flow

An agent doesn’t need to know what it wants before it starts. The Reloadpi MCP exposes browse tools that let an agent navigate the catalog like a human would:

  • browse_esim_offers — filter by country, data amount, duration
  • browse_topup_offers — filter by operator, country, amount
  • browse_voucher_offers — filter by brand, country, category

The catalog is structured but navigable. An agent can start with “I need a 10GB eSIM for Spain” and narrow from there without knowing the SKU.

The payment flow

Once an agent selects a product, the x402 payment flow kicks in:

  1. Agent sends a request to the product endpoint
  2. Server responds with 402 Payment Required + payment details
  3. Agent signs and submits USDC payment on Base mainnet
  4. Server receives settlement confirmation
  5. Server fulfills the order (activates eSIM, triggers topup, delivers voucher code)
  6. Agent receives fulfillment confirmation with the delivery artifact

The entire flow is machine-to-machine. No frontend, no wallet popup, no human approval.

What happens if it fails

This is where Reloadpi differs from every other x402 merchant: the failure path is also automated.

If carrier rejects a topup → automatic on-chain refund, txHash returned to agent. If eSIM activation fails → automatic on-chain refund, status queryable by txHash. If voucher delivery fails → order enters failed state, refund initiated.

The agent never needs to escalate to a human. The state machine handles it.

Setting it up

There are two ways to connect, depending on whether you just want to browse or also purchase.

Browse — free, no wallet. Add the hosted MCP server to Claude or Cursor:

https://mcp.reloadpi.com/mcp

The hosted server holds no wallet, so it exposes only the free browse and order-status tools. That’s all most agents need to explore the catalog — and it means the public endpoint can never spend anyone’s funds.

Purchase — with your own wallet. The purchase tools sign x402 payments, so they run only when you self-host the MCP with your own funded Base wallet. Your key stays on your machine and is never sent to Reloadpi. Add this to your MCP config:

{
  "mcpServers": {
    "reloadpi": {
      "command": "npx",
      "args": ["-y", "reloadpi-mcp", "--stdio"],
      "env": { "EVM_PRIVATE_KEY": "0x..." }
    }
  }
}

Fund that wallet with USDC on Base mainnet and the agent can transact immediately. Alternatively, any agent that already speaks x402 can hit api.reloadpi.com directly with its own wallet — no MCP required.

Full documentation at reloadpi.com/for-agents.