Awesome Agentic AI Payments Awesome

English | 简体中文

New: can you make an AI agent overspend? Try our open challenge against the sandbox (test money only): overspend-challenge

A curated list of protocols, MCP servers, wallets, spending controls and research for letting AI agents make payments safely.

Maintained by the team behind Pink Agentic AI Payments (PinkWallet); entries are selected on merit and include competitors.

Every link below was fetched directly and confirmed live on 2026-09-29 (see link-check.csv in this repo for the full audit trail). Every description is sourced from the linked page itself — see the same file for exactly which URL each description came from.

See also: Agentic Payments Timeline (2024–2026): 30 dated, source-linked events from MCP's release to the x402 Foundation.

See also: agentic-ai-payments — an open developer guide to agentic AI payments (protocols, providers, spending controls, sandbox quickstart), maintained by the same team.

Contents

Protocols & Standards

  • a2a-x402 — An extension that wires Google's Agent Payments Protocol (AP2) to the x402 protocol for stablecoin settlement, built "in collaboration with Coinbase, Ethereum Foundation, MetaMask and other leading organizations" to give "a production-ready solution for agent-based crypto payments."
  • Agent Payments Protocol (AP2) — Uses "Mandates — tamper-proof, cryptographically-signed digital contracts that serve as verifiable proof of a user's instructions." Donated by Google to the FIDO Alliance on 2026-04-28; the announcement says the move "ensures AP2 remains platform-agnostic and community-led." Apache-2.0.
  • Agentic Commerce Protocol (ACP) — "An interaction model and open standard for connecting buyers, their AI agents, and businesses to complete purchases seamlessly." Co-developed by Stripe and OpenAI; the reference repo's README states the spec "is maintained by OpenAI and Stripe and is currently in beta." Apache-2.0.
  • Machine Payments Protocol (MPP) — "MPP lets agents pay for services on the web, extensible to any payment method." Announced by Stripe on 2026-03-18, "co-authored by Tempo and Stripe." SDKs in TypeScript, Python, Rust, Go and Ruby.
  • Mastercard Agent Pay — Announced 2025-04-29. "Consumers will have complete control over what the agent is allowed to purchase on their behalf." Built on Mastercard's existing tokenization used for mobile contactless payments and card-on-file.
  • Universal Commerce Protocol (UCP) — "Specification and documentation for the Universal Commerce Protocol (UCP)." Announced 2026-01-11 by Google "in collaboration with industry leaders including Shopify, Etsy, Wayfair, Target, and Walmart," and "compatible with Agent Payments Protocol (AP2)." Apache-2.0.
  • Visa Trusted Agent Protocol (TAP) — Announced 2025-10-14, developed with Cloudflare, with Visa crediting "insightful feedback from other early partners including Adyen, Ant International, Checkout.com, Coinbase, CyberSource, Elavon, Fiserv, Microsoft, Nuvei, Shopify, Stripe and Worldpay." A cryptographic message-signing standard (RFC 9421) merchants use to verify an agent's identity before checkout; it does not itself move money.
  • x402 — "An open-source protocol that turns the dormant HTTP 402 Payment Required status code into a fully-featured, onchain payment layer for APIs, websites, and autonomous agents." Operational under Linux Foundation governance since 2026-07-14 as the x402 Foundation, with 40 member organizations. Apache-2.0.

Payment MCP Servers

Official vendor MCP servers whose own documentation describes tools that create or move payment objects (refunds, payouts, orders, payment links).

  • Adyen MCP server — Local-only server covering Adyen's Checkout API and Management API; labeled alpha on its GitHub repo. Example prompts on the docs page: "Refund order #12345" and "Create a €50 payment link for order #ABC789."
  • Checkout.com MCP Server — Hosted server (separate sandbox and production endpoints) described as a "production-ready source of truth," with tools including Create/Get Payment Link, Get Payment Details, List Entities and Voids. Access is scoped: "you can only perform payment operations that your Dashboard user has permissions to action."
  • Mollie MCP Server — Remote server (mcp.mollie.com/mcp) covering Payments, Payment links, Customers, Subscriptions, Mandates, Captures, Balances and Settlements; users authenticate via Mollie's own OAuth 2.0 browser login rather than entering an API key into the AI tool.
  • PayPal Agent Toolkit & MCP Server — Local (npx -y @paypal/mcp) or remote MCP server; environment can be set to SANDBOX or PRODUCTION. Documented tools include create_invoice, create_order and create_refund.
  • Razorpay MCP Server — Hosted or self-hosted (Docker) server with 35+ tools including capture_payment, create_refund and create_instant_settlement; supports a READ_ONLY flag to restrict the server to read-only operations.
  • Square MCP Server — Hosted (mcp.squareup.com/mcp) or local server giving access to "customers, orders, items, and more" across the Square API. Square "maintains an allowlist of MCP clients in order to protect against malicious client registration attempts." Currently in Beta.
  • Stripe MCP Server — Hosted (mcp.stripe.com) or local server exposing generic API read/write tools. Sensitive writes such as refunds and outbound payments require human confirmation via a URL that expires after 24 hours if unapproved. From 2026-10-31, "Stripe MCP no longer accepts full-access secret keys or restricted API keys without the Agent tag."

Agent Wallets & Payment Infrastructure

  • Airwallex AgentOS — CLI plus MCP connector for a production Airwallex account. "AgentOS components do not initiate money-out actions (transfers, FX conversions, or payouts) on your behalf" by default; write tools require explicit confirmation.
  • Circle Agent Wallets — Lets developers "set USDC spending limits for outbound transfers and x402 payments," with limits that "can be time-bound," plus wallet/contract allow- and blocklists and sanctions screening before onchain submission.
  • Coinbase Agentic Wallet / AgentKit — Wallet CLI for AI agents to hold and send USDC, with "configurable caps per session and per transaction" and automatic OFAC sanctions-list screening on all transfers.
  • Crossmint Agent Checkouts — Remote MCP server (create-order, check-order, get-usd-balance) that executes real purchases once the environment variable is switched from test to prod. Per the checkout MCP server's README, the item is delivered with expedited shipping, a receipt is generated and sales tax is collected.
  • Locus — "One Account for Every AI Agent Tool": gives "an AI agent one connection to a catalog of paid APIs and proprietary data sources," used "from one balance instead of relying on separate provider accounts, subscriptions, and API keys."
  • Payman (Genie) — A local stdio bridge to Payman's remote Genie MCP server, authenticated via OAuth 2.0 with PKCE. The official README documents an ask_genie natural-language tool plus self-service account-management tools; it does not itemize payment-execution tools.
  • Pink Agentic AI Payments — "The approval layer between AI agents and company money: plain-language rules, per-agent budgets and human approvals decide each payment before a one-time card or bank transfer is issued." Live sandbox at agentic-sandbox.pinkwallet.com (test credentials only, no money moves; production not yet available); MCP endpoint https://agentic-sandbox.pinkwallet.com/mcp with 7 tools (pink.get_budget, pink.list_payees, pink.list_rules, pink.check_policy, pink.request_payment, pink.get_credential, pink.report_receipt); listed in the official MCP Registry as com.pinkwallet/agentic-payments-sandbox. Runnable examples: sandbox-examples. (disclosure: maintained by the same team)
  • Skyfire (KYA / KYAPay) — Identity-plus-payment token protocol: "each buyer agent has a wallet, funded by the user," which presents signed JWT tokens (kya, pay, kya-pay) to seller MCP servers, APIs or websites to transact.
  • Tempo Wallet CLI — Command-line wallet where "each wallet can have multiple access keys with independent spending limits." --max-spend "stop[s] if the request would exceed a spend cap," and --dry-run previews cost and validates a request before committing funds.

Spending Controls & Guardrails

Products and libraries whose primary purpose is enforcing a budget, allowlist or approval step in front of agent payments — independent of any one payment rail.

  • agent-verifier-mcp — "MCP server for AI agent spending limits. One config change to add budget enforcement." Implements a Budget Authority Protocol (create_budget, check_budget, settle, release, refund) that is explicitly rail-agnostic: "works with x402, credit cards, MPP, bank transfers."
  • Authoryze — "The authorization and control layer for AI agent payments." Tagline: "Your agent asks. Your rules decide. Approved purchases get a single-use card." Note: this is the live site that the domain agentpays.dev (a name found in third-party MCP directories) now redirects to (HTTP 308, checked 2026-09-29); we could not confirm anywhere whether the two names refer to the same company.
  • PayAgents — "Payment Orchestration for AI Agents & MCP Servers." Policy-controlled wallet for Bitcoin Lightning (L402) and Base-chain USDC (x402) payments, with per-transaction, per-day and per-30-day spend caps, destination allow/denylists and an audit trail.
  • PolicyLayer — "The system of record for AI agent authority." Acts as a proxy in front of any MCP server, evaluating every tools/call request against a YAML policy file and forwarding, blocking, rate-limiting, or routing it to a human for approval.
  • SpendNod — "Open-source authorization gateway for AI agents." MIT-licensed and self-hosted; agents call an authorize_transaction tool before every purchase, checked against spending thresholds, vendor blocklists, daily caps and category rules.

SDKs, Examples & Tutorials

Runnable code, not just specs.

  • Coinbase AgentKit — "Every AI Agent deserves a wallet." Open-source SDK for giving AI agents an onchain wallet and payment actions.
  • Locus Pro Plugin — Official plugin whose README recommends agents "quote significant calls with estimate_cost first, and to confirm with you before unusually large spends," and notes "spend limits and approvals are configured per workspace in the dashboard."
  • MPP Quickstart — "Get started with MPP in minutes" — official quickstart for the Machine Payments Protocol, with SDKs in TypeScript, Python, Rust, Go and Ruby.
  • Pink agent-spending-limit-example — "Runnable example: enforce an AI agent's spending cap, allowlist, approval threshold and idempotency BEFORE a payment executes (Node, no deps)." (maintained by the list authors)
  • x402 Inspector — Static browser tool that "decodes and lints x402 payment headers" (PAYMENT-REQUIRED, X-PAYMENT/PAYMENT-SIGNATURE, PAYMENT-RESPONSE); it flags issues such as malformed payTo, missing EIP-712 extra and expired EIP-3009 authorizations. Runs locally with "no backend and no tracking."
  • x402 Quickstart for Buyers — "This guide walks you through how to use x402 to interact with services that require payment," including wallet signer setup across EVM, Solana, Aptos and Algorand.
  • x402 Quickstart for Sellers — "This guide walks you through integrating with x402 to enable payments for your API or service," including framework-specific middleware for Express, Next.js, Hono, Fastify, Go and Python.

Research, Reports & Datasets

  • AP2 announcement (Google Cloud) — Google Cloud's announcement of the Agent Payments Protocol, explaining that an Intent Mandate "provides the auditable context for the entire interaction" and a Cart Mandate "creates a secure, unchangeable record of the exact items and price."
  • AP2 joins FIDO Alliance (Google) — Google's 2026-04-28 announcement that transitioning ownership to the FIDO Alliance "ensures AP2 remains platform-agnostic and community-led."
  • Agent Spending Controls Crosswalk — Vendor-neutral crosswalk of how 14 payment providers and protocols cap AI agent spending: 43 quoted rows covering exact field names, units, and enforcement points, each sourced to a verbatim quote (CC BY 4.0). (maintained by the list authors) · Hugging Face
  • Agentic Commerce Protocol announcement (Stripe) — Stripe and OpenAI's announcement of ACP, describing it as enabling "programmatic commerce flows between buyers, AI agents, and businesses" while the business "is the merchant of record."
  • Machine Payments Protocol announcement (Stripe) — Stripe's 2026-03-18 announcement of MPP, "co-authored by Tempo and Stripe," supporting "stablecoins as well as fiat with cards and buy now, pay later payment methods via Shared Payment Tokens (SPTs)."
  • Pink agent-spending-policy — Draft v0.1 vendor-neutral JSON Schema for an AI agent's spending policy (caps, allowlists, approval thresholds), field-by-field mapped to 14 payment providers' native settings, cited against the crosswalk. Not a standard (CC BY 4.0 docs / Apache-2.0 code). (maintained by the list authors)
  • Pink agentic-payments-readiness — "Can AI agents actually pay? 16 payment providers scored on 7 agent-readiness dimensions, evidence-linked (CC BY 4.0)." 228 total checks, each with an evidence URL, direct quote and access date. (maintained by the list authors) · Hugging Face
  • Universal Commerce Protocol announcement (Google) — Google's 2026-01-11 announcement of UCP as "an open-source standard designed to power the next generation of agentic commerce," developed with Shopify, Etsy, Wayfair, Target and Walmart.
  • x402 Foundation operational launch (Linux Foundation) — Announcement that x402 governance moved to the Linux Foundation: "40 organizations have joined as members," including Premier members Adyen, AWS, American Express, Circle, Coinbase, Google, Mastercard, Shopify, Stripe and Visa.

Articles & Guides

  • Managing agent spend (MPP) — Official guide on layering spending controls on top of MPP payments using Tempo access keys, with a worked example: a key that "can spend up to 10 USDC per day and only transfer USDC to one recipient."
  • OpenAI Commerce docs — "The infrastructure between merchants and shoppers in ChatGPT," covering the Agentic Commerce Protocol (ACP) as "an open standard that serves as the connective layer between merchants and ChatGPT users."
  • Stripe Agentic Commerce docs — "Agentic commerce uses AI agents to support transactions between buyers and sellers, and to let agents transact on behalf of the people they serve," covering both selling through agents (UCP/ACP) and accepting machine payments (MPP/x402).
  • UCP merchant integration guide (Google) — "The Universal Commerce Protocol (UCP) is an open standard designed for the future of commerce, empowering you to turn AI interactions into instant sales," using an existing Merchant Center account's shopping feeds.
  • x402 vs AP2 vs ACP: Which Agent Payment Protocol Should You Build On? — "x402, AP2 and ACP solve different layers of AI agent payments: pay-per-request stablecoin settlement, proof of user authorization, and in-chat checkout." (maintained by the list authors)

Contributing

Pull requests welcome. To be added, a link must be:

  • Public — no login wall to read the page that's being linked.
  • Working — resolves with a normal HTTP 200 (or a redirect that ends in one) at the time you submit.
  • Relevant — about AI agents making payments: a protocol, an MCP server or SDK that touches payments, a spending-control/guardrail product, or research/analysis about agent payments specifically (not general fintech or general AI agent tooling).
  • Backed by a quote from the linked page itself — no marketing paraphrase, no claims the source page doesn't make.

Open a PR adding your entry in the correct alphabetical position within its section, with a one-line, factual, non-promotional description sourced from the page you're linking. If you work at a company being described and think a line is wrong or out of date, please say so in the PR — corrections are welcome and will be re-verified against your own page.

License

CC0

To the extent possible under law, the list authors have waived all copyright and related or neighboring rights to this work. See LICENSE (CC0-1.0).

Description
A curated, link-verified list of protocols, MCP servers, agent wallets, spending controls, and research for AI agents that make payments. Maintained by Pink Agentic AI Payments.
Readme CC0-1.0 75 KiB
Languages
Markdown 100%