Agent X402 Paywall MCP
Agent x402 Paywall MCP is a MCP server that integrates Coinbase x402 HTTP 402 pay-per-call payments so agents can access metered APIs without a Stripe merchant setup.
About
Agent x402 Paywall MCP exposes Coinbase’s x402 pattern—HTTP 402 Payment Required—through Model Context Protocol so coding agents can complete paid API calls without you standing up a classic Stripe checkout first. developers shipping agent-callable tools, micro-APIs, or research endpoints can gate usage with per-request payment semantics that machines understand, which matters when your customer is another agent rather than a browser session. The server runs over stdio from the published PyPI package and slots into Claude Code, Cursor, or other MCP clients as a payment integration layer. It does not replace legal, tax, or treasury operations; it focuses on the technical handshake between an agent client and a 402-gated resource. Use it when you are building or validating monetized agent access paths, especially if x402 fits your stack better than card-on-file flows aimed at humans.
- Wraps Coinbase x402 HTTP 402 pay-per-call for agent consumers
- Designed for agents paying per call without a traditional Stripe account
- stdio MCP via PyPI package agent-x402-paywall-mcp v1.0.2
- Fits API products that expose machine clients instead of only human checkout
- Local MCP process for agent hosts that support stdio servers
Agent X402 Paywall MCP by the numbers
- Data as of Aug 10, 2026 (Skillselion catalog sync)
claude mcp add agent-x402-paywall-mcp -- uvx agent-x402-paywall-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | agent-x402-paywall-mcp |
|---|---|
| Transport | STDIO |
| Auth | None |
What it does
Let agents pay for metered API calls via Coinbase x402 (HTTP 402) without setting up a full Stripe merchant flow.
Who is it for?
Best when you're creating agent-consumable paid APIs or internal tools and want x402-style per-request payment from MCP-enabled coding agents.
Skip if: Products that only need standard Stripe Checkout for human subscribers with no HTTP 402 or agent payment flow.
What you get
Your agent can satisfy HTTP 402 payment requirements on gated endpoints through MCP, enabling per-call monetization aligned with x402 rather than full Stripe onboarding.
- MCP-mediated x402 pay-per-call handling for agent API requests
- Integration path that avoids a traditional Stripe merchant account for machine clients
- stdio server agent-x402-paywall-mcp v1.0.2
By the numbers
- MCP server version 1.0.2
- 1 PyPI package with stdio transport
- Registry identifier: agent-x402-paywall-mcp
Recommended MCP Servers
$THREE Token MCPPrice, hold, and burn $THREE on Solana — the first MCP server whose actions burn a token.91
402 MCPAI agents discover, pay for, and consume any Lightning-gated API autonomously
9192 Public Compute MCPRemote MCP for 9192 discovery, pricebook, payment rails, GET_PULSE quotes, and receipt checks.
Aarna MCPAarna - 34 tools for swap quotes, liquidity pools, and trading dataAave MCPAave - 6 tools for lending rates, supply, and borrow data
AbraFlexi MCPMCP server for AbraFlexi ERP — invoices, contacts, products, bank transactions.1How it compares
MCP payment bridge for x402, not a hosted billing dashboard or storefront skill.
FAQ
Who is agent-x402-paywall-mcp for?
It is for developers building APIs or services paid per call by agents, using Coinbase x402 instead of a full Stripe merchant stack.
When should I use agent-x402-paywall-mcp?
Use it while integrating monetized endpoints into an agent workflow—when responses return HTTP 402 and the client must pay before retrying the call.
How do I add agent-x402-paywall-mcp to my agent?
Install agent-x402-paywall-mcp from PyPI, register it as a stdio MCP server in your agent host, and configure x402 wallet or payment settings required by your Coinbase x402 setup.