Stripe
Financial infrastructure for the internet
4.9•450 reviews•8.3K followers
Financial infrastructure for the internet
4.9•450 reviews•8.3K followers
Accept payments, send payouts, automate financial processes, and ultimately grow revenue.
This is the 72nd launch from Stripe. View more
Stripe.Directory
Launched this week
Stripe Directory is a single discovery layer for developers and AI agents to find businesses on Stripe—including Stripe Apps, Projects.dev providers, and mpp.dev services—and integrate them without the need to manually search for them.
Free Options
Launch Team
The MPP angle makes sense - agentic commerce needs a directory layer to work. But I'm skeptical about the chicken-and-egg problem here: the directory's value depends on how many quality services are indexed, and MPP is still very early. Is this pulling exclusively from Stripe Apps + MPP-registered services, or is there a broader listing process? Also curious how it handles the majority of Stripe-integrated tools that exist but haven't opted into MPP yet - those are often the most useful ones an agent would actually need.
The "agents discover, evaluate AND integrate autonomously" part is what makes this interesting and a little scary at once. Once an agent can act on a listing without a human in the loop, the directory becomes a trust gateway: what stops a malicious or typosquatting service from getting indexed and an agent integrating or paying it before anyone notices? Is there a verification layer on who gets listed, or is the index open and trust is left to the agent?
Stripe Directory — the single place to discover businesses and services across the Stripe network.
Developers and AI agents struggle to find and integrate Stripe services (apps, projects, machine payments APIs). Stripe Directory solves this by letting you search by keyword and get structured, actionable results you or your agent can use.
What’s Different: It’s the only Stripe index combining Stripe Apps, Stripe Projects providers, Machine Payments endpoints, and the broader Stripe business network—all searchable with structured output for agents.
Features:
- CLI-powered search (`stripe directory search`) with compact or JSON output
- Structured results with provider slugs, MPP endpoints, and app listings
- Built-in agent skills to let AI agents discover, evaluate, and integrate services autonomously
Benefits: Instant discovery, faster integration, and autonomous agent workflows without extra instruction.
Who It’s For & Use Cases: Developers building Stripe-integrated apps (e.g., finding a database provider like Neon and integrating in one flow) and AI agents that need to pay for services (e.g., PostalForm for sending mail via machine payments).
P.S. I hunt the latest and greatest launches in tech, SaaS and AI, follow to be notified → @rohanrecommends
Useful angle for agent-facing search. I would make three result fields very explicit: source freshness, whether the next step is read-only or money-moving, and the exact provider slug the agent should quote back before acting. That last confirmation step prevents "found a similar provider" mistakes.
Been shipping on Stripe for a while and the thing that keeps me here is the documentation — it's good enough that you can go from nothing to a working checkout + webhook flow in an afternoon. The sandbox mode is the unsung hero too: being able to simulate failed payments and edge cases before going live has caught a lot of bugs that would've been embarrassing in production.
Fair criticism: the product surface has gotten big (Payments, Billing, Connect, Checkout, Elements, Tax, Radar…) and picking the right combination for a simple recurring-payments use case is harder than it should be. But once it's wired up, it stays out of your way — which is exactly what you want from payments infra.
I can see this being useful for reducing integration friction. Finding services is rarely the hard part, but understanding whether they fit a workflow usually is. How are quality and trust signals surfaced inside the directory?