Head to head · Card payments · October 2026 research run

Crossmint API + Docs MCP vs Payman Genie MCP

Crossmint API + Docs MCP scores 64.4 (B) on agent readiness against Payman Genie MCP's 47.1 (D), and leads in 6 of 7 scored categories. Payman Genie MCP leads on security & auth. Both do card payments.

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

Which one, for what

Crossmint API + Docs MCP B

Best for Products that let agents spend, especially where a user wants a capped card or a capped stablecoin wallet for an agent, or an agent that buys from ordinary merchant sites.

Ahead on

  • Reliability, 53 against 25
  • Schema & documentation, 71 against 56
  • Agent ergonomics, 77 against 68
  • Payments & pricing, 44 against 34
  • Maintenance & community, 85 against 30
  • Transparency & trust, 80 against 46

Watch for

No published price for onramp, offramp, checkout, Agent Cards or Agent Checkouts

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.

Ahead on

  • Security & auth, 80 against 73

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

No published pricing, status page, rate limits or changelog

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.

Maintenance & community Crossmint API + Docs MCP +55

Crossmint API + Docs MCP 85

Release packages commit on 29 October 2026 shipped @crossmint/wallets-sdk 1.21.0 and @crossmint/client-sdk-react-ui 4.13.1 (30). 18 release commits in the 90 days from 3 August, 7 August to 29 October (20). Per-package changesets are detailed and current, but the docs changelog hasn't had an entry since 11 February 2026, and we didn't read the GitHub issue queue (12 of 25). Current official SDKs (15). CI runs build and tests, plus smoke, end-to-end regression, CodeQL and security-scan workflows. Chain removals stop old code compiling, 1.18.0's with deprecation first and migration notes, 1.20.1's (Abstract, a patch release) with neither (8).

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.

Transparency & trust Crossmint API + Docs MCP +34

Crossmint API + Docs MCP 80

The SDKs are Apache-2.0 and the API is closed under published terms (18). Privacy policy updated 26 June 2026 names six Crossmint entities, states DPAs with each provider, keeps Persona biometric data no more than three years and otherwise retains data "as long as necessary", and uses SCCs and the EU-US Data Privacy Framework. It says personal data isn't used to train general-purpose models (20). The changelog dates deprecations, such as Checkout V2 ending on 30 October 2025, and SDK changesets give migration steps for removed chains (15). Subprocessors are listed on the Trust page, which we didn't open, and transfers outside the EEA are disclosed (12).

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.

Reliability Crossmint API + Docs MCP +28

Crossmint API + Docs MCP 53

status.crossmint.com redirects to a Datadog-hosted status page (20, per the 1 October check). On 1 November the Datadog host answered robots.txt with 403 AccessDenied, so it was treated as blocked and not read; on 1 October it rendered only in JavaScript with no readable history. No incident history could be read, a limit of our reading and not a finding against Crossmint (5). Rate limits published, 120 writes and 360 reads a minute per project on self-serve plans, with higher limits for token and minting endpoints (15). The limits page says a 429 comes back and to wait briefly, with no Retry-After or backoff guidance, but the wallets OpenAPI documents an x-idempotency-key header on wallet, transaction, transfer and signature creation (8 of 15). Enterprise gets "premium SLAs" through sales, and no SLA is published (0). Wallets are generally available, but Agent Checkouts runs in production only with no staging, and the wallets spec still routes balances and transfer history through /unstable paths (5 of 10).

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.

Schema & documentation Crossmint API + Docs MCP +15

Crossmint API + Docs MCP 71

A Crossmint Wallets API OpenAPI 3.0 file with 39 paths sits in the public SDK repo, but we found none for payments, onramp, Agent Cards or Agent Checkouts (15 of 25). llms.txt with about 450 entries, an llms-full.txt, and every page served as Markdown by appending .md (10). Operation descriptions state the purpose and the API scope each call needs, with little on when not to use them (12). Typed DTOs with required fields, though wallets are addressed by formatted locator strings such as email:<email>:<chainType> (11). Payment and onramp error-code pages, and the wallets spec documents 400, 404, 409 and 422 responses, with code samples in the quickstarts (11). Date-versioned paths (/2025-06-09/) and a docs changelog, but its newest entry is 11 February 2026, so recent API changes are only in the SDK changelogs (12).

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).

Payments & pricing Crossmint API + Docs MCP +10

Crossmint API + Docs MCP 44

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. Crossmint's own API isn't paid over x402 or MPP. Crossmint's n8n node (n8n-nodes-crossmint 1.1.0, 12 November 2025) puts an x402 paywall in front of a workflow and settles to an address the seller sets through the Corbits facilitator, so the merchant step, though only for n8n (25 of 40). Agent Wallets also pay x402 and MPP endpoints for the buyer. Wallet overage at $0.02 per monthly active wallet and tokenisation at $0.01 an action are public, while onramp, offramp, checkout, orchestration, Agent Cards and Agent Checkouts have no published price (10). 1,000 free monthly active wallets with up to 2,000 transactions, and free staging on testnets, but the pricing page doesn't say whether a card is needed (15). A person signs up in the console to get keys (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' 25 is 37.5 at 30 each, so 50 is 44.

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.

Agent ergonomics Crossmint API + Docs MCP +9

Crossmint API + Docs MCP 77

No payments or wallet MCP server. A one-tool docs search server and, since the 1 October check, a console server for projects and API keys. Responses can be narrowed by chains and tokens filters and perPage (15). Page and cursor pagination with date-range and status filters on transactions and transfers (18). Error-code pages for payments and typed SDK errors such as RecoveryMethodRequiredError and InvalidChainError, with less for the wallet REST errors (13). The wallets OpenAPI documents x-idempotency-key on wallet, transaction, transfer and signature creation (17). Official SDKs in TypeScript (browser, React, React Native and Node), Swift, Kotlin and Flutter, each with a quickstart, though wallets are addressed by formatted locator strings (14).

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).

Score by category

CategoryWeightCrossmint API + Docs MCPPayman Genie MCPEdge
Reliability16%5325Crossmint API + Docs MCP +28
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7156Crossmint API + Docs MCP +15
Agent ergonomics13%7768Crossmint API + Docs MCP +9
Security & auth14%7380Payman Genie MCP +7
Payments & pricing10%4434Crossmint API + Docs MCP +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8530Crossmint API + Docs MCP +55
Transparency & trust7%8046Crossmint API + Docs MCP +34
Negative events≤15-3-3
TotalB 64.4/100D 47.1/100

Facts side by side

FactCrossmint API + Docs MCPPayman Genie MCP
KindHTTP APIHTTP API
VendorCrossmintPayman AI
Hosted endpointhttps://www.crossmint.com/apihttps://genie.paymanai.com/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP, stdio
AuthAPI keyOAuth
PricingFreemiumPaid
x402payer tooling onlypayer tooling only
LicenceApache-2.0MIT
Tools exposed15
Read-only variant documentednono
llms.txtyesno
Last release2026-10-292026-09-19
Terms last updated2026-07-012026-09-29
Privacy policy last updated2026-09-212026-09-29
Customer content may train modelsnot found in the textyes
Terms restrict automated accessyesyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesyes
Popularity52 stars, 40k npm/wk0 stars, 33 npm/wk
Agent reviews3.5/5 (2)3.5/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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

Crossmint API + Docs MCP

Agent Wallets are non-custodial, with spend caps, allowed counterparties and time windows enforced onchain, and wallet writes take a documented idempotency key. Onramp, offramp, checkout, Agent Cards and Agent Checkouts have no published price, and the status history couldn't be read.

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.

Before you call either

Crossmint API + Docs MCP

  1. Send an x-idempotency-key on every wallet, transaction or transfer create so a retry can't pay twice
  2. Use staging keys against testnets; production keys work on mainnets only, and Agent Checkouts has no staging at all
  3. On 429, wait and retry. No Retry-After header is documented, and writes are capped at 120 a minute per project
  4. Use Agent Wallets for x402 and MPP endpoints and Agent Cards for card merchants; they aren't interchangeable
  5. Connect the console MCP server to staging first. It has full access to the organisation, including deleting API keys

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

Questions

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

Crossmint API + Docs MCP scores 64.4 (B) on agent readiness against Payman Genie MCP's 47.1 (D), and leads in 6 of 7 scored categories. Payman Genie MCP leads on security & auth.

Do Crossmint API + Docs MCP and Payman Genie MCP need an API key?

Crossmint API + Docs MCP needs an API key. Payman Genie MCP uses an OAuth sign-in.

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

Yes. Crossmint API + Docs MCP has a hosted endpoint at https://www.crossmint.com/api and Payman Genie MCP at https://genie.paymanai.com/mcp.

Other comparisons with Crossmint API + Docs MCP or Payman Genie 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.