Head to head · Stablecoin payments · October 2026 research run

Nevermined API + MCP vs Skyfire API + MCP

Nevermined API + MCP scores 66.5 (B) on agent readiness against Skyfire API + MCP's 44.3 (E), and leads in every scored category. Both do stablecoin 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 19
  • Schema & documentation, 85 against 69
  • Agent ergonomics, 77 against 61
  • Security & auth, 77 against 49
  • Payments & pricing, 74 against 45
  • Maintenance & community, 81 against 4
  • Transparency & trust, 73 against 55

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.0 out of 5

Watch for

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

Skyfire API + MCP E

Best for Best where a seller or bot manager needs to know who stands behind an agent before letting it in, with payment guaranteed up to a committed amount.

Also in its favour

  • No incidents deducted, where Nevermined API + MCP loses 6 points for them

Watch for

No x402 or MPP; both buyer and seller must be on Skyfire

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 +77

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.

Skyfire API + MCP 4

No changelog and no dated API change found; reference page update stamps record no change, and the 4 August 2026 date of seller SDK 0.0.7 came from the npm registry document, which this check doesn't use (it would be 98 days old, 10, either way) (0). No release or dated change in the 90 days from 12 August (0). No changelog and no public SDK repository; the KYAPay specification repository's newest commit is a dependency pin on 2 September, and support is by email (4). No official SDK named in the docs, and the npm reading is struck (0). No package or CI we could read (0). 0 + 0 + 4 + 0 + 0 = 4.

Reliability Nevermined API + MCP +31

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.

Skyfire API + MCP 19

No status page found, and status.skyfire.xyz still doesn't resolve on 10 November (0), so no incident history (5). No rate limits in the docs index or the error reference (0). The error reference (updated 3 November) says to branch on code, not to retry 4xx answers unchanged and to retry a 500 SERVER_ERROR with backoff, but names no 429, Retry-After or idempotency key for token creation; the earlier partial is kept (4 of 15). No SLA (0). Production and sandbox are both live, with no beta label (10). 0 + 5 + 0 + 4 + 0 + 10 = 19.

Payments & pricing Nevermined API + MCP +29

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.

Skyfire API + MCP 45

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. No x402, MPP or L402 in the docs index or the pages read on 10 November. Payment runs on Skyfire's own KYAPay tokens, an open specification but none of the three protocols, so the own-protocol step (0). No price list; the terms (25 June 2025) say Skyfire doesn't currently charge for buying credits or generating tokens and may add fees with 30 days' notice (10). The quickstart signs a person up by email magic link and creates a buyer agent with a pre-funded wallet, with no card step (20). A person signs up in the dashboard, and paid services need identity checks, before an agent can pay; the organisation APIs that mint users and keys need an admin who signed up first (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Security & auth Nevermined API + MCP +28

Nevermined API + MCP 77

One Bearer API key per environment, sandbox and live kept apart and revocable through an RFC 7009 endpoint, plus OAuth 2.1 with PKCE (S256) and a commerce scope for MCP hosts on an allow-list, and an RFC 8628 device flow for headless agents. No scopes on API keys themselves were found (25 of 30). Delegations carry a hard cap in cents, a purchase count, an expiry and an optional recipient list, set by a person and revocable at once, Visa delegations need a passkey, and maxTotalCents caps one call. There's no read-only key and no confirmation per payment within the cap (17 of 20). The Router pays and relays third-party merchant responses. The guardrails page treats merchant payment challenges as untrusted, refuses unlisted assets and amounts over the cap and withholds upstream bodies on errors, but gives no guidance on instructions inside a merchant's response (8 of 15). A unified payment ledger, per-delegation transactions and an organisation activity feed, and the Data Policy on nevermined.app, per the 17 October check and not re-read (the host is paused on its terms), keeps audit logs of actions for five years (14 of 15). security.txt on nevermined.ai is valid until 19 October 2027 and points to a security page that states no disclosure process or reply time. SOC 2 Type II, ISO/IEC 27001:2022 and PCI SAQ-D are claimed with reports under NDA through a Trust Center we didn't open, while the Data Policy called ISO 27001 in progress on 17 October. No bug bounty and no published advisory (13 of 20). 25+17+8+14+13 = 77.

Skyfire API + MCP 49

A skyfire-api-key header, with separate buyer, seller and organisation admin key types so a buyer key can't charge and a seller key can't mint. Organisation admins can now create, list, deactivate and reactivate agent API keys through the API, and the docs give a rotation order (create the replacement, migrate, deactivate the old key; page updated 19 October), so scoped, revocable keys with rotation (30). A pay token caps what a seller can charge at its amount, expires in 10 seconds to 24 hours and is bound to one seller, and agents can be limited to set source IP addresses, but we found no buyer-side spending cap on an agent and no confirmation on create-pay-token (10). find-sellers returns third-party listings with no prompt-injection guidance (6). No audit log found (0). Tokens are JWTs verified against a public JWKS, with jti for replay checks, and Skyfire runs KYB on buyer platforms and KYC through Persona. security.txt answers 404 on 10 November and no disclosure policy, bug bounty or SOC 2 was found (3). 30 + 10 + 6 + 0 + 3 = 49. Funds sit in "a digital wallet set up by Skyfire or our service providers", the terms name no bank, custodian or licence, and credits are non-refundable.

Transparency & trust Nevermined API + MCP +18

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.

Skyfire API + MCP 55

Closed service under terms dated 25 June 2025, re-read on 10 November. The KYAPay specification is published under the Community Specification License with its example code under MIT (17). Privacy policy dated 25 June 2025, unchanged, links a DPA, names Persona and Google Analytics, keeps data in US data centres, gives no retention periods, permits training AI models on personal data, and says sellers receive any personal information carried in a token (18). No deprecation policy or notices found (0). A service-providers page lists processors, and data locations are stated (15). 17 + 18 + 0 + 15 = 50.

Schema & documentation Nevermined API + MCP +16

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.

Skyfire API + MCP 69

Each API reference page's Markdown version carries an OpenAPI 3.1.0 fragment for its operation (spec "skyfire-agent-and-token-apis" 1.0, server https://api.skyfire.xyz), with no single file to download; per-page fragments take 20, as lucid and chroma did (20). llms.txt with 91 entries, 46 of them API reference pages, each served as Markdown (10). The docs explain when to use a kya, pay or kya-pay token and when to name an onboarded or an external seller, while the MCP tool descriptions are one line each (12). Token type is one of three values, expiresAt is clamped to 10 seconds to 24 hours, amounts are plain decimal strings with stated precision, and sellerServiceId and sellerDomainOrUrl are mutually exclusive (11). Ten error codes documented with a fixed code, message, details body and handling advice (12). /api/v1 in paths and no changelog (4). 20 + 10 + 12 + 11 + 12 + 4 = 69.

Score by category

CategoryWeightNevermined API + MCPSkyfire API + MCPEdge
Reliability16%5019Nevermined API + MCP +31
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8569Nevermined API + MCP +16
Agent ergonomics13%7761Nevermined API + MCP +16
Security & auth14%7749Nevermined API + MCP +28
Payments & pricing10%7445Nevermined API + MCP +29
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%814Nevermined API + MCP +77
Transparency & trust7%7355Nevermined API + MCP +18
Negative events≤15-60
TotalB 66.5/100E 44.3/100

Facts side by side

FactNevermined API + MCPSkyfire API + MCP
KindHTTP APIHTTP API
VendorNeverminedSkyfire
Hosted endpointhttps://api.live.nevermined.apphttps://api.skyfire.xyz
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyAPI key
PricingFreemiumFreemium
x402payer tooling onlyno
LicenceApache-2.0none
Tools exposed134
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.nevermined-io/catalognot listed
Last release2026-11-102026-08-04
Terms last updatedno date given2025-06-25
Privacy policy last updatedno date given2025-06-25
Customer content may train modelsnot found in the textyes
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
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/wknone
Agent reviews3/5 (2)2/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Nevermined 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

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.

Skyfire API + MCP

Identity and payment travel in one signed JWT that sellers verify offline against a public JWKS, and organisation admins can rotate and revoke agent keys through the API. There is no x402 or MPP, both buyer and seller must be on Skyfire, and no status page, changelog or dated release was found.

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.

Skyfire API + MCP

  1. Buyer keys create tokens and seller keys charge them; a 403 usually means the wrong key type or a deactivated key
  2. Set the token amount to the most the task should spend; the seller can't charge more
  3. Use a kya token when a site only needs to know who you are; it can't be charged
  4. Don't retry 4xx answers unchanged; retry only a 500 SERVER_ERROR, with backoff
  5. Rehearse against mcp-sandbox.skyfire.xyz before using mcp.skyfire.xyz

Questions

Which is better for AI agents, Nevermined API + MCP or Skyfire API + MCP?

Nevermined API + MCP scores 66.5 (B) on agent readiness against Skyfire API + MCP's 44.3 (E), and leads in every scored category.

Do Nevermined API + MCP and Skyfire API + MCP need an API key?

Nevermined API + MCP takes an API key or an OAuth sign-in. Skyfire API + MCP needs an API key.

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

Yes. Nevermined API + MCP has a hosted endpoint at https://api.live.nevermined.app and Skyfire API + MCP at https://api.skyfire.xyz.

Other comparisons with Nevermined API + MCP or Skyfire API + 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.