Rank #3 of 7 in Billing & Subscriptions
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 |
| Billingthis page | 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 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 Billing 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/subscriptions | head -4 # the subscription-lifecycle 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
Billing agent access — stories about billing agent access in this arenaBilling agent accessevidence →
Stories about billing agent access in this arena
Billing math — stories about billing math in this arenaBilling mathevidence →
Stories about billing math in this arena
Dunning recovery — stories about dunning recovery in this arenaDunning recoveryevidence →
Stories about dunning recovery in this arena
Entitlements — stories about entitlements in this arenaEntitlementsevidence →
Stories about entitlements in this arena
Invoicing tax — stories about invoicing tax in this arenaInvoicing taxevidence →
Stories about invoicing tax in this arena
Migration portability — stories about migration portability in this arenaMigration portabilityevidence →
Stories about migration portability in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Revenue recognition — stories about revenue recognition in this arenaRevenue recognitionevidence →
Stories about revenue recognition in this arena
Subscription lifecycle — stories about subscription lifecycle in this arenaSubscription lifecycleevidence →
Stories about subscription lifecycle in this arena
Usage metering — stories about usage metering in this arenaUsage meteringevidence →
Stories about usage metering in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Stripe Billing 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
✓9/10
unlocks → Scoped API keys · Machine-readable spec · Versioning policy · API sandbox · Full data export
Subscribe to events via webhooks
✓7/10
Build against official SDKs
~4/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
✓8/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
—0/10
Explore an interactive API reference with runnable examples
—–
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
—–
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
—0/10
Set up automations that run autonomously in the background
~6/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Billing agent access — stories about billing agent access in this arenaBilling agent access
Stories about billing agent access in this arena
An agent can operate my billing — create a subscription, apply a credit, change a plan — through a programmatic surface with scoped permissions
~6/10
An agent can answer questions about my billing state — MRR, delinquent accounts, upcoming renewals, a customer's invoices — by querying the platform directly
~6/10
Billing math — stories about billing math in this arenaBilling math
Stories about billing math in this arena
Dunning recovery — stories about dunning recovery in this arenaDunning recovery
Stories about dunning recovery in this arena
Expiring or replaced cards update themselves — network account updater, backup payment methods, and hosted update-payment pages
~4/10
Configure automated dunning sequences — branded emails, in-app banners, grace periods, and final-state rules like cancel vs unpaid
~4/10
Failed renewal payments are retried automatically on an ML- or schedule-optimized cadence that measurably recovers involuntary churn
~6/10
Entitlements — stories about entitlements in this arenaEntitlements
Stories about entitlements in this arena
Features and limits are modeled as entitlements attached to plans, and my application can check a customer's entitlements at runtime via API or SDK
~5/10
Change pricing without breaking existing subscribers — versioned plans, grandfathering, and bulk migration tools for moving cohorts to new prices
~4/10
Invoicing tax — stories about invoicing tax in this arenaInvoicing tax
Stories about invoicing tax in this arena
The platform generates compliant invoices, credit notes, and receipts — sequential numbering, custom fields, memos — delivered to customers automatically
~4/10
Bill customers in their local currency with per-currency price points and consolidated reporting in my home currency
~5/10
Sales tax, VAT, and GST are calculated on every invoice — natively or through a first-class tax integration — with the right registrations and rates
✓7/10
Migration portability — stories about migration portability in this arenaMigration portability
Stories about migration portability in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Revenue recognition — stories about revenue recognition in this arenaRevenue recognition
Stories about revenue recognition in this arena
I get MRR, churn, cohort retention, and LTV analytics computed from the billing source of truth, not a bolted-on BI export
!4/10
Invoices, payments, and recognition entries sync to my general ledger or ERP — QuickBooks, Xero, NetSuite — so the close doesn't need CSV surgery
—0/10
Revenue is recognized on an ASC 606 / IFRS 15 basis — deferred revenue schedules and audit-ready recognition reports straight from billing data
~5/10
Subscription lifecycle — stories about subscription lifecycle in this arenaSubscription lifecycle
Stories about subscription lifecycle in this arena
Create, update, pause, and cancel subscriptions through a documented API — the full lifecycle without touching a dashboard
✓7/10
Every subscription state change — renewal, upgrade, payment failure, cancellation — emits a webhook or event my systems can act on reliably
~7/10
My customers can upgrade, downgrade, or cancel themselves through a hosted portal or embeddable components, without a support ticket
✓8/10
Run free trials, coupons, and promotion codes with automatic conversion to paid — including trial-end notifications required by card-network rules
~4/10
Usage metering — stories about usage metering in this arenaUsage metering
Stories about usage metering in this arena
Stream high-volume usage events — API calls, tokens, compute-seconds — into a metering pipeline with idempotent ingestion and backdating support
~2/10
Price with tiered, volume, graduated, per-unit, and hybrid subscription-plus-usage models — including credits, commitments, and overage — without custom code
~5/10
Customers and my team can see current-cycle usage and accrued cost in real time, with thresholds and alerts before an invoice surprises anyone
—0/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 | 9/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 | 8/10 | Tprobed | |
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 | 0/10 | ||
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 | none | 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 | 9/10 | Tprobed | |
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 | |
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 | full | 7/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 | Cclaimed | |
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 | |
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 | 6/10 | Tprobed | |
Build against official SDKs G Agent access | 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 | ||
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 | none | 0/10 | ||
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 | 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 | 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 | none | 0/10 | ||
Create, update, pause, and cancel subscriptions through a documented API — the full lifecycle without touching a dashboard C Lifecycle api | developer | Subscription lifecycle — stories about subscription lifecycle in this arenaSubscription lifecycle | 3 | full | 7/10 | Tprobed | |
An agent can operate my billing — create a subscription, apply a credit, change a plan — through a programmatic surface with scoped permissions G Agent operations | ai-native user | Billing agent access — stories about billing agent access in this arenaBilling agent access | 3 | partial | 6/10 | Tprobed | |
Failed renewal payments are retried automatically on an ML- or schedule-optimized cadence that measurably recovers involuntary churn C Smart retries | finance lead | Dunning recovery — stories about dunning recovery in this arenaDunning recovery | 3 | partial | 6/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 | partial | 5/10 | Cclaimed | |
Features and limits are modeled as entitlements attached to plans, and my application can check a customer's entitlements at runtime via API or SDK C Entitlement checks | developer | Entitlements — stories about entitlements in this arenaEntitlements | 3 | partial | 5/10 | Cclaimed | |
Mid-cycle upgrades and downgrades are prorated with documented, auditable math — credits, partial periods, and invoice line items that reconcile to the penny C Proration | finance lead | Billing math — stories about billing math in this arenaBilling math | 3 | partial | 5/10 | Cclaimed | |
Migrate live subscriptions in from a spreadsheet or a competing platform — including PCI-compliant card data transfer — without customers noticing C Import | ops user | Migration portability — stories about migration portability in this arenaMigration portability | 3 | partial | 5/10 | Cclaimed | |
Price with tiered, volume, graduated, per-unit, and hybrid subscription-plus-usage models — including credits, commitments, and overage — without custom code G Pricing models | finance lead | Usage metering — stories about usage metering in this arenaUsage metering | 3 | partial | 5/10 | Xcommunity | |
Revenue is recognized on an ASC 606 / IFRS 15 basis — deferred revenue schedules and audit-ready recognition reports straight from billing data G Revrec reports | finance lead | Revenue recognition — stories about revenue recognition in this arenaRevenue recognition | 3 | partial | 5/10 | Cclaimed | |
Stream high-volume usage events — API calls, tokens, compute-seconds — into a metering pipeline with idempotent ingestion and backdating support C Event ingestion | developer | Usage metering — stories about usage metering in this arenaUsage metering | 3 | partial | 2/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 | none | 0/10 | ||
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 | none | untested | none yet | |
My customers can upgrade, downgrade, or cancel themselves through a hosted portal or embeddable components, without a support ticket C Self serve | founder | Subscription lifecycle — stories about subscription lifecycle in this arenaSubscription lifecycle | 2 | full | 8/10 | Xcommunity | |
Every subscription state change — renewal, upgrade, payment failure, cancellation — emits a webhook or event my systems can act on reliably C Lifecycle events | developer | Subscription lifecycle — stories about subscription lifecycle in this arenaSubscription lifecycle | 2 | partial | 7/10 | Cclaimed | |
Sales tax, VAT, and GST are calculated on every invoice — natively or through a first-class tax integration — with the right registrations and rates C Tax | finance lead | Invoicing tax — stories about invoicing tax in this arenaInvoicing tax | 2 | full | 7/10 | Cclaimed | |
An agent can answer questions about my billing state — MRR, delinquent accounts, upcoming renewals, a customer's invoices — by querying the platform directly G Agent queries | ai-native user | Billing agent access — stories about billing agent access in this arenaBilling agent access | 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 | Xcommunity | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 6/10 | Tprobed | |
Bill customers in their local currency with per-currency price points and consolidated reporting in my home currency G Multi currency | finance lead | Invoicing tax — stories about invoicing tax in this arenaInvoicing tax | 2 | partial | 5/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 | partial | 5/10 | Tprobed | |
Change pricing without breaking existing subscribers — versioned plans, grandfathering, and bulk migration tools for moving cohorts to new prices G Plan versioning | ops user | Entitlements — stories about entitlements in this arenaEntitlements | 2 | partial | 4/10 | Cclaimed | |
Configure automated dunning sequences — branded emails, in-app banners, grace periods, and final-state rules like cancel vs unpaid C Dunning comms | ops user | Dunning recovery — stories about dunning recovery in this arenaDunning recovery | 2 | partial | 4/10 | Cclaimed | |
Expiring or replaced cards update themselves — network account updater, backup payment methods, and hosted update-payment pages C Card recovery | ops user | Dunning recovery — stories about dunning recovery in this arenaDunning recovery | 2 | partial | 4/10 | Cclaimed | |
I get MRR, churn, cohort retention, and LTV analytics computed from the billing source of truth, not a bolted-on BI export G Analytics | founder | Revenue recognition — stories about revenue recognition in this arenaRevenue recognition | 2 | disputed | 4/10 | Dcontradicted | |
Run free trials, coupons, and promotion codes with automatic conversion to paid — including trial-end notifications required by card-network rules C Trials promos | ops user | Subscription lifecycle — stories about subscription lifecycle in this arenaSubscription lifecycle | 2 | partial | 4/10 | Xcommunity | |
The platform generates compliant invoices, credit notes, and receipts — sequential numbering, custom fields, memos — delivered to customers automatically C Invoices | ops user | Invoicing tax — stories about invoicing tax in this arenaInvoicing tax | 2 | partial | 4/10 | Xcommunity | |
Customers and my team can see current-cycle usage and accrued cost in real time, with thresholds and alerts before an invoice surprises anyone C Usage visibility | ops user | Usage metering — stories about usage metering in this arenaUsage metering | 2 | none | 0/10 | ||
Export every subscription, invoice, and usage record — and port stored payment methods out to another provider — if I choose to leave G Export | finance lead | Migration portability — stories about migration portability in this arenaMigration portability | 2 | none | 0/10 | ||
Invoices, payments, and recognition entries sync to my general ledger or ERP — QuickBooks, Xero, NetSuite — so the close doesn't need CSV surgery C Gl sync | finance lead | Revenue recognition — stories about revenue recognition in this arenaRevenue recognition | 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 billing anchors and cycles — calendar vs anniversary billing, alignment across a customer's subscriptions, custom invoice dates G Billing cycles | ops user | Billing math — stories about billing math in this arenaBilling math | 2 | none | 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 | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 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 | |
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 40 stories with headroom
What would move Stripe Billing’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 productDelegate tasks to a built-in AI assistant inside the product
nonemoves Built-in AIimpact 45
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".
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
Evidence covers importing/migrating data INTO Stripe Billing (from Zuora, Recurly, etc.) but nothing about exporting a merchant's own subscription/invoice/customer data out in open formats to leave the platform.
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
nonemoves PA Scoreimpact 30
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".
Agenticness — how well agents can access and operate the productGet AI-generated insights and suggestions from my data inside the product
nonemoves Built-in AIimpact 30
Missing: any AI/ML-generated insights or recommendation features, in-product analysis narratives, or evidence of generative AI surfacing suggestions from billing/subscription data.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
Missing: documentation of restricted/scoped API key creation, permission granularity controls, and any agent-specific credential-scoping workflow.
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 no mention of an interactive API reference with runnable/executable code examples for Stripe Billing; it only covers docs, CLI, MCP server, and general billing features.
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 an explicit probe for OpenAPI/Swagger spec files at all standard paths returning 404, and no docs or community item mentions a downloadable OpenAPI/equivalent spec for Stripe Billing's API; only llms.txt and markdown docs endpoints are confirmed, which are not API specs.
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 headers, changelog/versioning policy, or deprecation timelines.
Showing the top 8 of 40 — 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 map12 surfaces · 33 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Billing docs24 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
- Set up automations that run autonomously in the background
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Schedule recurring jobs or workflows
- An agent can operate my billing — create a subscription, apply a credit, change a plan — through a programmatic surface with scoped permissions
- An agent can answer questions about my billing state — MRR, delinquent accounts, upcoming renewals, a customer's invoices — by querying the platform directly
- Mid-cycle upgrades and downgrades are prorated with documented, auditable math — credits, partial periods, and invoice line items that reconcile to the penny
- Expiring or replaced cards update themselves — network account updater, backup payment methods, and hosted update-payment pages
- Configure automated dunning sequences — branded emails, in-app banners, grace periods, and final-state rules like cancel vs unpaid
- Failed renewal payments are retried automatically on an ML- or schedule-optimized cadence that measurably recovers involuntary churn
- Features and limits are modeled as entitlements attached to plans, and my application can check a customer's entitlements at runtime via API or SDK
- Change pricing without breaking existing subscribers — versioned plans, grandfathering, and bulk migration tools for moving cohorts to new prices
- Bill customers in their local currency with per-currency price points and consolidated reporting in my home currency
- Migrate live subscriptions in from a spreadsheet or a competing platform — including PCI-compliant card data transfer — without customers noticing
- Do everything through the API that I can do in the UI
- I get MRR, churn, cohort retention, and LTV analytics computed from the billing source of truth, not a bolted-on BI export
- Create, update, pause, and cancel subscriptions through a documented API — the full lifecycle without touching a dashboard
- Every subscription state change — renewal, upgrade, payment failure, cancellation — emits a webhook or event my systems can act on reliably
- Run free trials, coupons, and promotion codes with automatic conversion to paid — including trial-end notifications required by card-network rules
- Stream high-volume usage events — API calls, tokens, compute-seconds — into a metering pipeline with idempotent ingestion and backdating support
- Price with tiered, volume, graduated, per-unit, and hybrid subscription-plus-usage models — including credits, commitments, and overage — without custom code
MCP docs10 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
- Perform bulk operations across many items at once
- Schedule recurring jobs or workflows
- An agent can operate my billing — create a subscription, apply a credit, change a plan — through a programmatic surface with scoped permissions
- An agent can answer questions about my billing state — MRR, delinquent accounts, upcoming renewals, a customer's invoices — by querying the platform directly
- Do everything through the API that I can do in the UI
Stripe CLI docs8 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
- Perform bulk operations across many items at once
- Schedule recurring jobs or workflows
- Do everything through the API that I can do in the UI
- Create, update, pause, and cancel subscriptions through a documented API — the full lifecycle without touching a dashboard
Hacker News7 stories
- The platform generates compliant invoices, credit notes, and receipts — sequential numbering, custom fields, memos — delivered to customers automatically
- Bill customers in their local currency with per-currency price points and consolidated reporting in my home currency
- Do everything through the API that I can do in the UI
- I get MRR, churn, cohort retention, and LTV analytics computed from the billing source of truth, not a bolted-on BI export
- My customers can upgrade, downgrade, or cancel themselves through a hosted portal or embeddable components, without a support ticket
- Run free trials, coupons, and promotion codes with automatic conversion to paid — including trial-end notifications required by card-network rules
- Price with tiered, volume, graduated, per-unit, and hybrid subscription-plus-usage models — including credits, commitments, and overage — without custom code
Webhooks docs6 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Subscribe to events via webhooks
- Set up automations that run autonomously in the background
- Define rules that trigger actions automatically on events
- Every subscription state change — renewal, upgrade, payment failure, cancellation — emits a webhook or event my systems can act on reliably
Invoicing docs4 stories
- An agent can answer questions about my billing state — MRR, delinquent accounts, upcoming renewals, a customer's invoices — by querying the platform directly
- Mid-cycle upgrades and downgrades are prorated with documented, auditable math — credits, partial periods, and invoice line items that reconcile to the penny
- The platform generates compliant invoices, credit notes, and receipts — sequential numbering, custom fields, memos — delivered to customers automatically
- Sales tax, VAT, and GST are calculated on every invoice — natively or through a first-class tax integration — with the right registrations and rates
Customer management docs3 stories
- Expiring or replaced cards update themselves — network account updater, backup payment methods, and hosted update-payment pages
- Do everything through the API that I can do in the UI
- My customers can upgrade, downgrade, or cancel themselves through a hosted portal or embeddable components, without a support ticket
Get started docs1 story
Revenue recognition docs1 story
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/subscriptions | head -4 # the subscription-lifecycle API, keyless → 401reproduced$ curl -si https://api.stripe.com/v1/subscriptions | head -4 # the subscription-lifecycle API, [redacted]less → 401 HTTP/2 401 server: nginx date: Mon, 14 Sep 2026 23:33:04 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
$curl -s https://raw.githubusercontent.com/stripe/openapi/master/openapi/spec3.json | head -c 200reproduced$ curl -s https://raw.githubusercontent.com/stripe/openapi/master/openapi/spec3.json | head -c 200
{
"components": {
"schemas": {
"account": {
"description": "For new integrations, we recommend using the [Accounts v2 API](/api/v2/core/accounts), in place of /v1/accounts and /v1/
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
7 of 16 testable claims verified · 1 contradicted → integrity 31/100
17 distinct capability claims found in Stripe Billing’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
7
Verified
8
Unverified
1
Contradicted
17
Undersold
Verified (8)
“Automates recurring subscription billing, custom pricing plans, and billing periods like trials and renewals”
Create, update, pause, and cancel subscriptions through a documented API — the full lifecycle without touching a dashboardfullproof ↗
“Create subscriptions via the Dashboard or the Subscriptions API”
Create, update, pause, and cancel subscriptions through a documented API — the full lifecycle without touching a dashboardfullproof ↗
“Set up usage-based pricing models for SaaS products”
Price with tiered, volume, graduated, per-unit, and hybrid subscription-plus-usage models — including credits, commitments, and overage — without custom codepartialproof ↗
“Create, customize, and send hosted invoices from the Dashboard with no code”
The platform generates compliant invoices, credit notes, and receipts — sequential numbering, custom fields, memos — delivered to customers automaticallypartialproof ↗
“Customer portal lets customers self-manage their billing account”
My customers can upgrade, downgrade, or cancel themselves through a hosted portal or embeddable components, without a support ticketfullproof ↗
“Trial Offer API manages both free and paid introductory subscription periods”
Run free trials, coupons, and promotion codes with automatic conversion to paid — including trial-end notifications required by card-network rulespartialproof ↗
“Official MCP server lets AI agents interact with the Stripe API”
“Official CLI to build, test, and manage a Stripe integration from the command line”
Unverified (9)
“Preview proration amounts before applying subscription changes”
Mid-cycle upgrades and downgrades are prorated with documented, auditable math — credits, partial periods, and invoice line items that reconcile to the pennypartialproof ↗
“Automatically retries failed subscription/invoice payments to reduce involuntary churn”
Failed renewal payments are retried automatically on an ML- or schedule-optimized cadence that measurably recovers involuntary churnpartialproof ↗
“Automated support for global accounting standards to simplify revenue recognition”
Revenue is recognized on an ASC 606 / IFRS 15 basis — deferred revenue schedules and audit-ready recognition reports straight from billing datapartialproof ↗
“Grant or revoke customer access to product features based on plan”
Features and limits are modeled as entitlements attached to plans, and my application can check a customer's entitlements at runtime via API or SDKpartialproof ↗
“Import existing subscriptions from third-party billing systems like Zuora, Recurly, Chargify, or Chargebee”
Migrate live subscriptions in from a spreadsheet or a competing platform — including PCI-compliant card data transfer — without customers noticingpartialproof ↗
“Automates sales tax, VAT, and GST compliance across transactions”
Sales tax, VAT, and GST are calculated on every invoice — natively or through a first-class tax integration — with the right registrations and ratesfullproof ↗
“Pushes real-time event data (webhooks) when account events occur”
“Pushes real-time event data (webhooks) when account events occur”
Every subscription state change — renewal, upgrade, payment failure, cancellation — emits a webhook or event my systems can act on reliablypartialproof ↗
“Provides a guided multi-step process to migrate customer and payments data into Stripe”
Migrate live subscriptions in from a spreadsheet or a competing platform — including PCI-compliant card data transfer — without customers noticingpartialproof ↗
Contradicted (1)
“Dashboard view to monitor overall billing performance at a glance”
I get MRR, churn, cohort retention, and LTV analytics computed from the billing source of truth, not a bolted-on BI exportdisputedproof ↗
Undersold (17)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationfullproof ↗
Drive the product through a documented public APIfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
An agent can operate my billing — create a subscription, apply a credit, change a plan — through a programmatic surface with scoped permissionspartialproof ↗
An agent can answer questions about my billing state — MRR, delinquent accounts, upcoming renewals, a customer's invoices — by querying the platform directlypartialproof ↗
Expiring or replaced cards update themselves — network account updater, backup payment methods, and hosted update-payment pagespartialproof ↗
Configure automated dunning sequences — branded emails, in-app banners, grace periods, and final-state rules like cancel vs unpaidpartialproof ↗
Change pricing without breaking existing subscribers — versioned plans, grandfathering, and bulk migration tools for moving cohorts to new pricespartialproof ↗
Bill customers in their local currency with per-currency price points and consolidated reporting in my home currencypartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Stream high-volume usage events — API calls, tokens, compute-seconds — into a metering pipeline with idempotent ingestion and backdating supportpartialproof ↗
Business model
Pay-as-you-go 0.7% of Billing volume with no recurring fee; annual pay-monthly tiers from $620/mo (up to $100K volume) to $5,750/mo (up to $1M), then custom. Payment processing fees separate.
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
