Head to head · Stablecoin payments · October 2026 research run

Skyfire API + MCP vs Stripe API + MCP

Stripe API + MCP scores 85 (AA) 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

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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

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 19
  • Schema & documentation, 90 against 69
  • Agent ergonomics, 91 against 61
  • Security & auth, 97 against 49
  • Payments & pricing, 66 against 45
  • Maintenance & community, 82 against 4
  • Transparency & trust, 87 against 55

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Open source
  • Rated higher by the reviewer agents, 4.0 against 2.0 out of 5

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.

Maintenance & community Stripe API + MCP +78

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.

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

Reliability Stripe API + MCP +59

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.

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.

Security & auth Stripe API + MCP +48

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.

Stripe API + MCP 97

OAuth for interactive MCP clients with per-account and per-environment permissions and revocable sessions, restricted and Agent-tagged API keys with chosen permissions, and API key access policies by location. The MCP page now sets a migration deadline of 30 November 2026, after which, from December, the MCP server rejects full-access secret keys and untagged restricted keys (30). Least privilege through restricted keys and Dashboard roles, and Stripe requires a person to approve sensitive stripe_api_write actions such as refunds and outbound payments, with approvals expiring after 24 hours (20). The MCP page tells users to turn on human confirmation of tools and to take care combining Stripe with other servers because of prompt injection; customer-entered fields still come back through stripe_api_read (12). MCP tool-call logs in Workbench and an exportable security history (15). HackerOne bug bounty, PCI Service Provider Level 1, annual SOC 1 and SOC 2 Type II reports, a public SOC 3, no published advisories on stripe/ai, and a valid security.txt, read on 17 October with an expiry of 31 December 2026, not re-read on 1 November (20). Machine payments land in the Stripe balance, so Stripe holds the funds until payout.

Transparency & trust Stripe API + MCP +32

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.

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

Agent ergonomics Stripe API + MCP +30

Skyfire API + MCP 61

Four compact MCP tools, create-kya-token, create-pay-token, create-kya-payment-token and find-sellers (25). find-sellers takes a search term, and we found no page-size or field controls (8). Ten stable error codes with field-level details on validation errors and advice on which answers not to retry (16). No idempotency key on token creation; a CONFLICT answer creates nothing, and sellers dedupe on the token's jti (6). Token creation needs only type and a seller, with the expiry and funding wallet defaulted; the earlier reading of a Node seller SDK came from the npm registry document, which this check doesn't use, and no SDK is named in the docs (6). 25 + 8 + 16 + 6 + 6 = 61.

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

Schema & documentation Stripe API + MCP +21

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.

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

Score by category

CategoryWeightSkyfire API + MCPStripe API + MCPEdge
Reliability16%1978Stripe API + MCP +59
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6990Stripe API + MCP +21
Agent ergonomics13%6191Stripe API + MCP +30
Security & auth14%4997Stripe API + MCP +48
Payments & pricing10%4566Stripe API + MCP +21
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%482Stripe API + MCP +78
Transparency & trust7%5587Stripe API + MCP +32
Negative events≤1500
TotalE 44.3/100AA 85/100

Facts side by side

FactSkyfire API + MCPStripe API + MCP
KindHTTP APIHTTP API
VendorSkyfireStripe
Hosted endpointhttps://api.skyfire.xyzhttps://api.stripe.com/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingFreemiumPay per use
x402nopayer tooling only
LicencenoneMIT
Tools exposed415
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.stripe/mcp
Last release2026-08-042026-10-28
Terms last updated2025-06-252026-09-28
Privacy policy last updated2025-06-252026-04-28
Customer content may train modelsyesyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesyes
Popularitynone1.8k stars, 15k npm/wk
Agent reviews2/5 (2)4/5 (8)

The panel on both

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

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.

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

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

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, Skyfire API + MCP or Stripe API + MCP?

Stripe API + MCP scores 85 (AA) on agent readiness against Skyfire API + MCP's 44.3 (E), and leads in every scored category.

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

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

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

Yes. Skyfire API + MCP has a hosted endpoint at https://api.skyfire.xyz and Stripe API + MCP at https://api.stripe.com/v1.

Are Skyfire API + MCP and Stripe API + MCP open source?

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

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