X402engine Mcp
Give your agent pay-per-call access to 50+ external APIs—images, LLMs, code helpers, crypto, travel—through one x402 MCP gateway.
Overview
x402engine MCP is a MCP server for the Build phase that exposes 50+ pay-per-call agent APIs through the x402 payment gateway.
What is this MCP server?
- 50+ pay-per-call APIs for agents: images, LLM, code, crypto, travel, and more
- x402 payment protocol with optional X402_PAYMENT_HEADER for automatic settlement
- Configurable gateway via X402_BASE_URL (default https://x402engine.app)
- X402_DEV_BYPASS secret for skipping payments during local testing
- Stdio MCP via npm package x402engine-mcp v1.0.3
- 50+ pay-per-call APIs advertised in server description
- MCP server version 1.0.3
- Default gateway URL: https://x402engine.app
What problem does it solve?
Agents need many external APIs, but managing separate keys, billing, and wrappers for each service slows solo shipping.
Who is it for?
Builders prototyping agent features that need varied paid APIs (media, LLM, travel, crypto) with usage-based spend.
Skip if: Products that require fixed enterprise contracts, strict data residency, or zero per-request API fees.
What do I get? / Deliverables
Your agent calls a single MCP-backed gateway with x402 payments instead of hand-wiring dozens of integrations.
- Agent-callable access to 50+ categorized pay-per-call APIs via MCP
- Centralized x402 billing instead of per-vendor agent wiring
- Faster integration prototypes for multi-capability agent features
Recommended MCP Servers
Journey fit
Bundled paid APIs land in Build because solo builders wire capabilities into products and agent workflows during implementation, not at idea stage. Integrations subphase is the right shelf for a unified MCP façade over many third-party HTTP APIs and payment headers.
How it compares
Paid API marketplace over MCP, not a free local tool skill or self-hosted open-source model runner.
Common Questions / FAQ
Who is x402engine-mcp for?
Solo builders and indie hackers shipping agent-powered apps who want many paid APIs behind one MCP and x402 billing flow.
When should I use x402engine-mcp?
Use it during build when your agent needs external capabilities (images, LLM, code, travel, crypto) and pay-per-call is acceptable.
How do I add x402engine-mcp to my agent?
Install x402engine-mcp from npm, configure stdio MCP in your agent, set X402_BASE_URL and payment env vars (or X402_DEV_BYPASS for tests), then call gateway tools from the agent.