Agent Pay
Connect an AI agent to AgentPay so it can discover payment tools, provision access, meter usage, and run reliability checks while you monetize agent features.
Overview
Agent Pay is a MCP server for the Build phase that connects AI agents to the AgentPay gateway for tool discovery, provisioning, metering, and payment reliability controls.
What is this MCP server?
- Agent-facing payment gateway MCP with tool discovery, provisioning, and metering for paid agent workflows
- Reliability tooling (circuit breakers, health metrics, config) when AGENTPAY_ADMIN_KEY is configured
- npm package mcp-server-agentpay with stdio transport (registry version 1.1.2)
- Secrets: required AGENTPAY_GATEWAY_KEY (apg_ prefix); optional AGENTPAY_URL for custom API origin
- Bridges indie agent products to commercial billing without building a payments stack from scratch
- npm identifier mcp-server-agentpay with stdio transport
- Three documented environment variables (one required gateway key)
What problem does it solve?
You are shipping an agent product that must charge or meter usage, but hand-rolling payment APIs and operational guardrails inside every agent session is slow and error-prone.
Who is it for?
Indie builders monetizing MCP-enabled or autonomous agents who already use AgentPay and want stdio tool access from Claude Code, Cursor, or Codex.
Skip if: Founders who only need a static Stripe Checkout link on a landing page with no agent-driven provisioning or metering.
What do I get? / Deliverables
Your agent can call AgentPay MCP tools with gateway credentials so payments, provisioning, and metering flow through a managed gateway instead of bespoke glue code.
- Agent-accessible payment and provisioning tools via MCP
- Metering and gateway-backed billing calls from agent sessions
- Optional reliability monitoring hooks when admin key is configured
Recommended MCP Servers
Journey fit
Payment gateway wiring happens while you integrate external services into the product—canonical Build—rather than at pure idea research or post-launch SEO work. Integrations is the fit because this MCP server fronts a hosted payment API (keys, URLs, gateway tools), not frontend UI or launch distribution.
How it compares
Hosted payment-gateway MCP integration—not an open-source billing UI kit or a generic coding skill.
Common Questions / FAQ
Who is Agent Pay for?
It is for solo builders and small teams running AI agents that must bill, provision, or meter customers through AgentPay’s gateway from an MCP-capable coding agent.
When should I use Agent Pay?
Use it in Build while wiring monetization and third-party payment APIs—after pricing intent in Validate and before you treat payment paths as production-ready in Ship.
How do I add Agent Pay to my agent?
Install the npm package mcp-server-agentpay, set AGENTPAY_GATEWAY_KEY (and optional AGENTPAY_URL / AGENTPAY_ADMIN_KEY), add the server to your MCP client config over stdio, then restart the agent.