API Evangelist API Evangelist
API Learnings
Toolbox
API Evangelist LLC

I have been reviewing API providers for the better part of fifteen years, and Stripe has been on every short list of provider operations I have pointed at as the bar. I have not actually sat down and walked their developer area end-to-end in a while — homepage to docs to GitHub to pricing — and I wanted to do that fresh, the way a developer arriving at stripe.com for the first time in 2026 would. This is what I found. Not a profile of what I have collected about Stripe — a review of what Stripe actually publishes. The Pitch The homepage lede sets the frame for everything that follows: “Financial infrastructure to grow your revenue. Accept payments, offer financial services, and implement custom revenue models—from your first transaction to your billionth.” The top nav is the cleanest API-company nav I see in the field — six items, the developers entry sits as a first-class peer of Products, Solutions, and Pricing. Most providers bury developers two levels deep. Stripe doesn’t. The scale numbers they put on the page are not shy: $1.9T in payments volume processed in 2025 500M+ API requests per day, 10K+ requests per second, 150K+ transactions per minute 200M+ active subscriptions on Stripe Billing 99.999% historical uptime — they cite 99.9999% during Black Friday/Cyber Monday 2025 processing over $40B 135+ currencies and payment methods 50% of the Fortune 100 and 78% of the Forbes AI 50 on the platform You can disagree with any single number but the pattern is unmistakable: Stripe is comfortable putting operational metrics on the homepage that most providers wouldn’t dare quote, because they are confident the metrics hold up. The Docs docs.stripe.com opens with the most minimal headline I have seen on a major provider’s docs landing page: “Documentation — Explore our guides and examples to integrate Stripe.” That’s it. No marketing chest-thumping. The body is then organized around three lanes — Getting Started Use Cases (Accept payments online, Sell subscriptions, In-person payments, Usage-based pricing, Customer Portal), Developer Setup & Resources (Set up your development environment, Build on Stripe with AI, Integration quickstarts), and Browse by Product (the full taxonomy — Payments, Revenue, Money Management, Prebuilt Components). What is missing from the landing page, and worth naming: a one-click changelog, a one-click status page, a one-click SDK list, a one-click support link. Those things exist on Stripe — but they live in nav and footer chrome, not on the docs index itself. A first-time arrival has to know to look for them. Stripe’s information density is high, but discovery for the things that aren’t a use case is a layer down. The “Build on Stripe with AI” entry is new since I last walked through here. It signals that Stripe sees the agent as a developer archetype now, not a future one. The API Reference docs.stripe.com/api is still the API reference everyone else gets compared to. The opening framing is exactly what you would hope a payment API would lead with:…