X402 Market
Pay per HTTP API call on Base mainnet through x402 from an agent using the pay_and_call MCP tool.
Overview
io.github.AsaiShota/mcp-server is a MCP server for the Build phase that lets AI agents pay-per-call for HTTP APIs via x402 on Base mainnet using pay_and_call.
What is this MCP server?
- Single primary tool pay_and_call for x402 pay-per-call HTTP APIs
- Base mainnet default chain ID 8453 with configurable RPC
- Read-only marketplace tools work without MCP_BUYER_PRIVATE_KEY
- Funded buyer wallet private key required for paid calls
- npm @x402-market/mcp-server v0.2.0-alpha.1 over stdio
- One primary spending tool: pay_and_call
- Default BASE_CHAIN_ID 8453 (Base mainnet); 84532 documented for Base Sepolia
- Server version 0.2.0-alpha.1; default MARKET_API_URL points to x402-market-api worker deployment
What problem does it solve?
Agents can call free APIs easily but lack a standard, wallet-native way to buy metered third-party HTTP access in one tool invocation.
Who is it for?
Technical solo builders shipping agent features that must consume paid, marketplace-listed HTTP APIs on Base with explicit spend caps.
Skip if: Non-crypto products, teams uncomfortable storing funded wallet keys in dev environments, or builders who only need free static REST keys.
What do I get? / Deliverables
Registering x402-market MCP enables pay_and_call flows so agents can settle x402 charges and execute paid HTTP endpoints on Base without bespoke payment code per API.
- Agent-executed paid HTTP API calls via x402 settlement
- Marketplace discovery using read-only tools without a private key
- Configurable RPC and max-price guardrails for integration testing and production
Recommended MCP Servers
Journey fit
Micropayment-gated API access is wired while you integrate external paid capabilities into agent products—not during passive research. x402-market is an agent-to-HTTP integration layer with wallet-backed pay_and_call, squarely in build integrations.
How it compares
x402 micropayment HTTP bridge MCP, not a traditional API key vault or cloud deploy skill.
Common Questions / FAQ
Who is io.github.AsaiShota/mcp-server for?
Developers building agent products who want Base mainnet x402 pay-per-call access to marketplace HTTP APIs from MCP clients.
When should I use io.github.AsaiShota/mcp-server?
Use it while integrating paid external APIs into an agent workflow where per-call x402 settlement on Base is acceptable and you can fund a buyer wallet.
How do I add io.github.AsaiShota/mcp-server to my agent?
Install @X402 Market/mcp-server via npm, configure stdio MCP, set MARKET_API_URL and optional BASE_RPC_URL, BASE_CHAIN_ID, MCP_MAX_PRICE, and MCP_BUYER_PRIVATE_KEY when you need pay_and_call spending.