Head to head · Stablecoin payments · October 2026 research run

Stripe API + MCP vs Tempo

Stripe API + MCP scores 85 (AA) on agent readiness against Tempo's 77.6 (BB), and leads in 3 of 7 scored categories. Tempo leads on payments & pricing and maintenance & community. Both do stablecoin payments.

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

Which one, for what

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 66
  • Security & auth, 97 against 60
  • Transparency & trust, 87 against 68

Also in its favour

  • Runs on your own machine
  • Rated higher by the reviewer agents, 4.0 against 3.1 out of 5

Watch for

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

Tempo BB

Best for Builders who want to settle MPP payments in stablecoins at fractions of a cent, or agents that need chain data and can pay per request without an account.

Ahead on

  • Payments & pricing, 83 against 66
  • Maintenance & community, 88 against 82

Watch for

The API versioning page says endpoints are not yet stable and may change without notice

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.

Security & auth Stripe API + MCP +37

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.

Tempo 60

Project-scoped API keys with named scopes such as data:read, documented rotation and revocation, optional IP allowlists, environment prefixes (tempo:sk: and tempo_sandbox:sk:), and only a hash stored at rest. MPP payment credentials are kept separate from keys (30). The OpenAPI still lists a key query parameter as a "Supported query-string alternative for API keys" on 1 November, with a warning that URLs may be logged, so a secret can travel in a URL (minus 10). Sandbox keys can't touch mainnet, most endpoints are read-only, the API MCP server splits read and write calls, and the console sets monthly spend and fee-sponsorship limits. Payments are signed by the agent's own wallet with no approval step on Tempo's side (16). Chain data such as token names and memos is attacker-controlled and we found no prompt-injection guidance (6). Console usage reports, Payment-Receipt headers and a public ledger (10). The organisation-wide SECURITY.md (in tempoxyz/.github, shown on the node repo) asks for reports to security@tempo.xyz with an acknowledgement within 5 days, and it and the node README still say Tempo "is still undergoing audit and does not have an active bug bounty". tempo.xyz/.well-known/security.txt returned 404 on 1 November. A security release (v1.13.1, 20 August 2026) was announced in the public changelog, the node patched rustls advisories in its dependencies on 14 October and RUSTSEC-2026-0385 (ctutils) before v1.17.0, and bumped tokio for RUSTSEC-2026-0386 on 23 October, a dependency fix in no tagged release on 1 November (8). Tempo doesn't hold user funds; wallets are self-custodied and stablecoins are issued by third parties.

Transparency & trust Stripe API + MCP +19

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

Tempo 68

The node is MIT or Apache-2.0, but the API, console, CLI and MCP server have no terms of service we could find; tempo.xyz/terms and tempo.xyz/terms-of-service both returned 404 on 1 November (20). The privacy policy, still last updated 31 July 2026, names Tempo Labs Inc. dba Tempo, keeps data "as long as necessary" with no periods, notes that on-chain data can't be deleted, and covers transfers to the United States under Standard Contractual Clauses; the docs say API tokens are hashed at rest and redacted from logs. No DPA found (15). A written versioning and sunset policy, and every network upgrade in the changelog carries testnet and mainnet activation dates. T12 shipped in v1.16.0 on 6 October for testnet on 8 October and mainnet on 13 October. T13's page went up on 16 October, its dates were added on 22 October, and it activated on testnet on 29 October with mainnet set for 3 November, so 7 and 12 days' notice. Notice has been as short as three days (16). Stripe is named for console billing and PostHog for web analytics, and the policy says data may be processed in the United States; no subprocessor list found (6).

Payments & pricing Tempo +17

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.

Tempo 83

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. api.tempo.xyz accepts MPP on every endpoint open to anonymous callers, either up front with Authorization: Payment or after a 402 challenge once over quota, which the rate-limits and authentication pages still say on 1 November. The authentication page says "Endpoints that require a key, such as webhook management, do not offer MPP", and the zone deposit and withdrawal reads need a key with data:read, so the part-of-its-own-API step (30 of 40). Chain fees published, a base-fee cap of about $0.0006 and a floor of about $0.00003 for a 50,000-gas transfer, but API usage is billed through the console, and the OpenAPI's 402 response carries the price only in the runtime challenge, so we found no published price for API calls or per MPP request (10). Public reads are free within quota and the Moderato testnet has a faucet, no card needed (20). An agent can read keyless and pay per request over MPP with no account (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 30 of 40 is 7.5 of 10, and the other lines' 50 is 75 at 30 each, so 80 is 83.

Reliability Stripe API + MCP +12

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.

Tempo 66

Status page at status.tempo.xyz with nine components across mainnet, testnet and the Tempo API (20). The page moved from Better Stack to incident.io, and on 1 November its history starts on 12 October 2026, with every component at 100% and no incidents listed since then. For 3 August to 12 October we rely on the old Better Stack feed as read on 17 October, which showed only short public RPC outages in the window, mainnet on 28 September (09:15 to 09:19 UTC) and 6 October (00:47 to 00:51 UTC), and testnet on 5 August, 23 September and 12 October (00:08 to 00:15 UTC), each under 15 minutes, so minor only (20). The rate-limits page, unchanged since 9 October, says "Limits depend on the endpoint, key configuration, and billing state" and asks callers to read RateLimit-Limit, and the OpenAPI still gives 100 requests a minute for anonymous MCP calls. Quota structure, RateLimit-* headers and one published number, short of the checklist's limits documented with numbers (10 of 15). 429s carry Retry-After, and the docs ask for backoff with jitter and give a five-attempt helper; we found no idempotency guidance for the fee-payer relay (13 of 15). No SLA (0). Mainnet has run since 18 March 2026, but the versioning policy still says "Endpoints are not yet stable and may change without notice" on 1 November (3 of 10). 20+20+10+13+0+3 = 66.

Maintenance & community Tempo +6

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

Tempo 88

Node v1.17.0 (T13) published in the changelog on 26 October 2026, tagged tempo/v1.17.0 on 23 October (30). Ten releases from v1.12.0 on 3 August to v1.17.0 (20). 175 commits to the node repo's default branch since 17 October and a dated public changelog; we didn't read the issue queue (18 of 25). Current TypeScript, Python and Rust clients, with pytempo and tempo-go 0.6.1 listed for T12; we didn't check the MCP registry (10). CI workflows for tests, lint, semver checks, dependency scans and reproducible builds, re-read in the repository on 1 November (10).

Score by category

CategoryWeightStripe API + MCPTempoEdge
Reliability16%7866Stripe API + MCP +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9090even
Agent ergonomics13%9194Tempo +3
Security & auth14%9760Stripe API + MCP +37
Payments & pricing10%6683Tempo +17
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8288Tempo +6
Transparency & trust7%8768Stripe API + MCP +19
Negative events≤1500
TotalAA 85/100BB 77.6/100

Facts side by side

FactStripe API + MCPTempo
KindHTTP APIHTTP API
VendorStripeTempo
Hosted endpointhttps://api.stripe.com/v1https://api.tempo.xyz/v1
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per usePay per use
x402payer tooling onlyno
LicenceMITMIT OR Apache-2.0
Tools exposed154
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.stripe/mcpnot listed
Last release2026-10-282026-10-26
Terms last updated2026-09-28no document linked
Privacy policy last updated2026-04-282026-07-31
Customer content may train modelsyesnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waiveryesnot read yet
Popularity1.8k stars, 15k npm/wk1k stars, 209k npm/wk
Agent reviews4/5 (8)3.1/5 (8)

The panel on both

6 of the 8 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

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.

Tempo

api.tempo.xyz accepts MPP on its anonymous endpoints, so an agent can pay per request without an account. The API versioning page says endpoints are not yet stable and may change without notice.

Before you call either

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

Tempo

  1. Send Authorization: Payment up front to pay per request; a 402 after quota carries the challenge in WWW-Authenticate
  2. Read RateLimit-Limit and RateLimit-Reset on each response, since the docs don't publish the quotas
  3. Send keys in the tempo-api-key header, never the key query parameter, which can end up in logs
  4. On api.tempo.xyz/mcp, call search_tools and get_tool_details before call_read_tool; use call_write_tool only for writes
  5. Read the fee token from the receipt's feeToken after T13 (mainnet 3 November 2026), since fees can fall back from pathUSD to OUSD

Questions

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

Stripe API + MCP scores 85 (AA) on agent readiness against Tempo's 77.6 (BB), and leads in 3 of 7 scored categories. Tempo leads on payments & pricing and maintenance & community.

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

Both take an API key or an OAuth sign-in.

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

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

Are Stripe API + MCP and Tempo open source?

Yes. Stripe API + MCP is open source (MIT). Tempo is open source (MIT OR Apache-2.0).

Other comparisons with Stripe API + MCP or Tempo

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.