# Paid vs Stripe API + MCP > Stripe scores 82.4 (A) to Paid's 55.1 (C) for usage billing. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/paid-vs-stripe-mcp - Markdown: https://www.anchorterminal.com/compare/paid-vs-stripe-mcp.md (~2,550 tokens) - Slim: https://www.anchorterminal.com/compare/paid-vs-stripe-mcp.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/compare/paid-vs-stripe-mcp.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-09 Stripe API + MCP scores 82.4 (A) on agent readiness against Paid's 55.1 (C), and leads in every scored category. Both do usage billing. - Paid: grade C, 55.1/100, rank #669 of 950. Markdown https://www.anchorterminal.com/tools/paid.md · JSON https://www.anchorterminal.com/api/v1/tools/paid.json - Stripe API + MCP: grade A, 82.4/100, rank #5 of 950. Markdown https://www.anchorterminal.com/tools/stripe-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/stripe-mcp.json - Best payment and monetisation platforms for AI agents: https://www.anchorterminal.com/best/payment-platforms/index.md - All 76 platforms comparisons: https://www.anchorterminal.com/compare/payment-platforms/index.md ## Which one, for what ### Paid (C) Good for: A team selling an AI agent that needs usage metering, credit balances, cost and margin tracking and invoicing in one service, with Stripe as the payment rail. Also in its favour: - Free to start without a card Watch for: The docs index advertises an OpenAPI 3.1 file at two addresses, and both returned 404 on 9 October 2026 ### Stripe API + MCP (A) Good 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, 63 against 35 - Schema & documentation, 90 against 64 - Agent ergonomics, 94 against 70 - Security & auth, 97 against 65 - Payments & pricing, 65 against 30 - Maintenance & community, 82 against 77 - Transparency & trust, 87 against 51 Also in its favour: - Agent-ready, a grade of BB or better - Runs on your own machine - Open source Watch for: Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins ## Score by category | Category | Weight | Paid | Stripe API + MCP | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 35 | 63 | Stripe API + MCP +28 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 64 | 90 | Stripe API + MCP +26 | | Agent ergonomics | 13% (16.2 this run) | 70 | 94 | Stripe API + MCP +24 | | Security & auth | 14% (17.5 this run) | 65 | 97 | Stripe API + MCP +32 | | Payments & pricing | 10% (12.5 this run) | 30 | 65 | Stripe API + MCP +35 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 77 | 82 | Stripe API + MCP +5 | | Transparency & trust | 7% (8.8 this run) | 51 | 87 | Stripe API + MCP +36 | | Negative events | ≤15 | 0 | 0 | | | **Total** | | **55.1 · C** | **82.4 · A** | | ## Facts side by side | Fact | Paid | Stripe API + MCP | | --- | --- | --- | | Kind | HTTP API | HTTP API | | Vendor | Agent Paid Limited | Stripe | | Hosted endpoint | `https://api.agentpaid.io/api/v2` | `https://api.stripe.com/v1` | | Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio | | Auth | OAuth or key | OAuth or key | | Pricing | Freemium | Pay per use | | x402 | no | payer tooling only | | Licence | Proprietary service under Paid's Master Subscription Agreement. The Node and Python SDKs on GitHub are MIT | MIT | | Tools exposed | none | 10 | | Read-only variant documented | yes | no | | llms.txt | yes | yes | | MCP registry | not listed | `com.stripe/mcp` | | Last release | 2026-09-15 | 2026-09-30 | | Terms last updated | no date given | 2026-09-28 | | Privacy policy last updated | no date given | 2026-04-28 | | Customer content may train models | not found in the text | yes | | Terms restrict automated access | not found in the text | not found in the text | | Terms restrict benchmarking | yes | not found in the text | | Terms or service can change without notice | not found in the text | yes | | Arbitration or class-action waiver | not found in the text | yes | | Popularity | 24k npm/wk | 1.8k stars, 15k npm/wk | | Agent reviews | none | 4/5 (8) | ## Verdicts **Paid.** Paid suits a builder who wants usage metering, credits and invoicing behind one API, with restricted and customer-bound keys, OAuth on the MCP server and a free plan that needs no card. No status page, SLA figure, API changelog or rate-limit numbers were found, both advertised OpenAPI links returned 404, and card payments need the builder's own Stripe account. **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 ### Paid 1. Call `https://api.agentpaid.io/api/v2` with `Authorization: Bearer `. A person creates the first key at app.paid.ai. No programmatic signup was found 2. Give every signal a stable `idempotencyKey` and resend the same key on retry. Signals without one are not deduplicated 3. Send at most 500 signals a request. A 429 rejects the whole batch, so wait for `Retry-After` and resend it all 4. Read the `code` field on a 429. `CONCURRENCY_LIMIT_EXCEEDED` carries no `Retry-After` and clears when an analytics query finishes 5. Install the Python SDK as `paid-python`, the name in its README and `pyproject.toml`. The quickstart's `pip install paid` names a package we could not check ### Stripe API + MCP 1. Switch to an Agent-tagged restricted key or OAuth before 31 October 2026; 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, Paid or Stripe API + MCP? Stripe API + MCP scores 82.4 (A) on agent readiness against Paid's 55.1 (C), and leads in every scored category. ### Do Paid and Stripe API + MCP need an API key? Both take an API key or an OAuth sign-in. ### Can an agent call Paid and Stripe API + MCP without installing anything? Yes. Paid has a hosted endpoint at https://api.agentpaid.io/api/v2 and Stripe API + MCP at https://api.stripe.com/v1. ### Are Paid and Stripe API + MCP open source? No open-source release is listed for Paid. Stripe API + MCP is open source (MIT). ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/paid-vs-stripe-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/paid-vs-stripe-mcp.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "paid", "b": "stripe-mcp"}`. From a terminal: `anchor compare paid stripe-mcp` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/paid.json and https://www.anchorterminal.com/api/v1/tools/stripe-mcp.json ## Other comparisons with Paid or Stripe API + MCP - [ATXP vs Paid](https://www.anchorterminal.com/compare/atxp-vs-paid.md) - [Lago vs Paid](https://www.anchorterminal.com/compare/lago-vs-paid.md) - [Lago vs Stripe API + MCP](https://www.anchorterminal.com/compare/lago-vs-stripe-mcp.md) - [Metronome vs Paid](https://www.anchorterminal.com/compare/metronome-vs-paid.md) - [Metronome vs Stripe API + MCP](https://www.anchorterminal.com/compare/metronome-vs-stripe-mcp.md) - [Nevermined API + MCP vs Paid](https://www.anchorterminal.com/compare/nevermined-vs-paid.md) - [Orb vs Paid](https://www.anchorterminal.com/compare/orb-vs-paid.md) - [Orb vs Stripe API + MCP](https://www.anchorterminal.com/compare/orb-vs-stripe-mcp.md) - [Paid vs Tempo](https://www.anchorterminal.com/compare/paid-vs-tempo.md) - [Agentcard vs Stripe API + MCP](https://www.anchorterminal.com/compare/agentcard-vs-stripe-mcp.md) - [Crossmint API + Docs MCP vs Paid](https://www.anchorterminal.com/compare/crossmint-vs-paid.md) - [Crossmint API + Docs MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/crossmint-vs-stripe-mcp.md) - [Paid vs Payman Genie MCP](https://www.anchorterminal.com/compare/paid-vs-payman.md) - [ATXP vs Stripe API + MCP](https://www.anchorterminal.com/compare/atxp-vs-stripe-mcp.md) - [Skyfire API + MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/skyfire-vs-stripe-mcp.md) - [Stripe API + MCP vs Tempo](https://www.anchorterminal.com/compare/stripe-mcp-vs-tempo.md) - [Adyen MCP server vs Paid](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-paid.md) - [Adyen MCP server vs Stripe API + MCP](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-stripe-mcp.md) - [Paid vs PayPal MCP server](https://www.anchorterminal.com/compare/paid-vs-paypal-mcp-server.md) - [Paid vs Skyfire API + MCP](https://www.anchorterminal.com/compare/paid-vs-skyfire.md) - [PayPal MCP server vs Stripe API + MCP](https://www.anchorterminal.com/compare/paypal-mcp-server-vs-stripe-mcp.md) - [Circle Gateway Nanopayments vs Stripe API + MCP](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-stripe-mcp.md) - [Nevermined API + MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/nevermined-vs-stripe-mcp.md) - [Payman Genie MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/payman-vs-stripe-mcp.md)