Install
npm install mppx stripeProducts
Stripe, product by product →Stripe ships more than one product — each judged line competes in its own arena on the same stories as everyone else.
| Line | Arena | Rank | PA Score | Agent-ready |
|---|---|---|---|---|
| Payments | Online Payments | #1/10 | 55/100 | 89/100 |
| Terminal | Mobile & In-Person Payments | #1/4 | 32/100 | 59/100 |
| Atlas | Startup Legal & Incorporation | #6/7 | 11/100 | 32/100 |
| Clerkyacquired | Startup Legal & Incorporation | #4/7 | 14/100 | 37/100 |
| Billing | Billing & Subscriptions | #3/7 | 28/100 | 65/100 |
| Metronomeacquired | Billing & Subscriptions | #5/7 | 21/100 | 28/100 |
| Connect | Marketplace & Platform Payments | #2/6 | 31/100 | 65/100 |
| Radar | Payment Fraud Prevention | #2/5 | 22/100 | 50/100 |
| Tax | Sales Tax Automation | #1/6 | 22/100 | 43/100 |
| TaxJaracquired | Sales Tax Automation | #6/6 | 13/100 | 26/100 |
| Issuing | Card Issuing Platforms | #1/5 | 33/100 | 65/100 |
| Treasury | Banking as a Service | #4/6 | 17/100 | 44/100 |
| Identity | Identity Verification & KYC | #3/6 | 24/100 | 47/100 |
| Financial Connections | Banking Data APIs | #4/7 | 22/100 | 54/100 |
| Crypto & Stablecoins | Stablecoin Payments | #6/6 | 19/100 | 39/100 |
| Agentic Commercethis page | Agentic Commerce | #1/7 | 37/100 | 80/100 |
Not yet judged (10 — no arena where they compete): Invoicing · Capital · Revenue Recognition · Sigma · Data Pipeline · Managed Payments · Lemon Squeezy · Directory · Projects · Climate
Try itExperimental
See what an agent can do with Stripe Agentic Commerce before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); the live MCP handshake runs real requests from our edge, right now — including, where the server allows it, one real read-only tool call (bring your own key for auth-gated servers); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -si -X POST https://mcp.stripe.com -H 'Content-Type: application/json' -d '<jsonrpc initialize>'recorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agent checkout — stories about agent checkout in this arenaAgent checkoutevidence →
Stories about agent checkout in this arena
Agent discovery — stories about agent discovery in this arenaAgent discoveryevidence →
Stories about agent discovery in this arena
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Fees economics — stories about fees economics in this arenaFees economicsevidence →
Stories about fees economics in this arena
Merchant enablement — stories about merchant enablement in this arenaMerchant enablementevidence →
Stories about merchant enablement in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Order lifecycle — stories about order lifecycle in this arenaOrder lifecycleevidence →
Stories about order lifecycle in this arena
Payment credentials — stories about payment credentials in this arenaPayment credentialsevidence →
Stories about payment credentials in this arena
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Protocol openness — stories about protocol openness in this arenaProtocol opennessevidence →
Stories about protocol openness in this arena
Refunds disputes — stories about refunds disputes in this arenaRefunds disputesevidence →
Stories about refunds disputes in this arena
Trust safety — stories about trust safety in this arenaTrust safetyevidence →
Stories about trust safety in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 0 free · 4 paid · 0 enterprise · 36 not stated in evidence
Follow the green: where the map greys out is where Stripe Agentic Commerce stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agent checkout — stories about agent checkout in this arenaAgent checkout
Stories about agent checkout in this arena
My agent can create and update a cart or order draft through a documented protocol call
~7/10
My agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed order
✓8/10
Buyers can complete purchases of my products inside chat and assistant surfaces (ChatGPT, Claude, Gemini, Copilot and peers)
~5/10
Build against a versioned commerce protocol with a published schema and conformance or validation tooling
~6/10
Agent discovery — stories about agent discovery in this arenaAgent discovery
Stories about agent discovery in this arena
My agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership required
~4/10
Read machine-readable offer data — price, availability, variants, checkout links — for any listed product or service
~6/10
Publish my product or service catalog into agent surfaces through a documented feed or import API so AI agents can discover what I sell
✓9/10
My agent can discover payable services and APIs through a published directory or discovery index
✓7/10
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓9/10
unlocks → Machine-readable spec · Versioning policy · Full data export
Subscribe to events via webhooks
✓8/10
Build against official SDKs
✓9/10
Issue scoped/least-privilege API credentials for an agent
✓8/10
Connect an agent via an official MCP server
✓9/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
✓7/10
Explore an interactive API reference with runnable examples
~4/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
n/an/a
Operate the product with natural-language commands
~6/10
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
~4/10
Set up automations that run autonomously in the background
~5/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Fees economics — stories about fees economics in this arenaFees economics
Stories about fees economics in this arena
Merchant enablement — stories about merchant enablement in this arenaMerchant enablement
Stories about merchant enablement in this arena
Orders are attributed to the originating agent and I can report on or filter transactions by agent
✓8/10
I have a documented self-serve path to start accepting agent traffic — enable a setting, sign an agreement, or publish an endpoint
~7/10
Rate-limit, allow, or deny specific agents and agent platforms accessing my catalog and checkout
~5/10
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Order lifecycle — stories about order lifecycle in this arenaOrder lifecycle
Stories about order lifecycle in this arena
Payment credentials — stories about payment credentials in this arenaPayment credentials
Stories about payment credentials in this arena
Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card number
✓8/10
Monetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UI
✓9/10
Settle agent-initiated payments in stablecoins over documented rails
~6/10
Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibility
✓8/10
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Protocol openness — stories about protocol openness in this arenaProtocol openness
Stories about protocol openness in this arena
Refunds disputes — stories about refunds disputes in this arenaRefunds disputes
Stories about refunds disputes in this arena
Trust safety — stories about trust safety in this arenaTrust safety
Stories about trust safety in this arena
Agents identify themselves verifiably — registered profiles, signatures, or trust tiers — so I can tell trusted agent traffic from anonymous bots
~6/10
Sensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money moves
✓8/10
The fraud, liability, and chargeback rules for agent-initiated transactions are documented so I know who bears the risk
—–
Set per-agent spend caps and usage limits and revoke an agent's payment authority instantly
~7/10
Sorted by importance (agentic first) (high → low) · 56/56 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 9/10 | Tprobed⚿ | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 9/10 | Tprobed⚿ | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed⚿ | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Cclaimed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Cclaimed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed⚿ | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Tprobed⚿ | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | full | 7/10 | Cclaimed | |
Monetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UI C Machine payments | developer | Payment credentials — stories about payment credentials in this arenaPayment credentials | 3 | full | 9/10 | Tprobed | |
Publish my product or service catalog into agent surfaces through a documented feed or import API so AI agents can discover what I sell C Merchant feeds | merchant | Agent discovery — stories about agent discovery in this arenaAgent discovery | 3 | full | 9/10 | Cclaimed | |
Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card number C Delegated credentials | ai-native user | Payment credentials — stories about payment credentials in this arenaPayment credentials | 3 | full | 8/10 | Tprobed | |
My agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed order C Checkout | ai-native user | Agent checkout — stories about agent checkout in this arenaAgent checkout | 3 | fullpaid | 8/10 | Tprobed⚿ | |
Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibility C Wallets | ai-native user | Payment credentials — stories about payment credentials in this arenaPayment credentials | 3 | full | 8/10 | Tprobed | |
Sensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money moves C Human oversight | ai-native user | Trust safety — stories about trust safety in this arenaTrust safety | 3 | full | 8/10 | Tprobed⚿ | |
The commerce protocol this product speaks is published as an open, versioned specification I can read and implement without signing anything C Spec publication | developer | Protocol openness — stories about protocol openness in this arenaProtocol openness | 3 | full | 8/10 | Tprobed | |
I have a documented self-serve path to start accepting agent traffic — enable a setting, sign an agreement, or publish an endpoint C Onboarding to agents | merchant | Merchant enablement — stories about merchant enablement in this arenaMerchant enablement | 3 | partial | 7/10 | Cclaimed | |
My agent can create and update a cart or order draft through a documented protocol call C Cart | ai-native user | Agent checkout — stories about agent checkout in this arenaAgent checkout | 3 | partial | 7/10 | Cclaimed | |
Agents identify themselves verifiably — registered profiles, signatures, or trust tiers — so I can tell trusted agent traffic from anonymous bots C Agent identity | merchant | Trust safety — stories about trust safety in this arenaTrust safety | 3 | partial | 6/10 | Cclaimed | |
My agent or backend can subscribe to order lifecycle events — created, updated, fulfilled, canceled — pushed programmatically C Order events | developer | Order lifecycle — stories about order lifecycle in this arenaOrder lifecycle | 3 | partial | 5/10 | Cclaimed | |
My agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership required C Agent search | ai-native user | Agent discovery — stories about agent discovery in this arenaAgent discovery | 3 | partial | 4/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | none | 0/10 | ||
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | n/a | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | untested | none yet | |
Orders are attributed to the originating agent and I can report on or filter transactions by agent C Attribution analytics | merchant | Merchant enablement — stories about merchant enablement in this arenaMerchant enablement | 2 | full | 8/10 | Cclaimed | |
My agent can discover payable services and APIs through a published directory or discovery index C Service discovery | ai-native user | Agent discovery — stories about agent discovery in this arenaAgent discovery | 2 | full | 7/10 | Tprobed | |
Set per-agent spend caps and usage limits and revoke an agent's payment authority instantly G Spend controls | ai-native user | Trust safety — stories about trust safety in this arenaTrust safety | 2 | partial | 7/10 | Cclaimed | |
The fees for agent-originated transactions are published — I can price agentic channels without asking sales C Fees transparency | merchant | Fees economics — stories about fees economics in this arenaFees economics | 2 | fullpaid | 7/10 | Xcommunity | |
At least two independent parties beyond the vendor implement the protocol or platform — it is an ecosystem, not a private integration C Ecosystem adoption | developer | Protocol openness — stories about protocol openness in this arenaProtocol openness | 2 | partial | 6/10 | Tprobed | |
Build against a versioned commerce protocol with a published schema and conformance or validation tooling C Protocol conformance | developer | Agent checkout — stories about agent checkout in this arenaAgent checkout | 2 | partial | 6/10 | Tprobed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 6/10 | Cclaimed | |
Read machine-readable offer data — price, availability, variants, checkout links — for any listed product or service C Machine readable offers | developer | Agent discovery — stories about agent discovery in this arenaAgent discovery | 2 | partial | 6/10 | Cclaimed | |
Settle agent-initiated payments in stablecoins over documented rails C Settlement rails | developer | Payment credentials — stories about payment credentials in this arenaPayment credentials | 2 | partial | 6/10 | Tprobed | |
Buyers can complete purchases of my products inside chat and assistant surfaces (ChatGPT, Claude, Gemini, Copilot and peers) C Embedded surfaces | merchant | Agent checkout — stories about agent checkout in this arenaAgent checkout | 2 | partialpaid | 5/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 5/10 | Cclaimed | |
Rate-limit, allow, or deny specific agents and agent platforms accessing my catalog and checkout C Traffic controls | merchant | Merchant enablement — stories about merchant enablement in this arenaMerchant enablement | 2 | partial | 5/10 | Cclaimed | |
Refunds on agent-placed orders can be initiated and tracked programmatically C Refunds | developer | Refunds disputes — stories about refunds disputes in this arenaRefunds disputes | 2 | partial | 5/10 | Cclaimed | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 4/10 | Tprobed | |
My agent can query the status and tracking of an order it placed, after the purchase C Post purchase status | ai-native user | Order lifecycle — stories about order lifecycle in this arenaOrder lifecycle | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Disputes and chargebacks on agent transactions can be handled via API — evidence submission, status, outcomes C Disputes | developer | Refunds disputes — stories about refunds disputes in this arenaRefunds disputes | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | n/a | untested | none yet | |
The fraud, liability, and chargeback rules for agent-initiated transactions are documented so I know who bears the risk C Liability | merchant | Trust safety — stories about trust safety in this arenaTrust safety | 2 | none | untested | none yet | |
Agent-originated payments settle through documented payout and reporting flows, reconcilable like any other channel C Payouts | merchant | Fees economics — stories about fees economics in this arenaFees economics | 1 | fullpaid | 8/10 | Cclaimed | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 29 stories with headroom
What would move Stripe Agentic Commerce’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Automation depth — how much of the product can run unattendedDefine rules that trigger actions automatically on events
nonemoves PA Scoreimpact 30
Evidence shows Stripe emits webhooks (checkout.session.completed, SPT state-transition events, import success/failure events) that developers can build on, but there is no documented feature letting an AI-native user define custom rules/conditions that automatically trigger actions on events — in fact, agent write-actions via MCP explicitly require human approval before execution, the opposite of automatic rule-triggered action.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
The evidence pack covers agentic checkout, payment tokens, MCP tools, machine payments, and wallet CLIs, but contains no mention of a data export feature, open-format data portability, or account/data offboarding process for merchants or AI agents using the platform.
Agenticness — how well agents can access and operate the productDownload a machine-readable API spec (OpenAPI or equivalent)
nonemoves API qualityimpact 30
The evidence pack shows a direct probe for an OpenAPI/Swagger spec at all standard locations (openapi.json, swagger.json, etc.) returning 404 across the board, and no other citation surfaces a downloadable machine-readable API spec for the Agentic Commerce endpoints.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
The evidence pack covers extensive agentic-commerce features (SPTs, MCP, MPP, Link CLI, ACP) but contains no documentation of API version strings, an upgrade/versioning scheme, or a deprecation policy for these agentic-commerce endpoints — several features are explicitly flagged as 'private preview' or waitlisted rather than versioned/stable, but no deprecation policy is cited anywhere.
Trust safety — stories about trust safety in this arenaThe fraud, liability, and chargeback rules for agent-initiated transactions are documented so I know who bears the risk
nonemoves PA Scoreimpact 20
The evidence pack covers SPT scoping/revocation, checkout session lifecycle, human-approval gates for refunds, and network Agent Pay/Intelligent Commerce token programs, but nowhere states explicit fraud-liability or chargeback-allocation rules (e.g., who bears loss on a disputed agent-initiated charge, liability-shift terms, or chargeback responsibility between merchant/agent/Stripe).
Order lifecycle — stories about order lifecycle in this arenaMy agent can query the status and tracking of an order it placed, after the purchase
nonemoves PA Scoreimpact 20
Evidence covers checkout completion, order attribution in the Stripe Dashboard, and bulk fulfillment tools for sellers, but nothing shows an agent being able to query order status or shipping/tracking information after a purchase is placed — no order-status API, webhook, or tool is documented for the agent side post-purchase.
Refunds disputes — stories about refunds disputes in this arenaDisputes and chargebacks on agent transactions can be handled via API — evidence submission, status, outcomes
nonemoves PA Scoreimpact 20
The evidence pack documents refunds via the standard Refunds API/Dashboard for machine payments, and general agent-approval workflows for actions like refunds, but contains no mention of a disputes/chargebacks API, evidence submission, dispute status tracking, or outcome reporting for agent-initiated transactions specifically.
Privacy posture — data-handling and privacy storiesControl data retention and deletion
nonemoves PA Scoreimpact 20
The evidence pack covers token/authorization revocation (SPT revocation, OCA termination) and human-approval gates for payment actions, but nothing about user-controlled data retention policies, data export, or deletion of stored personal/transaction data.
Showing the top 8 of 29 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map13 surfaces · 40 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Agentic commerce docs32 stories
- My agent can create and update a cart or order draft through a documented protocol call
- My agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed order
- Buyers can complete purchases of my products inside chat and assistant surfaces (ChatGPT, Claude, Gemini, Copilot and peers)
- My agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership required
- Read machine-readable offer data — price, availability, variants, checkout links — for any listed product or service
- Publish my product or service catalog into agent surfaces through a documented feed or import API so AI agents can discover what I sell
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Build against official SDKs
- Subscribe to events via webhooks
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Operate the product with natural-language commands
- Explore an interactive API reference with runnable examples
- Perform bulk operations across many items at once
- Agent-originated payments settle through documented payout and reporting flows, reconcilable like any other channel
- Orders are attributed to the originating agent and I can report on or filter transactions by agent
- I have a documented self-serve path to start accepting agent traffic — enable a setting, sign an agreement, or publish an endpoint
- Rate-limit, allow, or deny specific agents and agent platforms accessing my catalog and checkout
- Do everything through the API that I can do in the UI
- Read the product's source under an open license
- My agent or backend can subscribe to order lifecycle events — created, updated, fulfilled, canceled — pushed programmatically
- Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card number
- Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibility
- At least two independent parties beyond the vendor implement the protocol or platform — it is an ecosystem, not a private integration
- Refunds on agent-placed orders can be initiated and tracked programmatically
- Agents identify themselves verifiably — registered profiles, signatures, or trust tiers — so I can tell trusted agent traffic from anonymous bots
- Sensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money moves
- Set per-agent spend caps and usage limits and revoke an agent's payment authority instantly
MCP docs15 stories
- My agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed order
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Build against official SDKs
- Set up automations that run autonomously in the background
- Operate the product with natural-language commands
- Explore an interactive API reference with runnable examples
- Do everything through the API that I can do in the UI
- Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card number
- Refunds on agent-placed orders can be initiated and tracked programmatically
- Sensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money moves
- Set per-agent spend caps and usage limits and revoke an agent's payment authority instantly
Payments docs13 stories
- Build against a versioned commerce protocol with a published schema and conformance or validation tooling
- My agent can discover payable services and APIs through a published directory or discovery index
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Build against official SDKs
- Set up automations that run autonomously in the background
- Agent-originated payments settle through documented payout and reporting flows, reconcilable like any other channel
- Monetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UI
- Settle agent-initiated payments in stablecoins over documented rails
- At least two independent parties beyond the vendor implement the protocol or platform — it is an ecosystem, not a private integration
- The commerce protocol this product speaks is published as an open, versioned specification I can read and implement without signing anything
- Refunds on agent-placed orders can be initiated and tracked programmatically
Skills docs6 stories
- My agent can discover payable services and APIs through a published directory or discovery index
- Point an agent at llms.txt or agent-oriented docs
- Drive the product through a documented public API
- Build against official SDKs
- Operate the product with natural-language commands
- Explore an interactive API reference with runnable examples
GitHub README5 stories
- Use an official CLI
- Build against official SDKs
- Read the product's source under an open license
- Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card number
- Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibility
agenticcommerce.dev5 stories
- Buyers can complete purchases of my products inside chat and assistant surfaces (ChatGPT, Claude, Gemini, Copilot and peers)
- Build against a versioned commerce protocol with a published schema and conformance or validation tooling
- Read the product's source under an open license
- At least two independent parties beyond the vendor implement the protocol or platform — it is an ecosystem, not a private integration
- The commerce protocol this product speaks is published as an open, versioned specification I can read and implement without signing anything
Keys docs5 stories
- Issue scoped/least-privilege API credentials for an agent
- Build against official SDKs
- Do everything through the API that I can do in the UI
- Agents identify themselves verifiably — registered profiles, signatures, or trust tiers — so I can tell trusted agent traffic from anonymous bots
- Set per-agent spend caps and usage limits and revoke an agent's payment authority instantly
Sandboxes docs5 stories
OpenAPI spec3 stories
Directory docs2 stories
Pricing docs2 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -si -X POST https://mcp.stripe.com -H 'Content-Type: application/json' -d '<jsonrpc initialize>'reproduced$ curl -si -X POST https://mcp.stripe.com -H 'Content-Type: application/json' -d '<jsonrpc initialize>'
HTTP/2 401
server: nginx
date: Mon, 14 Sep 2026 23:24:01 GMT
content-type: application/json
content-length: 81
cache-control: max-age=0, no-cache, no-store, must-revalidate
content-security-policy: base-uri 'none'; default-src 'none'; form-action 'none'; frame-ancestors 'none'; img-src 'self'; script-src 'self' 'report-sample'; style-src 'self'; worker-src 'none'; upgrade-insecure-requests; report-uri https://q.stripe.com/csp-violation?q=kHNQbs2Q2-6TzXbIqU3meVzCDKjPQCZctL_B4supQA04x-H8v7bSOZHSI5LuPBGdf2s1cp0q; report-to csp
cross-origin-opener-policy: same-origin; report-to="wsp_coop"
expires: 0
pragma: no-cache
referrer-policy: strict-origin-when-cross-origin
report-to: {"group":"coop","max_age":8640,"endpoints":[{"url":"https://q.stripe.com/coop-report"}],"include_subdomains":true}, {"group":"wsp_coop","max_age":8640,"endpoints":[{"url":"https://q.stripe.com/coop-report?s=kHNQbs2Q2-6TzXbIqU3meVzCDKjPQCZctL_B4supQA04x-H8v7bSOZHSI5LuPBGdf2s1cp0q"}],"include_subdomains":true}, {"group":"wsp_coep","max_age":8640,"endpoints":[{"url":"https://q.stripe.com/coep-report?s=kHNQbs2Q2-6TzXbIqU3meVzCDKjPQCZctL_B4supQA04x-H8v7bSOZHSI5LuPBGdf2s1cp0q"}],"include_subdomains":true}, {"group":"csp","max_age":8640,"endpoints":[{"url":"https://q.stripe.com/csp-report-v2?q=kHNQbs2Q2-6TzXbIqU3meVzCDKjPQCZctL_B4supQA04x-H8v7bSOZHSI5LuPBGdf2s1cp0q&t=1"}],"include_subdomains":true}
reporting-endpoints: coop="https://q.stripe.com/coop-report", wsp_coop="https://q.stripe.com/coop-report?s=kHNQbs2Q2-6TzXbIqU3meVzCDKjPQCZctL_B4supQA04x-H8v7bSOZHSI5LuPBGdf2s1cp0q", wsp_coep="https://q.stripe.com/coep-report?s=kHNQbs2Q2-6TzXbIqU3meVzCDKjPQCZctL_B4supQA04x-H8v7bSOZHSI5LuPBGdf2s1cp0q", csp="https://q.stripe.com/csp-report-v2?q=kHNQbs2Q2-6TzXbIqU3meVzCDKjPQCZctL_B4supQA04x-H8v7bSOZHSI5LuPBGdf2s1cp0q&t=1"
request-id: req_gH1wg9lQO2TqyW
www-authenticate: Bearer resource_metadata=https://mcp.stripe.com/.well-known/oauth-protected-resource
x-content-type-options: nosniff
x-robots-tag: none
x-stripe-proxy-response: upstream
x-stripe-server-rpc-duration-micros: 8751
x-wc: 3ff
strict-transport-security: max-age=63072000; includeSubDomains; preload
{"error":"Unauthorized. See https://docs.stripe.com/mcp for usage instructions."}
$curl -s https://mpp.dev/ | head -4 # the MPP spec site answers agents in markdownreproduced$ curl -s https://mpp.dev/ | head -4 # the MPP spec site answers agents in markdown # MPP — Machine Payments Protocol MPP (Machine Payments Protocol) is the open standard for machine-to-machine payments via HTTP 402.
$npm view @stripe/link-cli version # the Link agent-wallet CLI, on the public registryreproduced$ npm view @stripe/link-cli version # the Link agent-wallet CLI, on the public registry link-cli version: 0.19.2
$npm view mppx version # the machine-payments SDK, on the public registryreproduced$ npm view mppx version # the machine-payments SDK, on the public registry mppx version: 0.9.3
$curl -s https://docs.stripe.com/.well-known/skills/index.json # Stripe-maintained agent skills, keylessreproduced$ curl -s https://docs.stripe.com/.well-known/skills/index.json # Stripe-maintained agent skills, [redacted]less
{"skills":[{"name":"connect-recommend","description":"Use this skill when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
14 of 28 testable claims verified · 0 contradicted → integrity 50/100
39 distinct capability claims found in Stripe Agentic Commerce’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
14
Verified
14
Unverified
0
Contradicted
12
Undersold
Verified (24)
“Sellers can build custom checkout endpoints and process agentic payments via a third-party processor”
Build against a versioned commerce protocol with a published schema and conformance or validation toolingpartialproof ↗
“Shared payment tokens give sellers scoped, limited access to a customer's payment method for agent purchases”
Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card numberfullproof ↗
“An official Stripe MCP server exposes tools agents use to call the Stripe API”
“Agent-oriented docs (including an llms-full CLI doc mode) help agents build accurate integrations”
Point an agent at llms.txt or agent-oriented docsfullproof ↗
“Machine payments let agents pay per-call for APIs/services via an HTTP 402 challenge-and-pay flow”
Monetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UIfullproof ↗
“x402 protocol returns a 402 response with a Stripe deposit address for stablecoin agent payments”
Monetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UIfullproof ↗
“Developers can generate an MPP-monetized API endpoint with a single prompt to a coding agent”
Point an agent at llms.txt or agent-oriented docsfullproof ↗
“An mppx conformance CLI validates MPP implementations end-to-end (discovery, challenge, payment flow)”
Build against a versioned commerce protocol with a published schema and conformance or validation toolingpartialproof ↗
“Agents can test-pay MPP endpoints using the official link-cli or Tempo CLI”
“Link CLI gives an agent access to a customer-controlled wallet with one-time-use payment credentials”
Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibilityfullproof ↗
“Every Link wallet agent spend requires the customer to approve the request in the Link app or website”
Sensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money movesfullproof ↗
“An agent can read transaction history, balances, and account details from connected bank/credit accounts”
Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibilityfullproof ↗
“Stripe Directory helps agents/developers discover and provision the best external providers for a task”
My agent can discover payable services and APIs through a published directory or discovery indexfullproof ↗
“The wallet CLI can issue a virtual card, a Link Pay Token, or a shared payment token as agent credentials”
Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card numberfullproof ↗
“The wallet CLI can issue a virtual card, a Link Pay Token, or a shared payment token as agent credentials”
“In private preview, agents can act as intermediaries presenting feeds, managing carts/checkout, and accepting payment”
My agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed orderfullproof ↗
“Custom ACP integration defines a reverse API with documented checkout session states Stripe calls on your backend”
Build against a versioned commerce protocol with a published schema and conformance or validation toolingpartialproof ↗
“Confirmed SPTs resolve into agentic_token or dpan credentials, potentially via network Agent Pay/Intelligent Commerce programs”
At least two independent parties beyond the vendor implement the protocol or platform — it is an ecosystem, not a private integrationpartialproof ↗
“Embedded checkout (OCA) manages the full lifecycle — feed ingestion, cart, fulfillment, payment collection — for agent builders”
My agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed orderfullproof ↗
“Stablecoin machine payments (USDC) are supported down to $0.01 across Tempo, Solana, and Base rails”
Settle agent-initiated payments in stablecoins over documented railspartialproof ↗
“Dashboard-side agent write actions like refunds/payouts require a human-approved token that expires after 24 hours”
Sensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money movesfullproof ↗
“ACP is published open source under Apache 2.0, implementable by any business with any AI agent or processor”
The commerce protocol this product speaks is published as an open, versioned specification I can read and implement without signing anythingfullproof ↗
“OpenAI has implemented ACP in ChatGPT and Stripe is the first compatible PSP with SPT support”
At least two independent parties beyond the vendor implement the protocol or platform — it is an ecosystem, not a private integrationpartialproof ↗
“Agent-originated orders are charged Stripe's standard published card processing rates with no separate agentic fee”
The fees for agent-originated transactions are published — I can price agentic channels without asking salesfullproof ↗
Unverified (17)
“ACS lets sellers start accepting agent-driven purchases with a single integration”
I have a documented self-serve path to start accepting agent traffic — enable a setting, sign an agreement, or publish an endpointpartialproof ↗
“ACS can be embedded directly into an AI assistant/chat interface for commerce”
Buyers can complete purchases of my products inside chat and assistant surfaces (ChatGPT, Claude, Gemini, Copilot and peers)partialproof ↗
“Restricted API keys (RAKs) are the recommended scoped credential type to hand to AI agents”
Issue scoped/least-privilege API credentials for an agentfullproof ↗
“Buyers can browse, get recommendations, and complete purchases without leaving the chat conversation”
Buyers can complete purchases of my products inside chat and assistant surfaces (ChatGPT, Claude, Gemini, Copilot and peers)partialproof ↗
“In private preview, agents can act as intermediaries presenting feeds, managing carts/checkout, and accepting payment”
My agent can create and update a cart or order draft through a documented protocol callpartialproof ↗
“Sellers individually review and approve each agent's terms before that agent can transact with them”
Rate-limit, allow, or deny specific agents and agent platforms accessing my catalog and checkoutpartialproof ↗
“Merchants publish their catalog as a CSV feed via a Product Catalog Import API with daily/15-min update cadence”
Publish my product or service catalog into agent surfaces through a documented feed or import API so AI agents can discover what I sellfullproof ↗
“Catalog imports emit success/failure webhooks with a per-row error report”
“Agent-placed orders are tagged with the originating agent in the Dashboard and filterable by agent name”
Orders are attributed to the originating agent and I can report on or filter transactions by agentfullproof ↗
“Stripe fires a checkout.session.completed event for each agent-completed order”
My agent or backend can subscribe to order lifecycle events — created, updated, fulfilled, canceled — pushed programmaticallypartialproof ↗
“Sellers can bulk fulfill agent orders via the List CheckoutSessions endpoint instead of one-by-one”
Perform bulk operations across many items at oncepartialproof ↗
“An OCA is a documented, mutually-confirmed connection between agent and seller that either party can terminate anytime”
Rate-limit, allow, or deny specific agents and agent platforms accessing my catalog and checkoutpartialproof ↗
“Issuers set SPT usage limits (currency, max amount, expiry) and can revoke the token at any time to block further use”
Set per-agent spend caps and usage limits and revoke an agent's payment authority instantlypartialproof ↗
“SPTs move through a documented state machine (active/requires_action/deactivated) with a webhook per transition”
“Machine payments settle directly into the seller's Stripe balance with standard reporting and multi-currency payouts”
Agent-originated payments settle through documented payout and reporting flows, reconcilable like any other channelfullproof ↗
“Refunds on machine payments are available through the standard Refunds API and Dashboard”
Refunds on agent-placed orders can be initiated and tracked programmaticallypartialproof ↗
“Link wallet lets an agent search products and complete purchases through the UCP protocol”
My agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership requiredpartialproof ↗
Undersold (12)
Read machine-readable offer data — price, availability, variants, checkout links — for any listed product or servicepartialproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIfullproof ↗
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Explore an interactive API reference with runnable examplespartialproof ↗
Test against a sandbox environment without touching production datafullproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Read the product's source under an open licensepartialproof ↗
Agents identify themselves verifiably — registered profiles, signatures, or trust tiers — so I can tell trusted agent traffic from anonymous botspartialproof ↗
Business model
Agent transactions ride standard Stripe processing (2.9% + 30¢ US cards); machine payments settle from $0.50 (cards via Shared Payment Tokens) or $0.01 (stablecoins over MPP/x402), priced per transaction.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
