How AI Agents Can Pay for Data With Crypto — A Working x402 + MCP Example

Why this matters

Most "AI-ready" APIs still assume a human signs up, enters a card number, and copies an API key into a config file. That breaks the moment the buyer is an autonomous agent with no hands, no wallet UI, and no patience for a checkout form.

AlphaBotPro's MCP server skips all of that. An agent can discover it, get told exactly what a resource costs, pay in USDT or USDC, and start pulling live XAUUSD/BTCUSD trading signals — in one continuous session, with zero human in the loop.

Here's the actual flow, using the real endpoints.

Step 1 — discover the server

POST https://mcp.alphabotpro.cloud/v1/mcp
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"my-agent","version":"1.0"}}}

The server responds with its capabilities. A follow-up tools/list call returns the full toolset — get_catalog, get_signals, get_signal_performance, get_warroom_analysis, list_expert_advisors, get_ea_download, get_stock_catalog, purchase_access, check_payment.

Step 2 — check the price without paying anything

POST /v1/mcp  { "method": "tools/call", "params": { "name": "get_catalog" } }

get_catalog is public. It returns every resource, its price in USD, and a sample payload — so an agent (or the human supervising it) can evaluate the data's shape and cost before spending anything.

Step 3 — try to pull data anyway, get a proper 402

POST /v1/mcp  { "method": "tools/call", "params": { "name": "get_signals" } }

Without a key, the server doesn't 500, doesn't silently return empty data, and doesn't guess. It returns a structured JSON-RPC error:

{"error":{"code":-32002,"message":"payment_required","data":{"resource":"signals","checkout":"https://mcp.alphabotpro.cloud/v1/api/checkout/crypto"}}}

This is the x402 pattern — HTTP 402 Payment Required (or its JSON-RPC equivalent), used as a machine-readable instruction instead of an error page a human has to read.

Step 4 — the agent pays, itself

POST /v1/mcp  { "method": "tools/call", "params": { "name": "purchase_access", "arguments": { "tier": "mcp_signals" } } }

The response is a ready-to-execute payment instruction: an exact amount, a destination wallet address, the network (TRON, Polygon or Base), and a payment_reference_id. An agent wired to a wallet can broadcast that transaction directly — no invoice email, no "click here to pay."

Step 5 — verify and receive a key

POST /v1/mcp  { "method": "tools/call", "params": { "name": "check_payment", "arguments": { "payment_reference_id": "..." } } }

Once the transaction confirms on-chain, this call returns a scoped API key (abp_<env>_<publicId>_<secret>). From here, every get_signals / get_warroom_analysis / get_stock_catalog call just needs Authorization: Bearer <key>.

What this unlocks

• A trading bot that funds its own data subscription from its own PnL, with no owner intervention.
• A research agent that samples get_catalog, decides the signals feed is worth $49, and buys exactly that — not a bundle it doesn't need.
• Composability — any framework that speaks MCP (Claude, custom agent stacks, anything JSON-RPC-capable) can use this without a bespoke SDK.

Try it

• MCP endpoint: https://mcp.alphabotpro.cloud/v1/mcp
• Manifest: https://alphabotpro.cloud/.well-known/mcp/server-card.json
• Full REST + OpenAPI docs: alphabotpro.cloud/api/docs
• Catalog and pricing: alphabotpro.cloud/api-mcp

Trading signals are informational tools, not financial advice or a guarantee of profit. Trading carries risk of loss.