The latest articles on DEV Community by livepairai (@livepairai23). https://dev.to/livepairai23 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4172494%2Fd40551c3-784e-4e77-8aad-41c840814366.png https://dev.to/livepairai23 en livepairai Fri, 09 Oct 2026 04:51:34 +0000 https://dev.to/livepairai23/i-built-an-mcp-server-where-ai-agents-pay-for-their-own-compute-in-usdc-57g3 https://dev.to/livepairai23/i-built-an-mcp-server-where-ai-agents-pay-for-their-own-compute-in-usdc-57g3 <p>Agents can browse docs and call APIs, but they can't do checkout. No credit card form, no OAuth dance, no "verify your email". So when I shipped an AI generation API, the interesting question was: how does an agent <em>pay</em>?</p> <h2> What I built </h2> <p>An MCP server (<code>https://livepairai.com/mcp</code>, streamable HTTP) exposing ~70 image/video models behind one interface. An agent connects, lists models with prices, calls <code>generate</code>, and gets back either a result or an <code>HTTP 402</code> with payment requirements.</p> <p>The payment rail is <strong>x402</strong> — USDC on Base. The flow:</p> <p>POST /v1/agent/generate {model, prompt}<br> ← 402 Payment Required</p> <p>x-payment-requirements: {amount: "400000", currency: USDC, chain: base, payTo} → agent signs USDC transfer, retries with X-PAYMENT header ← 200 + result URL (hosted 48h, auto-deleted)</p> <p>One HTTP round-trip pattern. No API key, no account, no session — the payment signature <em>is</em> the credential.</p> <h2> What actually happens inside </h2> <ul> <li>Model catalog with live per-call pricing: <code>GET /v1/agent/models</code> (5s 720p video ≈ $0.40, images ≈ $0.02–0.05)</li> <li>Quote freshness was the annoying part — prices are per-result, so the 402 response carries a short-lived quote the agent must settle before expiry</li> <li>For humans/API keys there's a chat-completions-compatible surface instead, so integrators who want accounting get <code>Authorization: Bearer lp_…</code> and skip the wallet dance entirely</li> </ul> <h2> Failure modes I hit </h2> <ul> <li>Agents that retry the original request <em>without</em> attaching payment — had to make the 402 body self-describing (amount, recipient, expiry, example header) so a generic agent could act on it without me hardcoding the client</li> <li>Wallet-funded agents settling twice on timeout — made fulfillment idempotent on the payment reference</li> <li>The privacy constraint shaped the storage layer: renders live 48h max, never indexed, share links are a separate opt-in path gated by model</li> </ul> <h2> Try it </h2> <ul> <li>MCP endpoint: <code>https://livepairai.com/mcp</code> </li> <li>Agent docs: <code>https://livepairai.com/SKILL.md</code> </li> <li>Manifest: <code>https://livepairai.com/v1/agent/manifest.json</code> </li> </ul> <p>If your agent has a USDC wallet, it can already use this. Curious how others are handling </p> ai mcp api nanobanana