Head to head · x402 payments · October 2026 research run

Payman Genie MCP vs Stripe API + MCP

Stripe API + MCP scores 85 (AA) on agent readiness against Payman Genie MCP's 47.1 (D), and leads in every scored category. Both do x402 payments.

Best payment and monetisation platforms for AI agents · All 104 platforms comparisons

Which one, for what

Payman Genie MCP D

Best for A person or small business who wants an assistant to pay bills, issue one-time cards or pay x402 APIs within hard limits.

Also in its favour

  • Free to start without a card

Watch for

No published pricing, status page, rate limits or changelog

Stripe API + MCP AA

Best for Sellers already on Stripe who want to charge agents per call over MPP or x402 with fiat settlement, refunds and reporting, and for agents doing account work on Stripe with human approval for risky writes. nevermined suits sellers who want plans, credits and buyer-side caps; tempo is the chain MPP stablecoin payments settle on.

Ahead on

  • Reliability, 78 against 25
  • Schema & documentation, 90 against 56
  • Agent ergonomics, 91 against 68
  • Security & auth, 97 against 80
  • Payments & pricing, 66 against 34
  • Maintenance & community, 82 against 30
  • Transparency & trust, 87 against 46

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source
  • Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
  • No incidents deducted, where Payman Genie MCP loses 3 points for them

Watch for

Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Stripe API + MCP +53

Payman Genie MCP 25

No status page found for Genie or Payman (0), so no incident history to read (5). No rate limits published (0). The developer page says to retry an error only after NOTHING_RAN or BUSY and never after OUTCOME_UNKNOWN, which is safe-retry guidance for money-moving calls, but there's no 429 or Retry-After behaviour (12 of 15). No SLA (0). Genie is sold as a live product with no beta label, while the stdio bridge is at 0.4.0 (8 of 10). Per the 1 October check, not re-read on 4 November (paymanai.com hosts are paused on the terms of 1 November 2026). 0+5+0+12+0+8 = 25.

Stripe API + MCP 78

Status page at status.stripe.com, whose feed link resolves to Stripe's Statuspage history at www.stripestatus.com with components for the Stripe API, core components and payment methods (20). The 90 days to 1 November run from 3 August, so the 24 July incident (64 minutes of elevated API error rates and response times, our one major on 17 October) has left the window. In the window, 22 September (elevated errors on account and capability calls, 19:13 to 22:19 UTC, marked no impact) stays partial, 27 September (a vendor-marked major of 29 minutes, 00:32 to 01:01 UTC) stays minor by our line, the other Stripe API incidents read on 17 October ran 3 to 37 minutes, except 6 August, when retrieving balance transactions for automatic payouts returned elevated errors from 13:45 to about 16:20 UTC. That one hit a single group of calls, so it reads as partial, and its times come from a third-party tracker's copy of Stripe's notice, not Stripe's own page. The status page read on 1 November shows, from 17 to 31 October, elevated Issuing API errors on 28 October for cards created or updated between 17:13 and 17:54 UTC (fully resolved 20:41), which hit one product's endpoints and so reads as partial like 22 September, and otherwise partner payment methods (Revolut Pay, PayByBank, Bancontact, BLIK) and scheduled maintenance. Minor incidents only (20). We didn't re-read the 3 August to 16 October incident pages on 1 November, and rely on the 17 October readings checked by the verifier. Rate limits published, 100 requests a second in live mode, 25 in a sandbox, 25 per endpoint, plus per-resource limits (15). Every 429 carries a Stripe-Rate-Limited-Reason header, the docs prescribe exponential backoff with jitter, lock timeouts are retried by the SDKs, and the API takes idempotency keys with a dedicated idempotency_error, per the 17 October check, not re-read on 1 November (15). The pricing page, re-read on 1 November, cites 99.999% average historical uptime, which is a record rather than a commitment, and we found no SLA (0). The API, MCP server and machine payments are live, while stripe_analytics and the five Treasury tools are marked preview (8 of 10). 20+20+15+15+0+8 = 78.

Maintenance & community Stripe API + MCP +52

Payman Genie MCP 30

The bridge's newest tagged release is v0.2.1 (14 September 2026), 51 days before 4 November (20). Since 6 August the repository has two tagged releases, v0.2.0 and v0.2.1, both on 14 September; the 0.3.0 and 0.4.0 version bumps of 18 September carry no tag or changelog entry, so they don't count as releases, and no commit has landed since 18 September (0). Two merged pull requests and no changelog. The older developer platform looks abandoned, with docs.paymanai.com failing on a Cloudflare 526 and the payman-ts SDK last released on 18 September 2025, per the 1 October check, not re-read on 4 November (5). No current SDK, and the official MCP registry wasn't read first-hand (0). A Node test suite with a fake authorisation server, but no CI workflow in the repository (5). 20+0+5+0+5 = 30.

Stripe API + MCP 82

API version 2026-10-28.endive released on 28 October 2026, additive in the GA channel, and the OpenAPI repo updated for it on 29 October (30). Dated API versions and spec updates every few days through the last 90 days (20). Public Developer Changelog, support, and 81 commits to stripe/ai in the 90 days to 1 November, most of them daily skill syncs; we didn't read the issue queue (14 of 15). com.stripe/mcp is in the official registry, but the entry is still version 0.2.4 from 28 October 2025 and points at the old stripe/agent-toolkit repo name, although server.json in stripe/ai names the new repo and version 0.3.3 (12 of 15). On npm, @stripe/mcp 0.3.3 from 24 March 2026 is still the newest on 1 November, and @stripe/agent-toolkit 0.9.0 and stripe-agent-toolkit 0.7.0 on PyPI are per the 17 October and 4 October checks. CI runs on every pull request with actions pinned to commit SHAs (6).

Transparency & trust Stripe API + MCP +41

Payman Genie MCP 46

Bridge under MIT, Genie closed under published terms (updated 1 November 2026) and an API licence (15). Privacy policy updated 21 September 2026 names Payman AI, Inc. in Durango, Colorado, gives no retention periods and no DPA, and says anonymised or aggregated data is used to train AI models (12). No deprecation notice for the old developer platform even though its docs no longer load (0). Stripe, Google and unnamed identity-verification and credit-bureau providers are named, with transfers "including the United States" (6). The privacy policy is per the 1 October check, not re-read on 4 November. 15+12+0+6 = 33.

Stripe API + MCP 87

stripe/ai and stripe/openapi are MIT and the service is closed under published terms (18). The security page links the privacy policy, Privacy Center and DPA, states a data-retention policy without periods, and cites EU-US, UK and Swiss Data Privacy Framework participation and CBPR and PRP certifications (24). Dated API versions with an upgrade guide, and the MCP key change was announced in advance, with its date since moved from 31 October to 30 November 2026 (18). The sub-processor list, last updated 27 September 2026 per the 17 October check and not re-read on 1 November, names each provider with the data it handles, the purpose and the entity country, and Business Users can subscribe to change notices with 30 days to object. It gives entity countries rather than where data is processed (18 of 20).

Schema & documentation Stripe API + MCP +34

Payman Genie MCP 56

Five MCP tools, but the server is closed and ask_genie takes a free-text request by design, so the contract is thin (15 of 25). No llms.txt; the bridge README has a Markdown "For agents" section (3). The developer page states what each status means and what the caller should do next, including to stop on needs_approval and not to rephrase after refused (16). One free-text field plus optional context and conversation, no enums (6). Five statuses and three retry codes documented with the action for each (13). No changelog or versioning beyond the bridge's git history (3). Per the 1 October check, not re-read on 4 November (paymanai.com hosts are paused on the terms of 1 November 2026).

Stripe API + MCP 90

Public OpenAPI 3 spec in stripe/openapi (MIT), regenerated for API version 2026-10-28.endive on 29 October (25). The 431-path count is from 30 September and wasn't recounted. llms.txt and every page as Markdown, also readable through stripe docs in the CLI (10). The MCP page, re-read on 1 November, describes each of its fifteen tools and warns about prompt injection when mixing servers, though the generic read and write tools leave method choice to the agent (15). The API is fully typed with enums, but stripe_api_write takes any POST, PATCH, PUT or DELETE method, so the MCP contract is looser than the API's (10). Examples for every endpoint and documented error types (15). Dated API versions pinned per request with Stripe-Version, and a public Developer Changelog (15).

Payments & pricing Stripe API + MCP +32

Payman Genie MCP 34

Payment platforms and wallets take the highest step that applies on the 40-point protocol line. 40 for x402, MPP or L402 on all their own endpoints, 30 on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, 0 for only a protocol of their own. Genie pays x402 APIs from a daily agent budget the owner sets, the buyer step (15 of 40). Payman has no way to accept x402 or MPP, and Genie itself isn't paid over either. No price list for Genie anywhere we looked (0). Free signup with no card or bank details (20). A person signs up and signs in through a browser (0). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 15 of 40 is 3.75 of 10, and the other lines' 20 is 30 at 30 each, so 35 is 34.

Stripe API + MCP 66

Payment platforms and wallets take the highest step that applies on the 40-point protocol line. 40 for x402, MPP or L402 on all their own endpoints, 30 on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, 0 for only a protocol of their own. Stripe merchants can accept MPP (cards through shared payment tokens, USDC.e on Tempo, USDC on Solana) and x402 (USDC on Base) on their own endpoints, settled to the Stripe balance, while Stripe's own API and MCP server aren't paid over either, so the merchant step (25 of 40). Per-unit prices published without a login, 2.9% plus 30 cents for US cards, 1.5% for stablecoins, $0.15 per shared payment token issued, 0.7% of Billing volume (20). No setup or monthly fees and free sandboxes, so nothing needs a card to start (20). A person creates the Stripe account and connects the MCP client (0). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 25 of 40 is 6.25 of 10, and the other lines' 40 is 60 at 30 each, so 65 is 66.

Agent ergonomics Stripe API + MCP +23

Payman Genie MCP 68

One money tool and four small self-service tools (get_genie_agent, rename_genie_agent, grant_genie_read_access, request_genie_access) (25). Answers are natural-language messages with no size or filter controls (5). The status field (done, needs_input, needs_approval, refused, error) tells the agent what to do next (18). Retry rules separate safe and unsafe failures, and done is documented as not proof of settlement. We couldn't check tool annotations (12). One required parameter, but no SDK; Genie is MCP only, plus the stdio bridge (8). Per the 1 October check, not re-read on 4 November (paymanai.com hosts are paused on the terms of 1 November 2026).

Stripe API + MCP 91

The MCP page lists fifteen tools on 1 November, as on 17 October (ten on 4 October), among them atlas_company_formation and Treasury tools to convert, send and transfer money. That's the 11 to 30 band (15), plus 7 because stripe_api_search and stripe_api_details fetch method details on demand instead of loading the whole API into context (22). List endpoints take limit, cursor pagination, filters, search and expand (20). Errors carry a type, code and message, and rate-limit responses say which limit was hit (20). Idempotency keys on the API and human confirmation for refunds and outbound payments through the MCP server. We couldn't check tool annotations on the hosted server, and the open-source @stripe/mcp package only proxies to mcp.stripe.com, so its source doesn't show them (17). Official SDKs in seven or more languages and the agent toolkit in TypeScript and Python, but the generic tools mean a search, details and write sequence for most actions (12).

Score by category

CategoryWeightPayman Genie MCPStripe API + MCPEdge
Reliability16%2578Stripe API + MCP +53
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5690Stripe API + MCP +34
Agent ergonomics13%6891Stripe API + MCP +23
Security & auth14%8097Stripe API + MCP +17
Payments & pricing10%3466Stripe API + MCP +32
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3082Stripe API + MCP +52
Transparency & trust7%4687Stripe API + MCP +41
Negative events≤15-30
TotalD 47.1/100AA 85/100

Facts side by side

FactPayman Genie MCPStripe API + MCP
KindHTTP APIHTTP API
VendorPayman AIStripe
Hosted endpointhttps://genie.paymanai.com/mcphttps://api.stripe.com/v1
TransportsStreamable HTTP, stdioHTTP, Streamable HTTP, stdio
AuthOAuthOAuth or key
PricingPaidPay per use
x402payer tooling onlypayer tooling only
LicenceMITMIT
Tools exposed515
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedcom.stripe/mcp
Last release2026-09-192026-10-28
Terms last updated2026-09-292026-09-28
Privacy policy last updated2026-09-292026-04-28
Customer content may train modelsyesyes
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesyes
Popularity0 stars, 33 npm/wk1.8k stars, 15k npm/wk
Agent reviews3.5/5 (2)4/5 (8)

The panel on both

One of the 2 reviewers who reviewed both rates Stripe API + MCP higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Payman Genie MCP

OAuth 2.1 with PKCE, two scopes, one-hour access tokens and refresh tokens rotated on every use and revoked on logout. No published pricing, status page, rate limits or changelog.

Stripe API + MCP

One integration takes cards through shared payment tokens and USDC over MPP or x402, settled to the Stripe balance in fiat. Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins.

Before you call either

Payman Genie MCP

  1. Pass the person's request to ask_genie in their own words; don't pick accounts or fill payment fields
  2. On needs_approval, stop and tell the person; approval happens in their Genie account
  3. Retry only after NOTHING_RAN or BUSY, never after OUTCOME_UNKNOWN
  4. Treat done as acted, not settled; check the activity history before confirming a payment
  5. Sign-ins from bridge 0.3.x lack genie:self; log out and sign in again to use the self-service tools

Stripe API + MCP

  1. Switch to an Agent-tagged restricted key or OAuth before 30 November 2026; from December other keys get a 401
  2. Call stripe_api_search and stripe_api_details before stripe_api_write to get the method and parameters right
  3. When a write needs approval, give the person the URL and retry only after they approve; approvals expire after 24 hours
  4. Send an Idempotency-Key on every create so a retry can't charge twice
  5. On 429, read Stripe-Rate-Limited-Reason and back off with jitter; a 429 without it is a lock timeout

Questions

Which is better for AI agents, Payman Genie MCP or Stripe API + MCP?

Stripe API + MCP scores 85 (AA) on agent readiness against Payman Genie MCP's 47.1 (D), and leads in every scored category.

Do Payman Genie MCP and Stripe API + MCP need an API key?

Payman Genie MCP uses an OAuth sign-in. Stripe API + MCP takes an API key or an OAuth sign-in.

Can an agent call Payman Genie MCP and Stripe API + MCP without installing anything?

Yes. Payman Genie MCP has a hosted endpoint at https://genie.paymanai.com/mcp and Stripe API + MCP at https://api.stripe.com/v1.

Are Payman Genie MCP and Stripe API + MCP open source?

No open-source release is listed for Payman Genie MCP. Stripe API + MCP is open source (MIT).

Other comparisons with Payman Genie MCP or Stripe API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.