ATXP — Agent Payment & Wallet Infrastructure
Give your coding agent a funded wallet plus pay-as-you-go access to search, media generation, email, SMS, and voice without wiring each API separately.
Overview
ATXP is a MCP server for the Build phase that gives coding agents a wallet and bundled paid tools for search, generative media, email, SMS, and voice over one stdio connection.
What is this MCP server?
- Agent wallet and USDC-style pay-as-you-go billing described as payment infrastructure for autonomous agents
- 41 paid tools in one server: web search, image, video, and music generation
- Email, phone, SMS, voice calls, and contacts for agent identity and outreach
- stdio npm package with ATXP_CONNECTION secret from npx atxp agent register or accounts.atxp.ai
- Registry version 1.21.x with keywords positioning it as Stripe-like infrastructure for AI agents
- 41 paid tools advertised in the catalog description
- Server schema version 1.21.2 with npm package identifier atxp
- stdio transport with one required secret env ATXP_CONNECTION
What problem does it solve?
Solo builders waste days stitching billing, identity, and dozens of vendor APIs when their agent only needs to search, generate media, and message users.
Who is it for?
Indie builders shipping autonomous or semi-autonomous agents that need metered access to search, media APIs, and real-world contact channels from Claude Code.
Skip if: Teams that only need free local dev tools, refuse pay-as-you-go agent spend, or want a single-purpose MCP with no wallet layer.
What do I get? / Deliverables
After you register and set ATXP_CONNECTION, your agent can call wallet-backed tools from the MCP host without maintaining separate payment and API integrations for each capability.
- Wallet-backed MCP tool access for search, media, email, SMS, and voice
- Single stdio integration instead of many separate vendor MCP entries
- Agent identity and contacts surfaced through registry-defined tools
Recommended MCP Servers
Journey fit
ATXP is infrastructure you wire into the agent during product build so autonomous workflows can pay and call external capabilities from one MCP connection. Integrations is the canonical shelf because the server’s value is connecting Claude Code or Cursor to wallet, identity, and dozens of billed third-party tools over stdio MCP.
How it compares
MCP payment and multi-tool gateway, not a workflow skill or static documentation pack.
Common Questions / FAQ
Who is ATXP for?
ATXP is for solo and indie builders who run Claude Code, Cursor, or other MCP clients and want one funded agent identity with many paid capabilities behind a single connection string.
When should I use ATXP?
Use ATXP during Build when you are wiring agent integrations and need search, generative media, email, SMS, or calls without implementing Stripe and each vendor API yourself.
How do I add ATXP to my agent?
Install the npm stdio package atxp, run agent registration to obtain ATXP_CONNECTION, add the server to your MCP config with that secret env var, and restart the host.