Rank #2 of 6 in Marketplace & Platform Payments
Install
npm install 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 |
| Connectthis page | 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 Commerce | 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 Connect 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 https://api.stripe.com/v1/accounts | head -4 # Connect accounts API, keyless → 401recorded 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
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
Embedded experience — stories about embedded experience in this arenaEmbedded experienceevidence →
Stories about embedded experience in this arena
Funds routing — stories about funds routing in this arenaFunds routingevidence →
Stories about funds routing in this arena
Marketplace disputes — stories about marketplace disputes in this arenaMarketplace disputesevidence →
Stories about marketplace disputes in this arena
Marketplace payouts — stories about marketplace payouts in this arenaMarketplace payoutsevidence →
Stories about marketplace payouts in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Payfac liability — stories about payfac liability in this arenaPayfac liabilityevidence →
Stories about payfac liability in this arena
Platform agent access — stories about platform agent access in this arenaPlatform agent accessevidence →
Stories about platform agent access in this arena
Platform ledger — stories about platform ledger in this arenaPlatform ledgerevidence →
Stories about platform ledger in this arena
Platform monetization — stories about platform monetization in this arenaPlatform monetizationevidence →
Stories about platform monetization in this arena
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Seller onboarding — stories about seller onboarding in this arenaSeller onboardingevidence →
Stories about seller onboarding in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Stripe Connect stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
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
✓8/10
unlocks → Machine-readable spec · Versioning policy · The platform is ready for agent buyers — documented support for agent-initiated checkout on marketplace transactions (agentic-commerce protocols, delegated payment credentials) that works with split funds flows
Subscribe to events via webhooks
✓7/10
Build against official SDKs
~6/10
Issue scoped/least-privilege API credentials for an agent
n/an/a
Connect an agent via an official MCP server
✓7/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
~6/10
Explore an interactive API reference with runnable examples
—0/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
n/an/a
Operate the product with natural-language commands
~5/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
n/an/a
Set up automations that run autonomously in the background
~4/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Embedded experience — stories about embedded experience in this arenaEmbedded experience
Stories about embedded experience in this arena
Seller-facing surfaces are embeddable — white-label components or APIs for balances, payouts, and transaction history that live inside my product under my brand
~6/10
In-person works on the same stack — terminals or tap-to-pay SDKs that settle into the same seller balances and reporting as online payments
—–
Sellers can self-serve their money questions — per-seller statements, payout reconciliation reports, and exports that let their bookkeeper close the month without contacting me
—0/10
Funds routing — stories about funds routing in this arenaFunds routing
Stories about funds routing in this arena
Funds can wait — hold seller funds in a balance until delivery or dispute windows pass, release on my schedule or trigger, with the escrow-like mechanics and their limits documented
~5/10
Refunds and chargebacks that exceed a seller's balance are recoverable — automatic debits against future earnings or their bank account, with the liability order documented
—0/10
Split one charge among any set of parties — route funds to multiple sellers, take my cut, and reverse or adjust the split later, all as first-class API objects
~7/10
Marketplace disputes — stories about marketplace disputes in this arenaMarketplace disputes
Stories about marketplace disputes in this arena
Disputes are managed per seller — chargebacks land against the right sub-merchant, evidence is submitted via API or dashboard, and outcomes flow back into seller balances automatically
~5/10
Watch risk across my seller portfolio — fraud and credit-risk signals per sub-merchant, alerts on anomalous sellers, and tools to pause payouts or offboard bad actors
~4/10
Marketplace payouts — stories about marketplace payouts in this arenaMarketplace payouts
Stories about marketplace payouts in this arena
International sellers get paid properly — local-currency payouts, documented FX handling, and settlement to local bank rails rather than expensive wires
~3/10
Payouts run on the schedule each seller needs — daily, weekly, monthly, or manual, plus instant payouts to cards or real-time rails where supported, configurable per seller
✓8/10
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Payfac liability — stories about payfac liability in this arenaPayfac liability
Stories about payfac liability in this arena
There's a path up the stack — start on the managed model and graduate toward registered payment facilitation with more economics and control, without replatforming
~4/10
The responsibility split is explicit — who owns KYC/AML, card-network compliance, fraud losses, and seller misconduct between me and the provider, in the docs rather than the contract's fine print
—0/10
Seller tax reporting is handled — 1099-K thresholds tracked, forms generated, delivered, and filed, with the data corrections workflow documented
—–
Platform agent access — stories about platform agent access in this arenaPlatform agent access
Stories about platform agent access in this arena
An agent can work the money side — read balances and payouts, investigate a seller's missing payout, draft dispute evidence — against documented, agent-usable surfaces
~7/10
An agent can run seller operations — create accounts, drive onboarding to completion, and answer requirements-due states through the API or an MCP surface with scoped credentials
~5/10
The platform is ready for agent buyers — documented support for agent-initiated checkout on marketplace transactions (agentic-commerce protocols, delegated payment credentials) that works with split funds flows
—–
Platform ledger — stories about platform ledger in this arenaPlatform ledger
Stories about platform ledger in this arena
Platform funds have a home — clarity on where in-flight and held funds sit, whether balances earn yield, and how money is segregated from the provider's own accounts
~4/10
The platform's money is legible — balances by seller and by my own fee accounts, every movement traceable from charge through split to payout, reconcilable to the penny
~7/10
Reconciliation is automatable — settlement and balance reports per seller and rolled up, delivered as files or APIs my finance stack consumes on schedule
~4/10
Platform monetization — stories about platform monetization in this arenaPlatform monetization
Stories about platform monetization in this arena
Payments are a revenue line — take an application fee or markup on every transaction, set per-seller pricing, and see my payments revenue reported distinctly from processing costs
~6/10
I control the economics — a documented buy rate from the provider and freedom to set the sell rate my sellers see, with interchange-level cost visibility to manage the spread
~4/10
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Seller onboarding — stories about seller onboarding in this arenaSeller onboarding
Stories about seller onboarding in this arena
Sellers can join from where they are — supported onboarding countries, local payment methods, and local-currency settlement documented as a coverage map, not discovered ticket by ticket
—0/10
Onboard a seller through the API — KYB and KYC, bank account linking, and terms acceptance — with hosted flows and embeddable components when I don't want to build the forms
✓8/10
Onboarding friction is tunable — collect the minimum to start selling and gather the rest before payout thresholds, with clear requirements-due states per seller
~5/10
Sorted by importance (agentic first) (high → low) · 53/53 stories · click a row’s chevron for the rationale and evidence
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 | 8/10 | Tprobed | |
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 | 7/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 | |
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 | 8/10 | Tprobed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Xcommunity | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Tprobed | |
Build against official SDKs G Agent access | 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 | 6/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 | 5/10 | Tprobed | |
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 | 4/10 | Tprobed | |
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 | ||
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 | none | 0/10 | ||
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 | n/a | untested | none yet | |
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 | n/a | untested | none yet | |
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 | untested | none yet | |
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 | partial | 6/10 | Cclaimed | |
Onboard a seller through the API — KYB and KYC, bank account linking, and terms acceptance — with hosted flows and embeddable components when I don't want to build the forms C Onboarding api | developer | Seller onboarding — stories about seller onboarding in this arenaSeller onboarding | 3 | full | 8/10 | Xcommunity | |
Payouts run on the schedule each seller needs — daily, weekly, monthly, or manual, plus instant payouts to cards or real-time rails where supported, configurable per seller C Payout schedules | ops user | Marketplace payouts — stories about marketplace payouts in this arenaMarketplace payouts | 3 | full | 8/10 | Cclaimed | |
Split one charge among any set of parties — route funds to multiple sellers, take my cut, and reverse or adjust the split later, all as first-class API objects C Splits | developer | Funds routing — stories about funds routing in this arenaFunds routing | 3 | partial | 7/10 | Cclaimed | |
The platform's money is legible — balances by seller and by my own fee accounts, every movement traceable from charge through split to payout, reconcilable to the penny C Ledger visibility | finance lead | Platform ledger — stories about platform ledger in this arenaPlatform ledger | 3 | partial | 7/10 | Xcommunity | |
Payments are a revenue line — take an application fee or markup on every transaction, set per-seller pricing, and see my payments revenue reported distinctly from processing costs G Application fees | founder | Platform monetization — stories about platform monetization in this arenaPlatform monetization | 3 | partial | 6/10 | Xcommunity | |
An agent can run seller operations — create accounts, drive onboarding to completion, and answer requirements-due states through the API or an MCP surface with scoped credentials C Agent onboarding | ai-native user | Platform agent access — stories about platform agent access in this arenaPlatform agent access | 3 | partial | 5/10 | Tprobed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 5/10 | Cclaimed | |
Disputes are managed per seller — chargebacks land against the right sub-merchant, evidence is submitted via API or dashboard, and outcomes flow back into seller balances automatically C Dispute handling | ops user | Marketplace disputes — stories about marketplace disputes in this arenaMarketplace disputes | 3 | partial | 5/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | 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 | |
An agent can work the money side — read balances and payouts, investigate a seller's missing payout, draft dispute evidence — against documented, agent-usable surfaces C Agent money ops | ai-native user | Platform agent access — stories about platform agent access in this arenaPlatform agent access | 2 | partial | 7/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 | 7/10 | Tprobed | |
Seller-facing surfaces are embeddable — white-label components or APIs for balances, payouts, and transaction history that live inside my product under my brand C Embedded components | developer | Embedded experience — stories about embedded experience in this arenaEmbedded experience | 2 | partial | 6/10 | Cclaimed | |
Funds can wait — hold seller funds in a balance until delivery or dispute windows pass, release on my schedule or trigger, with the escrow-like mechanics and their limits documented C Holds release | developer | Funds routing — stories about funds routing in this arenaFunds routing | 2 | partial | 5/10 | Xcommunity | |
Onboarding friction is tunable — collect the minimum to start selling and gather the rest before payout thresholds, with clear requirements-due states per seller C Progressive requirements | ops user | Seller onboarding — stories about seller onboarding in this arenaSeller onboarding | 2 | partial | 5/10 | Cclaimed | |
I control the economics — a documented buy rate from the provider and freedom to set the sell rate my sellers see, with interchange-level cost visibility to manage the spread G Buy rates | finance lead | Platform monetization — stories about platform monetization in this arenaPlatform monetization | 2 | partial | 4/10 | Xcommunity | |
Platform funds have a home — clarity on where in-flight and held funds sit, whether balances earn yield, and how money is segregated from the provider's own accounts C Funds custody | finance lead | Platform ledger — stories about platform ledger in this arenaPlatform ledger | 2 | partial | 4/10 | Xcommunity | |
Reconciliation is automatable — settlement and balance reports per seller and rolled up, delivered as files or APIs my finance stack consumes on schedule C Recon exports | developer | Platform ledger — stories about platform ledger in this arenaPlatform ledger | 2 | partial | 4/10 | Cclaimed | |
There's a path up the stack — start on the managed model and graduate toward registered payment facilitation with more economics and control, without replatforming C Graduation path | founder | Payfac liability — stories about payfac liability in this arenaPayfac liability | 2 | partial | 4/10 | Cclaimed | |
Watch risk across my seller portfolio — fraud and credit-risk signals per sub-merchant, alerts on anomalous sellers, and tools to pause payouts or offboard bad actors C Portfolio risk | ops user | Marketplace disputes — stories about marketplace disputes in this arenaMarketplace disputes | 2 | partial | 4/10 | Cclaimed | |
International sellers get paid properly — local-currency payouts, documented FX handling, and settlement to local bank rails rather than expensive wires C Cross border | finance lead | Marketplace payouts — stories about marketplace payouts in this arenaMarketplace payouts | 2 | partial | 3/10 | Xcommunity | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | 0/10 | ||
Refunds and chargebacks that exceed a seller's balance are recoverable — automatic debits against future earnings or their bank account, with the liability order documented C Negative balances | finance lead | Funds routing — stories about funds routing in this arenaFunds routing | 2 | none | 0/10 | ||
Sellers can join from where they are — supported onboarding countries, local payment methods, and local-currency settlement documented as a coverage map, not discovered ticket by ticket C Global coverage | founder | Seller onboarding — stories about seller onboarding in this arenaSeller onboarding | 2 | none | 0/10 | ||
Sellers can self-serve their money questions — per-seller statements, payout reconciliation reports, and exports that let their bookkeeper close the month without contacting me C Seller reporting | ops user | Embedded experience — stories about embedded experience in this arenaEmbedded experience | 2 | none | 0/10 | ||
The responsibility split is explicit — who owns KYC/AML, card-network compliance, fraud losses, and seller misconduct between me and the provider, in the docs rather than the contract's fine print C Responsibility split | ops user | Payfac liability — stories about payfac liability in this arenaPayfac liability | 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 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | untested | none yet | |
In-person works on the same stack — terminals or tap-to-pay SDKs that settle into the same seller balances and reporting as online payments C Omnichannel | founder with offline sellers | Embedded experience — stories about embedded experience in this arenaEmbedded experience | 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 | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
Seller tax reporting is handled — 1099-K thresholds tracked, forms generated, delivered, and filed, with the data corrections workflow documented C Tax forms | finance lead | Payfac liability — stories about payfac liability in this arenaPayfac liability | 2 | none | untested | none yet | |
The platform is ready for agent buyers — documented support for agent-initiated checkout on marketplace transactions (agentic-commerce protocols, delegated payment credentials) that works with split funds flows C Agentic commerce | developer | Platform agent access — stories about platform agent access in this arenaPlatform agent access | 2 | none | untested | none yet | |
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 36 stories with headroom
What would move Stripe Connect’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.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
The evidence pack contains only docs.stripe.com guide pages, an llms.txt probe, CLI/MCP mentions, and a failed openapi.json probe (404 on all candidate paths) — nothing documents an interactive API reference page or runnable/try-it code examples for Connect.
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 OpenAPI/swagger spec files at all standard locations returning 404, and no other evidence item shows a downloadable machine-readable API spec (only markdown docs, an MCP server, and CLI are documented).
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
Missing: any documentation of API version pinning, deprecation notices, changelog, or migration guides.
Platform agent access — stories about platform agent access in this arenaThe platform is ready for agent buyers — documented support for agent-initiated checkout on marketplace transactions (agentic-commerce protocols, delegated payment credentials) that works with split funds flows
nonemoves PA Scoreimpact 20
Missing: any documentation of agent/AI buyer checkout support, delegated payment credential mechanisms, or agentic-commerce protocol integration with split funds.
Automation depth — how much of the product can run unattendedPerform bulk operations across many items at once
nonemoves PA Scoreimpact 20
Missing: documented bulk/batch API endpoints, evidence of batch job or async bulk-processing tooling, and any AI-native automation examples operating on many items simultaneously.
Automation depth — how much of the product can run unattendedSchedule recurring jobs or workflows
nonemoves PA Scoreimpact 20
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Seller onboarding — stories about seller onboarding in this arenaSellers can join from where they are — supported onboarding countries, local payment methods, and local-currency settlement documented as a coverage map, not discovered ticket by ticket
nonemoves PA Scoreimpact 20
Missing: an explicit supported-countries list, a local-payment-methods matrix, and a local-currency settlement reference, plus confirmation these are unified rather than discovered piecemeal.
Embedded experience — stories about embedded experience in this arenaIn-person works on the same stack — terminals or tap-to-pay SDKs that settle into the same seller balances and reporting as online payments
nonemoves PA Scoreimpact 20
The evidence pack covers Connect's online payment splitting, onboarding, payouts, identity verification, and dashboard features, but contains no mention of Stripe Terminal, in-person/tap-to-pay hardware or SDKs, or how such in-person payments would settle into the same connected-account balances/reporting as online charges.
Showing the top 8 of 36 — 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 map6 surfaces · 29 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Connect docs26 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Subscribe to events via webhooks
- Set up automations that run autonomously in the background
- Test against a sandbox environment without touching production data
- Define rules that trigger actions automatically on events
- Seller-facing surfaces are embeddable — white-label components or APIs for balances, payouts, and transaction history that live inside my product under my brand
- Funds can wait — hold seller funds in a balance until delivery or dispute windows pass, release on my schedule or trigger, with the escrow-like mechanics and their limits documented
- Split one charge among any set of parties — route funds to multiple sellers, take my cut, and reverse or adjust the split later, all as first-class API objects
- Disputes are managed per seller — chargebacks land against the right sub-merchant, evidence is submitted via API or dashboard, and outcomes flow back into seller balances automatically
- Watch risk across my seller portfolio — fraud and credit-risk signals per sub-merchant, alerts on anomalous sellers, and tools to pause payouts or offboard bad actors
- International sellers get paid properly — local-currency payouts, documented FX handling, and settlement to local bank rails rather than expensive wires
- Payouts run on the schedule each seller needs — daily, weekly, monthly, or manual, plus instant payouts to cards or real-time rails where supported, configurable per seller
- Do everything through the API that I can do in the UI
- There's a path up the stack — start on the managed model and graduate toward registered payment facilitation with more economics and control, without replatforming
- An agent can work the money side — read balances and payouts, investigate a seller's missing payout, draft dispute evidence — against documented, agent-usable surfaces
- An agent can run seller operations — create accounts, drive onboarding to completion, and answer requirements-due states through the API or an MCP surface with scoped credentials
- Platform funds have a home — clarity on where in-flight and held funds sit, whether balances earn yield, and how money is segregated from the provider's own accounts
- The platform's money is legible — balances by seller and by my own fee accounts, every movement traceable from charge through split to payout, reconcilable to the penny
- Reconciliation is automatable — settlement and balance reports per seller and rolled up, delivered as files or APIs my finance stack consumes on schedule
- Payments are a revenue line — take an application fee or markup on every transaction, set per-seller pricing, and see my payments revenue reported distinctly from processing costs
- I control the economics — a documented buy rate from the provider and freedom to set the sell rate my sellers see, with interchange-level cost visibility to manage the spread
- Onboard a seller through the API — KYB and KYC, bank account linking, and terms acceptance — with hosted flows and embeddable components when I don't want to build the forms
- Onboarding friction is tunable — collect the minimum to start selling and gather the rest before payout thresholds, with clear requirements-due states per seller
MCP docs8 stories
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Build against official SDKs
- Set up automations that run autonomously in the background
- Operate the product with natural-language commands
- Do everything through the API that I can do in the UI
- An agent can work the money side — read balances and payouts, investigate a seller's missing payout, draft dispute evidence — against documented, agent-usable surfaces
- An agent can run seller operations — create accounts, drive onboarding to completion, and answer requirements-due states through the API or an MCP surface with scoped credentials
Hacker News8 stories
- Subscribe to events via webhooks
- Funds can wait — hold seller funds in a balance until delivery or dispute windows pass, release on my schedule or trigger, with the escrow-like mechanics and their limits documented
- International sellers get paid properly — local-currency payouts, documented FX handling, and settlement to local bank rails rather than expensive wires
- Platform funds have a home — clarity on where in-flight and held funds sit, whether balances earn yield, and how money is segregated from the provider's own accounts
- The platform's money is legible — balances by seller and by my own fee accounts, every movement traceable from charge through split to payout, reconcilable to the penny
- Payments are a revenue line — take an application fee or markup on every transaction, set per-seller pricing, and see my payments revenue reported distinctly from processing costs
- I control the economics — a documented buy rate from the provider and freedom to set the sell rate my sellers see, with interchange-level cost visibility to manage the spread
- Onboard a seller through the API — KYB and KYC, bank account linking, and terms acceptance — with hosted flows and embeddable components when I don't want to build the forms
Stripe CLI docs7 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Build against official SDKs
- Operate the product with natural-language commands
- Do everything through the API that I can do in the UI
- An agent can work the money side — read balances and payouts, investigate a seller's missing payout, draft dispute evidence — against documented, agent-usable surfaces
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 https://api.stripe.com/v1/accounts | head -4 # Connect accounts API, keyless → 401reproduced$ curl -si https://api.stripe.com/v1/accounts | head -4 # Connect accounts API, [redacted]less → 401 HTTP/2 401 server: nginx date: Tue, 15 Sep 2026 09:12:36 GMT content-type: application/json
$curl -sL https://docs.stripe.com/llms.txt | head -3reproduced$ curl -sL https://docs.stripe.com/llms.txt | head -3 # Stripe Documentation When installing Stripe packages, always check the npm registry for the latest version rather than relying on memorized version numbers. Run `npm view stripe version` or check https://www.npmjs.com/package/stripe before pinning a version. For Python, check https://pypi.org/project/stripe/. Never hardcode an old version number from training data — always install with `@latest` or verify the current version first.
$curl -si -X POST https://mcp.stripe.com/ -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # the remote MCP server Stripe documents at docs.stripe.com/mcpreproduced$ curl -si -X POST https://mcp.stripe.com/ -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # the remote MCP server Stripe documents at docs.stripe.com/mcp HTTP/2 401 www-authenticate: Bearer resource_metadata=https://mcp.stripe.com/.well-known/oauth-protected-resource
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
6 of 12 testable claims verified · 0 contradicted → integrity 50/100
18 distinct capability claims found in Stripe Connect’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
6
Verified
6
Unverified
0
Contradicted
17
Undersold
Verified (7)
“Embed a hosted onboarding component so connected accounts complete onboarding inside your own app”
Onboard a seller through the API — KYB and KYC, bank account linking, and terms acceptance — with hosted flows and embeddable components when I don't want to build the formsfullproof ↗
“Build a fully custom onboarding UI using the API instead of a hosted component”
Onboard a seller through the API — KYB and KYC, bank account linking, and terms acceptance — with hosted flows and embeddable components when I don't want to build the formsfullproof ↗
“Implement custom platform pricing/fee strategies for different payment use cases without writing code”
Payments are a revenue line — take an application fee or markup on every transaction, set per-seller pricing, and see my payments revenue reported distinctly from processing costspartialproof ↗
“Implement custom platform pricing/fee strategies for different payment use cases without writing code”
I control the economics — a documented buy rate from the provider and freedom to set the sell rate my sellers see, with interchange-level cost visibility to manage the spreadpartialproof ↗
“Embed Treasury so platform customers can hold funds, pay bills, earn cash back, and manage cashflow”
Platform funds have a home — clarity on where in-flight and held funds sit, whether balances earn yield, and how money is segregated from the provider's own accountspartialproof ↗
“Set up a webhook endpoint to listen for Connect account and payment events”
“Retrieve a connected account's balance via an API call authenticated as that account”
The platform's money is legible — balances by seller and by my own fee accounts, every movement traceable from charge through split to payout, reconcilable to the pennypartialproof ↗
Unverified (11)
“Collect a customer payment and automatically pay out a portion to a seller or service provider”
Split one charge among any set of parties — route funds to multiple sellers, take my cut, and reverse or adjust the split later, all as first-class API objectspartialproof ↗
“Embed a hosted onboarding component so connected accounts complete onboarding inside your own app”
Seller-facing surfaces are embeddable — white-label components or APIs for balances, payouts, and transaction history that live inside my product under my brandpartialproof ↗
“Create a charge and split the payment between the platform and sellers/service providers”
Split one charge among any set of parties — route funds to multiple sellers, take my cut, and reverse or adjust the split later, all as first-class API objectspartialproof ↗
“Manage payouts and external bank accounts for connected accounts”
Payouts run on the schedule each seller needs — daily, weekly, monthly, or manual, plus instant payouts to cards or real-time rails where supported, configurable per sellerfullproof ↗
“Manage payouts and external bank accounts for connected accounts”
Seller-facing surfaces are embeddable — white-label components or APIs for balances, payouts, and transaction history that live inside my product under my brandpartialproof ↗
“Review and take action on connected accounts from a management dashboard”
Watch risk across my seller portfolio — fraud and credit-risk signals per sub-merchant, alerts on anomalous sellers, and tools to pause payouts or offboard bad actorspartialproof ↗
“Allow connected accounts to access balances immediately after a successful charge”
Payouts run on the schedule each seller needs — daily, weekly, monthly, or manual, plus instant payouts to cards or real-time rails where supported, configurable per sellerfullproof ↗
“Schedule the frequency of automatic payouts to connected accounts”
Payouts run on the schedule each seller needs — daily, weekly, monthly, or manual, plus instant payouts to cards or real-time rails where supported, configurable per sellerfullproof ↗
“Test the full Connect integration (account creation, identity verification, payouts) before going live”
Test against a sandbox environment without touching production datapartialproof ↗
“Use built-in identity verification to reduce platform risk”
Watch risk across my seller portfolio — fraud and credit-risk signals per sub-merchant, alerts on anomalous sellers, and tools to pause payouts or offboard bad actorspartialproof ↗
“View all disputes filed against the platform and its connected accounts in the Dashboard”
Disputes are managed per seller — chargebacks land against the right sub-merchant, evidence is submitted via API or dashboard, and outcomes flow back into seller balances automaticallypartialproof ↗
Undersold (17)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Funds can wait — hold seller funds in a balance until delivery or dispute windows pass, release on my schedule or trigger, with the escrow-like mechanics and their limits documentedpartialproof ↗
International sellers get paid properly — local-currency payouts, documented FX handling, and settlement to local bank rails rather than expensive wirespartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
There's a path up the stack — start on the managed model and graduate toward registered payment facilitation with more economics and control, without replatformingpartialproof ↗
An agent can work the money side — read balances and payouts, investigate a seller's missing payout, draft dispute evidence — against documented, agent-usable surfacespartialproof ↗
An agent can run seller operations — create accounts, drive onboarding to completion, and answer requirements-due states through the API or an MCP surface with scoped credentialspartialproof ↗
Reconciliation is automatable — settlement and balance reports per seller and rolled up, delivered as files or APIs my finance stack consumes on schedulepartialproof ↗
Onboarding friction is tunable — collect the minimum to start selling and gather the rest before payout thresholds, with clear requirements-due states per sellerpartialproof ↗
Claims outside our story set (3)
Real capability claims found in Stripe Connect’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Platforms can provide payment-collection services to their own business customers”
source ↗“Represent each connected account with a unified identity that can have multiple configurations (e.g. merchant, customer)”
source ↗“Issue and manage virtual and physical cards at platform scale”
source ↗
Business model
Two modes: Stripe-handled pricing ($0 per account, Stripe bills sellers, optional revenue share) or platform-handled ($2 per monthly active account + 0.25% + $0.25 per payout, platform sets its own markup); instant payouts 1%.
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
