AgentPays MCP
AgentPays is a MCP server that gives AI agents governed spending via rules, approvals, and single-use virtual cards.
About
AgentPays is an MCP server that exposes payment infrastructure tuned for AI agents: spending limits, human-in-the-loop approvals, and disposable virtual cards. developers shipping agent products or internal automations that need to buy APIs, domains, or SaaS on behalf of a bot install it during the build phase when wiring integrations. Instead of handing agents a real card or building Stripe flows from scratch, you register the remote endpoint and let the model request spend inside policy. OAuth covers Claude and ChatGPT clients; other agents use a Bearer agent API key. It fits teams who want financial guardrails before they scale autonomous purchasing in validate-to-operate workflows, without replacing your full billing stack for customer checkout.
- Spending rules and approval flows so agents cannot exceed budgets you define
- Single-use virtual cards for isolated checkout sessions
- Remote MCP at agentpays.dev with Bearer API key or OAuth on Claude Desktop, Claude.ai, and ChatGPT
- Streamable HTTP transport (MCP schema 2025-12-11), version 1.0.0
- Purpose-built payment infrastructure for AI agents, not generic card widgets
AgentPays MCP by the numbers
- Data as of Aug 10, 2026 (Skillselion catalog sync)
claude mcp add --transport http agentpays https://agentpays.dev/api/mcp --header "Authorization: Bearer YOUR_TOKEN"Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | Required |
What it does
Wire governed payments into agent workflows so autonomous tools can spend within rules instead of sharing your main card.
Who is it for?
Best when you're prototyping or shipping agents that need to autonomously pay for APIs, tools, or one-off purchases with caps and approvals.
Skip if: Skip if you only need human checkout on a marketing site or a full merchant-of-record stack without any agent spend surface.
What you get
After you add the remote MCP, your agent can initiate purchases inside spending rules and approval flows instead of bypassing your wallet.
- Remote MCP connection to governed agent payment APIs
- Ability to issue single-use virtual cards under configured rules
- Approval-gated spend paths the agent can invoke from the IDE
By the numbers
- MCP server version 1.0.0
- One streamable-http remote: https://agentpays.dev/api/mcp
- Schema: MCP server.schema.json 2025-12-11
Recommended MCP Servers
$THREE Token MCPPrice, hold, and burn $THREE on Solana — the first MCP server whose actions burn a token.91
402 MCPAI agents discover, pay for, and consume any Lightning-gated API autonomously
9192 Public Compute MCPRemote MCP for 9192 discovery, pricebook, payment rails, GET_PULSE quotes, and receipt checks.
Aarna MCPAarna - 34 tools for swap quotes, liquidity pools, and trading dataAave MCPAave - 6 tools for lending rates, supply, and borrow data
AbraFlexi MCPMCP server for AbraFlexi ERP — invoices, contacts, products, bank transactions.1How it compares
Agent-governed spend MCP, not a storefront payment skill or generic Stripe checkout tutorial.
FAQ
Who is dev.agentpays/agentpays for?
and developers who run Claude Code, Cursor, or similar agents and need safe, policy-bound purchasing during product development.
When should I use dev.agentpays/agentpays?
Use it while building agent integrations whenever the agent must pay vendors under limits, not when you are only validating ideas without real spend.
How do I add dev.agentpays/agentpays to my agent?
Register the streamable HTTP remote https://agentpays.dev/api/mcp with Authorization Bearer your agent API key, or use OAuth where the host supports it.