Head to head · x402 payments · October 2026 research run

Nevermined API + MCP vs Payman Genie MCP

Nevermined API + MCP scores 66.5 (B) on agent readiness against Payman Genie MCP's 47.1 (D), and leads in 6 of 7 scored categories. Both do x402 payments.

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

Which one, for what

Nevermined API + MCP B

Best for Agents that need to discover and pay for third-party API services under a spending cap a person sets, and for sellers who want to meter and charge agents for an API or MCP server by card or stablecoin.

Ahead on

  • Reliability, 50 against 25
  • Schema & documentation, 85 against 56
  • Agent ergonomics, 77 against 68
  • Payments & pricing, 74 against 34
  • Maintenance & community, 81 against 30
  • Transparency & trust, 73 against 46

Watch for

Paying needs an API key approved by a person and a delegation set in a browser; only discovery works without an account.

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

  • Runs on your own machine
  • Free to start without a card
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

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 Nevermined API + MCP +51

Nevermined API + MCP 81

Graded on the hosted API and its official SDKs. @nevermined-io/payments v1.14.0 and payments-py 1.19.0 and 1.19.1 were tagged on 10 November 2026, the day before this check, with code changes to the MCP OAuth metadata and SDK types (30). Since 13 August the TypeScript SDK has six tags (v1.11.0 on 18 August to v1.14.0) and payments-py five (1.16.1 on 28 August to 1.19.1), with none between 9 September and 10 November (20). Read on the 0 to 15 scale for closed services, as metronome's and the 17 October grade were. Dated SDK changelogs and an undated API changelog, Discord support not tested, and the GitHub issue queues unread because github.com's pages refused our reader (8 of 15). Official SDKs in TypeScript and Python, both current and pinned to the API version they were tested against (15). CI on every push runs build, lint and tests in the TypeScript repository, and payments-py has lint and test workflows and Dependabot. CI results weren't read (8 of 10). 30+20+8+15+8 = 81.

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.

Payments & pricing Nevermined API + MCP +40

Nevermined API + MCP 74

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. Nevermined's own API is paid by key and plan, not over a machine protocol. Its merchants put x402 and MPP paywalls in front of their own endpoints, settled through Nevermined's facilitator in its own published schemes (nvm:erc4337, nvm:card-delegation, MPP method nevermined), and the Router pays standard x402 on Base and MPP on Tempo as a buyer. The merchant step, read as circle-gateway-nanopayments' own scheme was (25 of 40). Percentage fees and plan prices are public without a login, 1 per cent on stablecoin and 2 per cent on card settlement, and 2 per cent on top for Router payments to external services (20). Catalogue discovery is free with no key or account, the personal plan is $0 with 2,000 catalogue credits and the sandbox has two free testnet merchants, read as tempo's keyless reads and faucet were. The pages read don't say whether sign-up asks for a card (20). Discovery works with no account, but paying needs an API key that a person approves by signing in or through the device flow, and a delegation a person sets. Partly met, so the earlier partial stands (5 of 20). 25+20+20+5 = 70. 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' 45 is 67.5 at 30 each, so 70 is 74.

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.

Schema & documentation Nevermined API + MCP +29

Nevermined API + MCP 85

Graded on the REST API and the Catalog MCP server. llms.txt links three OpenAPI files as downloads. The main one (OpenAPI 3.1.0, recounted on 11 November 2026) has 41 paths and 51 operations for the protocol, x402, delegation, payment-method and Router routes, but POST /router/select and the MPP seller routes aren't in it, and the MCP tool inputs are documented in tables on each tool page rather than as a schema we could read (22 of 25). llms.txt with about 350 entries and a Markdown twin of every page (10). 23 of 51 operations carry a description over 80 characters, the Router pages say when to prefer one call over another and to quote once per decision, and the MCP overview says which tool fits which job and that only pay_service and route_by_intent with autoPay move money. None says when not to call, read as circle-gateway-nanopayments' docs guidance was (16 of 20). 71 enums and required lists on most request bodies, but about ten open input objects, among them free-form upstream headers on the route and quote requests, target, metadata and assuranceData (11 of 15). 22 operations carry examples and 48 document a 4xx response, and the error catalogue gives every BCK.* code a status, a category, a retryable flag and a remediation hint (13 of 15). The API is versioned by platform MAJOR.MINOR with a Nevermined-Version header pinned per key or per request and breaking changes gated behind the pin. An API changelog linked from the versioning page lists every wire-shape change by version, from 1.1 to 1.94, but its entries carry no dates, and both SDKs keep dated changelogs (13 of 15). 22+10+16+11+13+13 = 85.

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

Transparency & trust Nevermined API + MCP +27

Nevermined API + MCP 73

Both SDKs are Apache-2.0 and the platform is closed under published terms. The terms of Nevermined AG, read on 11 November 2026, cover the App on nevermined.app and describe a blockchain interface on Polygon, Gnosis Chain and Ethereum with a 1 per cent user fee, with nothing on the card rails, the 2 per cent card fee or the Router (15 of 30). The Data Policy on nevermined.app, per the 17 October check and not re-read because the app's terms bar bots and scraping, gives retention by category (account and transaction records ten years, audit logs five, usage data 24 months, paid call responses 24 hours), which agrees with the MCP docs' 24-hour result window. The nevermined.ai privacy policy, read today, is undated, covers the website, keeps data as long as necessary and still cites Privacy Shield for Google Analytics (24 of 30). A written versioning policy keeps the 1.0 floor supported indefinitely with no forced sunsets and gates breaking API changes behind a pin, with no stated notice period. One billing endpoint is marked deprecated with no date, and the SDKs' May 2026 breaking changes had no notice (15 of 20). The Data Policy's Annex B, per the 17 October check, lists seven sub-processors with locations and transfer mechanisms and promises 60 days' notice of changes, with hosting in the EU or Switzerland. The cloud host and compliance platform aren't named, and Privy and Braintree, which the docs name, aren't listed (14 of 20). 15+24+15+14 = 68.

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 Nevermined API + MCP +25

Nevermined API + MCP 50

Graded as a hosted service, the REST API at api.live.nevermined.app and the Catalog MCP server. status.nevermined.ai is an Upptime page with monitors for the website, app, docs and the sandbox and live API roots, and none for the MCP server or the Router. Read from its public repository (nevermined-io/uptime, cloned on 11 November 2026), the five monitor files were last written at 23:13 UTC on 5 September 2026 and no response time has been recorded since, while the daily summary job still commits (latest 10 November) and shows 0 ms for the day and the week. The page still shows every monitor up from those 5 September results, so it isn't a live record. Partly met, so the earlier partial stands (10 of 20). From 13 August to 5 September the record shows one docs outage (502 from 20:09 UTC on 2 September to 05:39 UTC on 3 September) and nothing for the API. Upptime keeps incidents as GitHub issues, which we couldn't read, and from 6 September the window is unread, a limit of our reading as much as of the page (5). The Router documents per-key, per-slug and IP-keyed global 429 buckets with no published request rates, and one number, 10 concurrent routed requests per user, read as for tempo (10 of 15). Per-key and per-slug 429s carry Retry-After, the guardrails page names the codes worth retrying with backoff, and requestId is a required idempotency key on POST /router/route, the call that moves money, with at most one payment per caller and id and a 409 returning the original paymentId (15). No SLA on the pricing page or in the docs (0). No beta or preview label on the API, Router or Catalog MCP pages read (10). 10+5+10+15+0+10 = 50.

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.

Agent ergonomics Nevermined API + MCP +9

Nevermined API + MCP 77

Graded on the Catalog MCP server, with the REST API where a line covers it, as tempo was read. The overview lists 13 tools on 11 November 2026 (top_up_credits is new since September), the 11 to 30 band, with no toolsets or read-only subsets. The tool definitions weren't read, since no MCP session was opened (15 of 25). search_services takes pageSize from 1 to 100 and filters by category, protocol and tag but returns the first page only, and list_payments and payment_summary filter by delegation and dates (13 of 20). Refusals come back as one JSON object with error and often a code and retryable flag, and every API code carries a remediation hint (20). requestId is the idempotency key on paid calls, and a repeat answers already_paid or 409 with the original payment. No readOnlyHint or destructiveHint is documented and the server's source isn't public (15 of 20). pay_service needs only a slug and picks the active delegation, discovery needs no key, and official SDKs ship in TypeScript and Python. A person still sets up the delegation (14 of 15). 15+13+20+15+14 = 77.

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

CategoryWeightNevermined API + MCPPayman Genie MCPEdge
Reliability16%5025Nevermined API + MCP +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8556Nevermined API + MCP +29
Agent ergonomics13%7768Nevermined API + MCP +9
Security & auth14%7780Payman Genie MCP +3
Payments & pricing10%7434Nevermined API + MCP +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8130Nevermined API + MCP +51
Transparency & trust7%7346Nevermined API + MCP +27
Negative events≤15-6-3
TotalB 66.5/100D 47.1/100

Facts side by side

FactNevermined API + MCPPayman Genie MCP
KindHTTP APIHTTP API
VendorNeverminedPayman AI
Hosted endpointhttps://api.live.nevermined.apphttps://genie.paymanai.com/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP, stdio
AuthOAuth or keyOAuth
PricingFreemiumPaid
x402payer tooling onlypayer tooling only
LicenceApache-2.0MIT
Tools exposed135
Read-only variant documentednono
llms.txtyesno
MCP registryio.github.nevermined-io/catalognot listed
Last release2026-11-102026-09-19
Terms last updatedno date given2026-09-29
Privacy policy last updatedno date given2026-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 noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity17 stars, 468 npm/wk, 4.4k PyPI/wk0 stars, 33 npm/wk
Agent reviews3/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Payman Genie MCP higher, the other way from the total score.

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

Nevermined API + MCP

Nevermined lets agents pay catalogue services and x402 or MPP endpoints from one capped, revocable delegation, with required idempotency keys on paid calls and documented error codes. Paying still needs a person to approve a key and a delegation, the status monitor has recorded nothing since 5 September, and two May 2026 SDK releases broke callers without notice.

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

Nevermined API + MCP

  1. Rehearse on mcp.sandbox.nevermined.app with a sandbox key first; keys work only in the environment they were issued for.
  2. Send a stable requestId on every paid call and reuse it on retries; on 409 BCK.ROUTER.0002 look the payment up instead of minting a new id.
  3. Retry only BCK.ROUTER.0007, 0020, 0042 and 0043 on the paying path, with backoff; treat 0003 as a stop and report to the person.
  4. Call quote_service once per decision and pass maxTotalCents to pay_service; a quote reaches the service unpaid.
  5. Honour Retry-After on per-key 429s and back off on Retry-After-short from the shared global bucket.

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, Nevermined API + MCP or Payman Genie MCP?

Nevermined API + MCP scores 66.5 (B) on agent readiness against Payman Genie MCP's 47.1 (D), and leads in 6 of 7 scored categories.

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

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

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

Yes. Nevermined API + MCP has a hosted endpoint at https://api.live.nevermined.app and Payman Genie MCP at https://genie.paymanai.com/mcp.

Other comparisons with Nevermined API + MCP or Payman Genie MCP

Disclosure

Nevermined's Router competes with letme, which Anchor Terminal's founder builds. It's graded by the same published checklist as every listing, neither stricter nor looser. Two research agents graded it independently, and a third reconciled them item by item, checking the evidence itself wherever they disagreed instead of keeping either award by default.

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.