AgentPay
Let coding agents pay for APIs and services under vault-backed keys and spending mandates you define.
Overview
AgentPay is a MCP server for the Build phase that enables governed agent payments, API key vaulting, and mandate-enforced spending limits.
What is this MCP server?
- Governed spend mandates so agents cannot exceed user-defined limits
- API key vaulting so secrets stay out of prompts and local configs
- Streamable HTTP remote at api.agentpay.so plus optional npm stdio transport
- Merchant API key authentication with optional merchant ID attribution
- Supports payment intent flows for agent-initiated purchases
- Server version 0.2.0
- 1 npm package (@agentpayxyz/mcp-server) with stdio transport
- 1 streamable-http remote endpoint
Community signal: 1 GitHub stars.
What problem does it solve?
Solo builders cannot safely let agents hit paid APIs when every run risks leaked keys and uncapped charges.
Who is it for?
Indie builders shipping agents that must purchase API usage, SaaS seats, or metered services under explicit caps.
Skip if: Teams that only need static API keys in .env with no agent autonomy or spend governance.
What do I get? / Deliverables
After install, your agent calls AgentPay tools to spend within vault-backed keys and limits you control.
- MCP tools for agent payment and key-vault operations within defined limits
- Authenticated connection to AgentPay via remote HTTP or local stdio transport
- Configurable merchant attribution and API base URL overrides
Recommended MCP Servers
Journey fit
Payment rails and API vaulting are wired into the product while you connect agent workflows to real billing—not a launch or growth marketing task. This MCP server is the integration layer between Claude Code, Cursor, or Codex and AgentPay’s payment intents, keys, and limits.
How it compares
Payments-focused MCP integration, not a general coding skill or marketplace catalog.
Common Questions / FAQ
Who is AgentPay for?
Solo and indie builders running Claude Code, Cursor, or similar agents who need governed payments and vaulted API keys.
When should I use AgentPay?
Use it while building agent integrations that must call paid third-party APIs without exposing unlimited credentials.
How do I add AgentPay to my agent?
Add the remote MCP URL https://api.agentpay.so/api/mcp or install @agentpayxyz/mcp-server and set AGENTPAY_API_KEY in your client’s MCP config.