How Stripe Agentic Commerce’s scores are calculated

Point an agent at llms.txt or agent-oriented docsweight 2

2 (weight) × 9 (quality) × 1.0 (full) = 18.0 of 20 max

• [probe] https://docs.stripe.com/llms.txt“PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm registry for the latest version rather tha”
• [probe] https://docs.stripe.com/agentic-commerce.md“PROBE docs-md: HTTP 200 at https://docs.stripe.com/agentic-commerce.md # Agentic commerce Sell through agents, or embed commerce into your AI interface. Agentic commerce uses AI agents to s”
• [probe] https://docs.stripe.com/skills.md“PROBE runtime (recorded 2026-09-14): the machine-readable skills catalog is live at the documented keyless well-known URL — https://docs.stripe.com/.well-known/skills/index.json returns the JSON index of Stripe-maintained agent skills (connect-recommend, stripe-best-practices, stripe-directory, ...).”
• [claimed-docs] https://docs.stripe.com/skills.md“Install instructions that help AI agents create more accurate Stripe integrations.”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/link-cli.md“"Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to complete purchases, and retrieve permissioned financial data to answer questions about spending, balances, and trends." Every spend is human-gated: "Customers approve each request on the Link website or in the mobile app. Agent payments support one-time-use virtual cards and shared payment tokens." Wallet guides cover "Search products and complete payments with UCP" and how to "pay merchants that accept machine payments over HTTP 402", and the tool is agent-legible: "Your agent can inspect the full CLI documentation with `link-cli --llms-full`".”
• [probe] https://docs.stripe.com/mcp“official MCP server documented at https://docs.stripe.com/mcp”

Run the product headlessly / in CI for automationweight 2

2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max

• [claimed-docs] https://docs.stripe.com/sandboxes.md“Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymous Stripe sandbox with working API keys. No account registration required.”
• [claimed-docs] https://docs.stripe.com/payments/machine/mpp.md“MPP "is an open protocol that lets agents pay for your APIs and services programmatically without a checkout UI, co-authored by Stripe and Tempo": on an unpaid request "your server returns an HTTP `402` response with payment details", then "The agent authorizes the payment, retries the request, and gets access to the paid resource along with a receipt." The docs ship a one-prompt agent build path ("Read https://docs.stripe.com/payments/machine/mpp.md?lang=node, and monetize my API using MPP to charge 0.50 USD per API call") and a conformance CLI: "Run `mppx validate` to automatically verify your implementation end-to-end. The command tests discovery, challenge formats, error handling, and the full payment flow." Agents test-pay with `npx @stripe/link-cli mpp pay` or the Tempo CLI.”
• [claimed-docs] https://docs.stripe.com/mcp.md“Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirmation before it takes certain `stripe_api_write` actions, such as refunds and outbound payments." The human reviews an approval URL; "When you click Approve, Stripe provides the agent with an approval token, but you need to tell the agent to retry the operation", and "If you don’t approve the action within 24 hours, it expires."”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/link-cli.md“"Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to complete purchases, and retrieve permissioned financial data to answer questions about spending, balances, and trends." Every spend is human-gated: "Customers approve each request on the Link website or in the mobile app. Agent payments support one-time-use virtual cards and shared payment tokens." Wallet guides cover "Search products and complete payments with UCP" and how to "pay merchants that accept machine payments over HTTP 402", and the tool is agent-legible: "Your agent can inspect the full CLI documentation with `link-cli --llms-full`".”

Plug MCP servers into this product so it can use their toolsweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Connect an agent via an official MCP serverweight 3

3 (weight) × 9 (quality) × 1.0 (full) = 27.0 of 30 max

• [claimed-docs] https://docs.stripe.com/mcp.md“The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API”
• [claimed-docs] https://docs.stripe.com/mcp.md“The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe’s knowledge base, including documentation and support articles.”
• [claimed-docs] https://docs.stripe.com/mcp.md“Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirmation before it takes certain `stripe_api_write` actions, such as refunds and outbound payments." The human reviews an approval URL; "When you click Approve, Stripe provides the agent with an approval token, but you need to tell the agent to retry the operation", and "If you don’t approve the action within 24 hours, it expires."”
• [probe] https://docs.stripe.com/mcp“PROBE runtime (recorded 2026-09-14): Stripe's hosted MCP server is live and gated exactly as documented — a keyless JSON-RPC initialize POST to https://mcp.stripe.com answered HTTP 401 with the OAuth challenge pointing at docs.stripe.com/mcp, the per-spec auth contract an agent reads before connecting.”
• [probe] https://docs.stripe.com/mcp“official MCP server documented at https://docs.stripe.com/mcp”

Use an official CLIweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

• [claimed-docs] https://docs.stripe.com/agentic-commerce/link-cli.md“Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to complete purchases”
• [github] https://github.com/stripe/link-cli“The CLI can produce one of three credential types: A virtual card (PAN)... A Link Pay Token (LPT)... A Shared Payment Token (SPT)”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/link-cli.md“"Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to complete purchases, and retrieve permissioned financial data to answer questions about spending, balances, and trends." Every spend is human-gated: "Customers approve each request on the Link website or in the mobile app. Agent payments support one-time-use virtual cards and shared payment tokens." Wallet guides cover "Search products and complete payments with UCP" and how to "pay merchants that accept machine payments over HTTP 402", and the tool is agent-legible: "Your agent can inspect the full CLI documentation with `link-cli --llms-full`".”
• [probe] https://docs.stripe.com/agentic-commerce/link-cli“official CLI documented at https://docs.stripe.com/agentic-commerce/link-cli”
• [probe] https://docs.stripe.com/agentic-commerce/link-cli.md“PROBE runtime (recorded 2026-09-14): the Link CLI — the agent-wallet client documented for retrieving one-time-use payment credentials and permissioned financial data — is published on the public npm registry (npm view @stripe/link-cli → 0.19.2; source at github.com/stripe/link-cli).”
• [claimed-docs] https://docs.stripe.com/sandboxes.md“Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymous Stripe sandbox with working API keys. No account registration required.”
• [claimed-docs] https://docs.stripe.com/payments/machine/mpp.md“MPP "is an open protocol that lets agents pay for your APIs and services programmatically without a checkout UI, co-authored by Stripe and Tempo": on an unpaid request "your server returns an HTTP `402` response with payment details", then "The agent authorizes the payment, retries the request, and gets access to the paid resource along with a receipt." The docs ship a one-prompt agent build path ("Read https://docs.stripe.com/payments/machine/mpp.md?lang=node, and monetize my API using MPP to charge 0.50 USD per API call") and a conformance CLI: "Run `mppx validate` to automatically verify your implementation end-to-end. The command tests discovery, challenge formats, error handling, and the full payment flow." Agents test-pay with `npx @stripe/link-cli mpp pay` or the Tempo CLI.”

Drive the product through a documented public APIweight 3

3 (weight) × 9 (quality) × 1.0 (full) = 27.0 of 30 max

• [claimed-docs] https://docs.stripe.com/mcp.md“The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API”
• [probe] https://docs.stripe.com/mcp“PROBE runtime (recorded 2026-09-14): Stripe's hosted MCP server is live and gated exactly as documented — a keyless JSON-RPC initialize POST to https://mcp.stripe.com answered HTTP 401 with the OAuth challenge pointing at docs.stripe.com/mcp, the per-spec auth contract an agent reads before connecting.”
• [probe] https://docs.stripe.com/payments/machine/mpp.md“PROBE runtime (recorded 2026-09-14): the Machine Payments Protocol is published in the open — https://mpp.dev/ answers a plain GET with the full markdown spec index ('# MPP — Machine Payments Protocol... the open standard for machine-to-machine payments via HTTP 402'), including governance, quickstarts, and llms-full.txt guidance; and the mppx SDK resolves on the public npm registry (npm view mppx → 0.9.3).”
• [probe] https://docs.stripe.com/skills.md“PROBE runtime (recorded 2026-09-14): the machine-readable skills catalog is live at the documented keyless well-known URL — https://docs.stripe.com/.well-known/skills/index.json returns the JSON index of Stripe-maintained agent skills (connect-recommend, stripe-best-practices, stripe-directory, ...).”
• [probe] https://docs.stripe.com/agentic-commerce/link-cli.md“PROBE runtime (recorded 2026-09-14): the Link CLI — the agent-wallet client documented for retrieving one-time-use payment credentials and permissioned financial data — is published on the public npm registry (npm view @stripe/link-cli → 0.19.2; source at github.com/stripe/link-cli).”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/for-sellers/custom.md“The ACP-style custom integration has sellers "implement a reverse API that defines the requests Stripe sends to your commerce backend and the response shapes your backend returns" — "When an agent routes a checkout request through Stripe, Stripe calls these endpoints on your behalf." Checkout create/update/confirm hooks move a session through the documented statuses "incomplete | ready_for_payment | requires_escalation | processing | completed | canceled"; on confirm the seller receives a shared payment token — a "scoped grant of the customer’s payment method from the agent to your" Stripe profile "with specific usage and expiration limits" — and resolves it into credentials whose type "is either `agentic_token` or `dpan`". "In collaboration with the card networks, Stripe might use tokens issued through network programs such as Mastercard’s Agent Pay and Visa’s Intelligent Commerce programs on your behalf." Geography and access are gated: "Agentic Commerce Suite (ACS) is available in the US." and onboarding the endpoint requires the waitlist.”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/concepts/shared-payment-tokens.md?agent-seller=agent“"Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases." The issuing agent must "Set usage limits, including currency, maximum amount, and expiration window" (usage_limits currency / max_amount / expires_at in the create call), and can "Revoke the SPT at any time to prevent the seller from using it to create a payment" — "Sellers can’t create a payment with a revoked SPT." "An SPT functions as a state machine" across active / requires_action / deactivated, with webhooks for each transition (for `shared_payment.issued_token.used`: "You receive this event when the seller uses the SPT").”
• [claimed-docs] https://docs.stripe.com/payments/machine.md“"Machine payments let agents pay for APIs and services programmatically. Your server returns a payment challenge, the agent presents a valid payment credential, and Stripe settles the payment to your Stripe balance." Minimums are documented per rail: for card payments through SPTs "the minimum amount is 0.50 USD", for stablecoins "the minimum amount is 0.01" USDC — across MPP on Tempo (USDC.e) and Solana (USDC) and x402 on Base (USDC) — and "Stablecoin payments are available to businesses in all US states, except New York." Settlement stays on-platform: "Payments land directly in your Stripe balance and settle in fiat. Metrics, reporting, and multi-currency payouts work the same as any other payment in Stripe", with refunds available through the standard Refunds API and Dashboard per the features table.”
• [probe] https://docs.stripe.com/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/api/openapi.json, https://docs.stripe.com/.well-known/openapi.json)”

Issue scoped/least-privilege API credentials for an agentweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

• [claimed-docs] https://docs.stripe.com/keys/restricted-api-keys.md“RAKs are the recommended type of key for API keys you give to AI agents.”
• [claimed-docs] https://docs.stripe.com/keys/restricted-api-keys.md“Stripe recommends always using RAKs instead of unrestricted secret keys, especially when giving a key to an AI agent. Use RAK permissions to limit what an agent can do in your account.”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/concepts/shared-payment-tokens.md?agent-seller=agent“"Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases." The issuing agent must "Set usage limits, including currency, maximum amount, and expiration window" (usage_limits currency / max_amount / expires_at in the create call), and can "Revoke the SPT at any time to prevent the seller from using it to create a payment" — "Sellers can’t create a payment with a revoked SPT." "An SPT functions as a state machine" across active / requires_action / deactivated, with webhooks for each transition (for `shared_payment.issued_token.used`: "You receive this event when the seller uses the SPT").”
• [claimed-docs] https://docs.stripe.com/mcp.md“Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirmation before it takes certain `stripe_api_write` actions, such as refunds and outbound payments." The human reviews an approval URL; "When you click Approve, Stripe provides the agent with an approval token, but you need to tell the agent to retry the operation", and "If you don’t approve the action within 24 hours, it expires."”
• [claimed-docs] https://docs.stripe.com/sandboxes.md“Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymous Stripe sandbox with working API keys. No account registration required.”

Build against official SDKsweight 2

2 (weight) × 9 (quality) × 1.0 (full) = 18.0 of 20 max

• [claimed-docs] https://docs.stripe.com/mcp.md“The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API”
• [claimed-docs] https://docs.stripe.com/skills.md“Install instructions that help AI agents create more accurate Stripe integrations.”
• [claimed-docs] https://docs.stripe.com/keys/restricted-api-keys.md“RAKs are the recommended type of key for API keys you give to AI agents.”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/link-cli.md“Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to complete purchases”
• [github] https://github.com/stripe/link-cli“The CLI can produce one of three credential types: A virtual card (PAN)... A Link Pay Token (LPT)... A Shared Payment Token (SPT)”
• [probe] https://docs.stripe.com/mcp“PROBE runtime (recorded 2026-09-14): Stripe's hosted MCP server is live and gated exactly as documented — a keyless JSON-RPC initialize POST to https://mcp.stripe.com answered HTTP 401 with the OAuth challenge pointing at docs.stripe.com/mcp, the per-spec auth contract an agent reads before connecting.”
• [probe] https://docs.stripe.com/payments/machine/mpp.md“PROBE runtime (recorded 2026-09-14): the Machine Payments Protocol is published in the open — https://mpp.dev/ answers a plain GET with the full markdown spec index ('# MPP — Machine Payments Protocol... the open standard for machine-to-machine payments via HTTP 402'), including governance, quickstarts, and llms-full.txt guidance; and the mppx SDK resolves on the public npm registry (npm view mppx → 0.9.3).”
• [probe] https://docs.stripe.com/skills.md“PROBE runtime (recorded 2026-09-14): the machine-readable skills catalog is live at the documented keyless well-known URL — https://docs.stripe.com/.well-known/skills/index.json returns the JSON index of Stripe-maintained agent skills (connect-recommend, stripe-best-practices, stripe-directory, ...).”
• [probe] https://docs.stripe.com/agentic-commerce/link-cli.md“PROBE runtime (recorded 2026-09-14): the Link CLI — the agent-wallet client documented for retrieving one-time-use payment credentials and permissioned financial data — is published on the public npm registry (npm view @stripe/link-cli → 0.19.2; source at github.com/stripe/link-cli).”
• [claimed-docs] https://docs.stripe.com/payments/machine/mpp.md“MPP "is an open protocol that lets agents pay for your APIs and services programmatically without a checkout UI, co-authored by Stripe and Tempo": on an unpaid request "your server returns an HTTP `402` response with payment details", then "The agent authorizes the payment, retries the request, and gets access to the paid resource along with a receipt." The docs ship a one-prompt agent build path ("Read https://docs.stripe.com/payments/machine/mpp.md?lang=node, and monetize my API using MPP to charge 0.50 USD per API call") and a conformance CLI: "Run `mppx validate` to automatically verify your implementation end-to-end. The command tests discovery, challenge formats, error handling, and the full payment flow." Agents test-pay with `npx @stripe/link-cli mpp pay` or the Tempo CLI.”
• [claimed-docs] https://docs.stripe.com/mcp.md“Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirmation before it takes certain `stripe_api_write` actions, such as refunds and outbound payments." The human reviews an approval URL; "When you click Approve, Stripe provides the agent with an approval token, but you need to tell the agent to retry the operation", and "If you don’t approve the action within 24 hours, it expires."”

Subscribe to events via webhooksweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

• [claimed-docs] https://docs.stripe.com/agentic-commerce/for-sellers.md“Agent orders flow through standard Stripe rails with per-agent attribution: "Stripe sends `checkout.session.completed` after the agent completes an order. Each order generates a unique `checkout.session.completed` event." In the Dashboard, orders appear on the Transactions page "where they’re tagged with the originating agent" and "You can also filter transactions by agent names." The field reference exposes `CheckoutSessions.PaymentIntent.agent_details` (Private preview), and sellers can batch — "Instead of fulfilling each order individually, bulk fulfill orders" via the List CheckoutSessions endpoint.”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/for-sellers.md“Merchant onboarding is Dashboard self-serve — "Use Agentic Commerce Suite (ACS) to start selling through agents with a single integration", "choose to onboard as a seller", then per-agent consent: "Find the agent you want to sell through and review its terms" and "We send the agent an approval request that the agent must accept" ("ACS is available in the US, Canada, and select European countries", 34 country codes listed). Catalog publishing is a CSV feed ("Format your feed as a CSV where each row is a product or variant") uploaded via the v2 Product Catalog Import API to a presigned URL ("The maximum file size is 4 GB"); cadence is product data "Once per day" and, for inventory/pricing, "in most cases, uploading inventory and pricing data every 15 minutes is enough". Deletion semantics are explicit ("In replace mode, any product not included in the uploaded file is permanently deleted from Stripe’s catalog"), indexing completes via v2.commerce.product_catalog.imports succeeded / succeeded_with_errors / failed webhooks with a per-row error CSV, and restricted keys need Product Catalog Imports write permission ("Without this permission, API requests return a `403` error").”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/for-agents.md?agent-checkout-mode=full“For agent builders, the embedded mode manages "the full checkout lifecycle through Stripe, including product feed ingestion, cart management, fulfillment, and payment collection" — "Stripe handles routing, authentication, error retries, and shared payment token (SPT) creation so you don’t need to integrate directly with each seller", and after confirm "Stripe routes the token to the seller for payment processing, so you don’t need to manage the token’s lifecycle" (completion signalled by the `delegated_checkout.requested_session.completed` webhook). Access is agreement-gated: "An OCA is a required connection between your agent and a seller that enables agentic commerce flows. Only a seller can initiate an OCA request", "After both parties confirm the OCA, it authorizes data access between your agent and the seller", and "Either party can terminate an OCA at any time." Caveats are explicit: "Agentic Commerce Suite is private preview and is available in the US, Canada, and select European countries. It supports purchases of physical goods", and embedding agents "might be considered marketplace facilitators (MPFs) with tax collection and remittance obligations."”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/concepts/shared-payment-tokens.md?agent-seller=agent“"Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases." The issuing agent must "Set usage limits, including currency, maximum amount, and expiration window" (usage_limits currency / max_amount / expires_at in the create call), and can "Revoke the SPT at any time to prevent the seller from using it to create a payment" — "Sellers can’t create a payment with a revoked SPT." "An SPT functions as a state machine" across active / requires_action / deactivated, with webhooks for each transition (for `shared_payment.issued_token.used`: "You receive this event when the seller uses the SPT").”

Explore an interactive API reference with runnable examplesweight 2

2 (weight) × 4 (quality) × 0.6 (partial) = 4.8 of 20 max

• [claimed-docs] https://docs.stripe.com/sandboxes.md“Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymous Stripe sandbox with working API keys. No account registration required.”
• [claimed-docs] https://docs.stripe.com/mcp.md“The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe’s knowledge base, including documentation and support articles.”
• [probe] https://docs.stripe.com/mcp“PROBE runtime (recorded 2026-09-14): Stripe's hosted MCP server is live and gated exactly as documented — a keyless JSON-RPC initialize POST to https://mcp.stripe.com answered HTTP 401 with the OAuth challenge pointing at docs.stripe.com/mcp, the per-spec auth contract an agent reads before connecting.”
• [probe] https://docs.stripe.com/skills.md“PROBE runtime (recorded 2026-09-14): the machine-readable skills catalog is live at the documented keyless well-known URL — https://docs.stripe.com/.well-known/skills/index.json returns the JSON index of Stripe-maintained agent skills (connect-recommend, stripe-best-practices, stripe-directory, ...).”
• [probe] https://docs.stripe.com/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/api/openapi.json, https://docs.stripe.com/.well-known/openapi.json)”
• [probe] https://docs.stripe.com/agentic-commerce.md“PROBE docs-md: HTTP 200 at https://docs.stripe.com/agentic-commerce.md # Agentic commerce Sell through agents, or embed commerce into your AI interface. Agentic commerce uses AI agents to s”

Download a machine-readable API spec (OpenAPI or equivalent)weight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

• [probe] https://docs.stripe.com/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/api/openapi.json, https://docs.stripe.com/.well-known/openapi.json)”

Test against a sandbox environment without touching production dataweight 1

1 (weight) × 7 (quality) × 1.0 (full) = 7.0 of 10 max

• [claimed-docs] https://docs.stripe.com/sandboxes.md“Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymous Stripe sandbox with working API keys. No account registration required.”

Rely on versioned APIs with a documented deprecation policyweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

• [claimed-docs] https://docs.stripe.com/agentic-commerce.md“Stripe's agentic-commerce hub is explicitly chat-native: "Buyers can browse products, get personalized recommendations, and complete purchases without leaving the conversation", and "Agents can also act on behalf of the people who use them, making purchases with a customer-controlled wallet and retrieving permissioned financial insights from connected accounts." Sellers get "Share product catalog with agents", "Enable agent to complete checkout", and "Receive payment credentials from agents" over UCP or ACP, or "monetize your API or service using machine payments" over MPP/x402, while agent builders can "Embed checkout flows in chats or advertisements". The agents-as-intermediaries side ("They present product feeds, manage carts and checkout, and accept payments") is gated: "This feature is in private preview."”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/for-agents.md?agent-checkout-mode=full“For agent builders, the embedded mode manages "the full checkout lifecycle through Stripe, including product feed ingestion, cart management, fulfillment, and payment collection" — "Stripe handles routing, authentication, error retries, and shared payment token (SPT) creation so you don’t need to integrate directly with each seller", and after confirm "Stripe routes the token to the seller for payment processing, so you don’t need to manage the token’s lifecycle" (completion signalled by the `delegated_checkout.requested_session.completed` webhook). Access is agreement-gated: "An OCA is a required connection between your agent and a seller that enables agentic commerce flows. Only a seller can initiate an OCA request", "After both parties confirm the OCA, it authorizes data access between your agent and the seller", and "Either party can terminate an OCA at any time." Caveats are explicit: "Agentic Commerce Suite is private preview and is available in the US, Canada, and select European countries. It supports purchases of physical goods", and embedding agents "might be considered marketplace facilitators (MPFs) with tax collection and remittance obligations."”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/for-sellers/custom.md“The ACP-style custom integration has sellers "implement a reverse API that defines the requests Stripe sends to your commerce backend and the response shapes your backend returns" — "When an agent routes a checkout request through Stripe, Stripe calls these endpoints on your behalf." Checkout create/update/confirm hooks move a session through the documented statuses "incomplete | ready_for_payment | requires_escalation | processing | completed | canceled"; on confirm the seller receives a shared payment token — a "scoped grant of the customer’s payment method from the agent to your" Stripe profile "with specific usage and expiration limits" — and resolves it into credentials whose type "is either `agentic_token` or `dpan`". "In collaboration with the card networks, Stripe might use tokens issued through network programs such as Mastercard’s Agent Pay and Visa’s Intelligent Commerce programs on your behalf." Geography and access are gated: "Agentic Commerce Suite (ACS) is available in the US." and onboarding the endpoint requires the waitlist.”

Do everything through the API that I can do in the UIweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

• [claimed-docs] https://docs.stripe.com/agentic-commerce/for-sellers.md“Merchant onboarding is Dashboard self-serve — "Use Agentic Commerce Suite (ACS) to start selling through agents with a single integration", "choose to onboard as a seller", then per-agent consent: "Find the agent you want to sell through and review its terms" and "We send the agent an approval request that the agent must accept" ("ACS is available in the US, Canada, and select European countries", 34 country codes listed). Catalog publishing is a CSV feed ("Format your feed as a CSV where each row is a product or variant") uploaded via the v2 Product Catalog Import API to a presigned URL ("The maximum file size is 4 GB"); cadence is product data "Once per day" and, for inventory/pricing, "in most cases, uploading inventory and pricing data every 15 minutes is enough". Deletion semantics are explicit ("In replace mode, any product not included in the uploaded file is permanently deleted from Stripe’s catalog"), indexing completes via v2.commerce.product_catalog.imports succeeded / succeeded_with_errors / failed webhooks with a per-row error CSV, and restricted keys need Product Catalog Imports write permission ("Without this permission, API requests return a `403` error").”
• [claimed-docs] https://docs.stripe.com/mcp.md“Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirmation before it takes certain `stripe_api_write` actions, such as refunds and outbound payments." The human reviews an approval URL; "When you click Approve, Stripe provides the agent with an approval token, but you need to tell the agent to retry the operation", and "If you don’t approve the action within 24 hours, it expires."”
• [claimed-docs] https://docs.stripe.com/mcp.md“The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API”
• [claimed-docs] https://docs.stripe.com/keys/restricted-api-keys.md“RAKs are the recommended type of key for API keys you give to AI agents.”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/for-sellers.md“Agent orders flow through standard Stripe rails with per-agent attribution: "Stripe sends `checkout.session.completed` after the agent completes an order. Each order generates a unique `checkout.session.completed` event." In the Dashboard, orders appear on the Transactions page "where they’re tagged with the originating agent" and "You can also filter transactions by agent names." The field reference exposes `CheckoutSessions.PaymentIntent.agent_details` (Private preview), and sellers can batch — "Instead of fulfilling each order individually, bulk fulfill orders" via the List CheckoutSessions endpoint.”

Export all of my data in open formats and leaveweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Read the product's source under an open licenseweight 2

2 (weight) × 4 (quality) × 0.6 (partial) = 4.8 of 20 max

• [claimed-docs] https://www.agenticcommerce.dev/“"ACP is open source and community-designed under the Apache 2.0 license. Businesses can implement the specification to transact with any AI agent or payment processor." Steering is disclosed on the site itself: "Stripe and OpenAI developed the Agentic Commerce Protocol to define a common language for how agents and businesses transact", "OpenAI is the first AI platform to implement ACP with ChatGPT", Stripe is "the first compatible PSP with its Shared Payment Token", and the contributor contact routes to acp@stripe.com. Listing is not automatic: "If your business wants to participate in ChatGPT, you'll need to apply."”
• [github] https://github.com/stripe/link-cli“The CLI can produce one of three credential types: A virtual card (PAN)... A Link Pay Token (LPT)... A Shared Payment Token (SPT)”
• [probe] https://docs.stripe.com/agentic-commerce/link-cli.md“PROBE runtime (recorded 2026-09-14): the Link CLI — the agent-wallet client documented for retrieving one-time-use payment credentials and permissioned financial data — is published on the public npm registry (npm view @stripe/link-cli → 0.19.2; source at github.com/stripe/link-cli).”

Self-host the core productweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Get AI-generated insights and suggestions from my data inside the productweight 2

2 (weight) × 4 (quality) × 0.6 (partial) = 4.8 of 20 max

• [claimed-docs] https://docs.stripe.com/agentic-commerce.md“Buyers can browse products, get personalized recommendations, and complete purchases without leaving the conversation.”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/link-cli.md“"Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to complete purchases, and retrieve permissioned financial data to answer questions about spending, balances, and trends." Every spend is human-gated: "Customers approve each request on the Link website or in the mobile app. Agent payments support one-time-use virtual cards and shared payment tokens." Wallet guides cover "Search products and complete payments with UCP" and how to "pay merchants that accept machine payments over HTTP 402", and the tool is agent-legible: "Your agent can inspect the full CLI documentation with `link-cli --llms-full`".”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/link-cli.md“retrieve permissioned financial data to answer questions about spending, balances, and trends.”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/link-cli.md““What did I spend on dining this month?””

Set up automations that run autonomously in the backgroundweight 2

2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max

• [claimed-docs] https://docs.stripe.com/payments/machine.md“"Machine payments let agents pay for APIs and services programmatically. Your server returns a payment challenge, the agent presents a valid payment credential, and Stripe settles the payment to your Stripe balance." Minimums are documented per rail: for card payments through SPTs "the minimum amount is 0.50 USD", for stablecoins "the minimum amount is 0.01" USDC — across MPP on Tempo (USDC.e) and Solana (USDC) and x402 on Base (USDC) — and "Stablecoin payments are available to businesses in all US states, except New York." Settlement stays on-platform: "Payments land directly in your Stripe balance and settle in fiat. Metrics, reporting, and multi-currency payouts work the same as any other payment in Stripe", with refunds available through the standard Refunds API and Dashboard per the features table.”
• [claimed-docs] https://docs.stripe.com/payments/machine/mpp.md“MPP "is an open protocol that lets agents pay for your APIs and services programmatically without a checkout UI, co-authored by Stripe and Tempo": on an unpaid request "your server returns an HTTP `402` response with payment details", then "The agent authorizes the payment, retries the request, and gets access to the paid resource along with a receipt." The docs ship a one-prompt agent build path ("Read https://docs.stripe.com/payments/machine/mpp.md?lang=node, and monetize my API using MPP to charge 0.50 USD per API call") and a conformance CLI: "Run `mppx validate` to automatically verify your implementation end-to-end. The command tests discovery, challenge formats, error handling, and the full payment flow." Agents test-pay with `npx @stripe/link-cli mpp pay` or the Tempo CLI.”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/concepts/shared-payment-tokens.md?agent-seller=agent“"Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases." The issuing agent must "Set usage limits, including currency, maximum amount, and expiration window" (usage_limits currency / max_amount / expires_at in the create call), and can "Revoke the SPT at any time to prevent the seller from using it to create a payment" — "Sellers can’t create a payment with a revoked SPT." "An SPT functions as a state machine" across active / requires_action / deactivated, with webhooks for each transition (for `shared_payment.issued_token.used`: "You receive this event when the seller uses the SPT").”
• [claimed-docs] https://docs.stripe.com/mcp.md“Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirmation before it takes certain `stripe_api_write` actions, such as refunds and outbound payments." The human reviews an approval URL; "When you click Approve, Stripe provides the agent with an approval token, but you need to tell the agent to retry the operation", and "If you don’t approve the action within 24 hours, it expires."”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/link-cli.md“"Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to complete purchases, and retrieve permissioned financial data to answer questions about spending, balances, and trends." Every spend is human-gated: "Customers approve each request on the Link website or in the mobile app. Agent payments support one-time-use virtual cards and shared payment tokens." Wallet guides cover "Search products and complete payments with UCP" and how to "pay merchants that accept machine payments over HTTP 402", and the tool is agent-legible: "Your agent can inspect the full CLI documentation with `link-cli --llms-full`".”

Delegate tasks to a built-in AI assistant inside the productweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Operate the product with natural-language commandsweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

• [claimed-docs] https://docs.stripe.com/agentic-commerce.md“Buyers can browse products, get personalized recommendations, and complete purchases without leaving the conversation.”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/link-cli.md““Buy me this book from Stripe Press””
• [claimed-docs] https://docs.stripe.com/agentic-commerce/link-cli.md““What did I spend on dining this month?””
• [claimed-docs] https://docs.stripe.com/agentic-commerce/link-cli.md“"Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to complete purchases, and retrieve permissioned financial data to answer questions about spending, balances, and trends." Every spend is human-gated: "Customers approve each request on the Link website or in the mobile app. Agent payments support one-time-use virtual cards and shared payment tokens." Wallet guides cover "Search products and complete payments with UCP" and how to "pay merchants that accept machine payments over HTTP 402", and the tool is agent-legible: "Your agent can inspect the full CLI documentation with `link-cli --llms-full`".”
• [claimed-docs] https://docs.stripe.com/mcp.md“The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API”
• [claimed-docs] https://docs.stripe.com/skills.md“Install instructions that help AI agents create more accurate Stripe integrations.”
• [probe] https://docs.stripe.com/mcp“PROBE runtime (recorded 2026-09-14): Stripe's hosted MCP server is live and gated exactly as documented — a keyless JSON-RPC initialize POST to https://mcp.stripe.com answered HTTP 401 with the OAuth challenge pointing at docs.stripe.com/mcp, the per-spec auth contract an agent reads before connecting.”
• [probe] https://docs.stripe.com/agentic-commerce/link-cli.md“PROBE runtime (recorded 2026-09-14): the Link CLI — the agent-wallet client documented for retrieving one-time-use payment credentials and permissioned financial data — is published on the public npm registry (npm view @stripe/link-cli → 0.19.2; source at github.com/stripe/link-cli).”

Perform bulk operations across many items at onceweight 2

2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max

• [claimed-docs] https://docs.stripe.com/agentic-commerce/for-sellers.md“Merchant onboarding is Dashboard self-serve — "Use Agentic Commerce Suite (ACS) to start selling through agents with a single integration", "choose to onboard as a seller", then per-agent consent: "Find the agent you want to sell through and review its terms" and "We send the agent an approval request that the agent must accept" ("ACS is available in the US, Canada, and select European countries", 34 country codes listed). Catalog publishing is a CSV feed ("Format your feed as a CSV where each row is a product or variant") uploaded via the v2 Product Catalog Import API to a presigned URL ("The maximum file size is 4 GB"); cadence is product data "Once per day" and, for inventory/pricing, "in most cases, uploading inventory and pricing data every 15 minutes is enough". Deletion semantics are explicit ("In replace mode, any product not included in the uploaded file is permanently deleted from Stripe’s catalog"), indexing completes via v2.commerce.product_catalog.imports succeeded / succeeded_with_errors / failed webhooks with a per-row error CSV, and restricted keys need Product Catalog Imports write permission ("Without this permission, API requests return a `403` error").”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/for-sellers.md“Agent orders flow through standard Stripe rails with per-agent attribution: "Stripe sends `checkout.session.completed` after the agent completes an order. Each order generates a unique `checkout.session.completed` event." In the Dashboard, orders appear on the Transactions page "where they’re tagged with the originating agent" and "You can also filter transactions by agent names." The field reference exposes `CheckoutSessions.PaymentIntent.agent_details` (Private preview), and sellers can batch — "Instead of fulfilling each order individually, bulk fulfill orders" via the List CheckoutSessions endpoint.”

Define rules that trigger actions automatically on eventsweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

• [claimed-docs] https://docs.stripe.com/agentic-commerce/for-sellers.md“Agent orders flow through standard Stripe rails with per-agent attribution: "Stripe sends `checkout.session.completed` after the agent completes an order. Each order generates a unique `checkout.session.completed` event." In the Dashboard, orders appear on the Transactions page "where they’re tagged with the originating agent" and "You can also filter transactions by agent names." The field reference exposes `CheckoutSessions.PaymentIntent.agent_details` (Private preview), and sellers can batch — "Instead of fulfilling each order individually, bulk fulfill orders" via the List CheckoutSessions endpoint.”
• [claimed-docs] https://docs.stripe.com/agentic-commerce/concepts/shared-payment-tokens.md?agent-seller=agent“"Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases." The issuing agent must "Set usage limits, including currency, maximum amount, and expiration window" (usage_limits currency / max_amount / expires_at in the create call), and can "Revoke the SPT at any time to prevent the seller from using it to create a payment" — "Sellers can’t create a payment with a revoked SPT." "An SPT functions as a state machine" across active / requires_action / deactivated, with webhooks for each transition (for `shared_payment.issued_token.used`: "You receive this event when the seller uses the SPT").”
• [claimed-docs] https://docs.stripe.com/mcp.md“Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirmation before it takes certain `stripe_api_write` actions, such as refunds and outbound payments." The human reviews an approval URL; "When you click Approve, Stripe provides the agent with an approval token, but you need to tell the agent to retry the operation", and "If you don’t approve the action within 24 hours, it expires."”

Schedule recurring jobs or workflowsweight 2

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Version, review, and roll back my automationsweight 1

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh