Stripe Directory turns payment infrastructure into an agent economy

Stripe launched a public preview of Stripe Directory this week, a searchable index of businesses on the Stripe network. The product is a directory, but the design is not for humans alone. Every result returns structured data a CLI tool or an AI agent can parse. That design choice, more than the feature itself, signals where Stripe is placing its bet.

Stripe Directory indexes four categories: Stripe Apps from the App Marketplace, Stripe Projects providers, Machine Payments Protocol (MPP) endpoints on mpp.dev, and the broader Stripe business network. A developer or agent can search by keyword, filter by capability, and get back a structured table with provider slugs, MPP endpoints, and app listings. The output format defaults to a compact table, but the --format json flag returns machine-readable results. An agent can parse those results, compare options, and use the returned endpoint to integrate automatically.

The directory is not a passive listing. It is a discovery layer for an increasingly automated payments stack. Stripe Projects lets developers provision services with a stripe projects add command. MPP endpoints let agents pay per API call with mppx fetch. Stripe Directory connects those two worlds: find a service, inspect its catalog, provision it, pay for it. All from a terminal.

Stripe’s documentation makes the agent use case explicit. “Stripe Directory lets AI agents discover, evaluate, and integrate services autonomously,” the docs state. An agent can search for “serverless postgres database,” parse the JSON output, and run stripe projects add neon to provision Neon’s database service. No human clicks a button. No API key exchange. The payment rail is already connected.

The directory currently lists a small set of providers. Browserbase, You.com, Exa, Firecrawl appear in the sample search for “web browsing api.” Neon is the example for serverless postgres. PostalForm, a service that sends physical mail via API, appears for “send mail” with MPP support. These are early partners, but the pattern is clear. Stripe is building the plumbing for a machine-to-machine economy where agents discover, negotiate, and pay for services without human intervention.

This is not a new idea. The concept of an automated marketplace for services has been tried before, from early API marketplaces to blockchain-based service directories. What is different here is the payment infrastructure. Stripe already processes payments for millions of businesses. The directory layers discovery on top of that existing rail. An agent that finds a service through the directory does not need to set up a new payment method. The Stripe account is already connected.

The timing aligns with the broader agent ecosystem. Multiple frontier labs have released agent frameworks in the past year. OpenAI’s Agents SDK, Anthropic’s tool-use API, and various open-source agent frameworks all rely on the same pattern: an LLM calls external APIs to accomplish tasks. The bottleneck has not been the LLM. It has been the integration layer. Every API requires authentication, billing, and error handling. Stripe Directory collapses those steps into a single search-and-provision flow.

Stripe’s own Machine Payments Protocol, launched earlier this year, is the payment rail for this new economy. MPP lets developers charge per API call, with Stripe handling settlement. The directory surfaces MPP endpoints alongside traditional payment links. A search result for PostalForm includes both a Stripe App link and an MPP endpoint. The agent can choose the payment method that fits its workflow.

The directory also includes a skills installation path for agents. Stripe provides a global agent skill that can be installed with npx skills add https://docs.stripe.com --skill stripe-directory -g -y. After installation, an agent can search the directory, interpret results, and use returned endpoints without additional instruction. This is Stripe embedding itself into the agent’s tool-use loop, not just providing an API.

For businesses listed in the directory, the incentive is clear. Stripe’s search uses website content to match businesses to relevant searches. A business that describes itself in plain language, with the phrases customers actually type, will appear in more searches. Stripe advises businesses to “describe what you do in plain language, the words your customers would actually type.” This is SEO for the agent economy.

The public preview is opt-in. Stripe users appear in search results only if they enable a public profile. Businesses can also remove themselves by setting their profile to private. The directory is not a default listing. It is a deliberate choice to be discoverable by automated systems.

The most significant implication is for the business model of API providers. Services like Neon and Browserbase already charge for API usage. Stripe Directory adds a discovery channel that feeds directly into their billing systems. An agent that discovers Neon through the directory and provisions it through Stripe Projects generates revenue for both Neon and Stripe. Stripe takes a cut of the payment, Neon gets a customer with zero acquisition cost.

This is the infrastructure for a world where AI agents are the customers. Not human developers browsing documentation, but automated systems that evaluate, select, and pay for services. The directory is the storefront. Stripe Projects is the provisioning layer. MPP is the payment rail. Together they form a complete loop for machine commerce.

The open question is adoption. Stripe Directory works only for businesses already on Stripe with public profiles. The index is limited to what Stripe can crawl and categorize. The current partner list is small. But the infrastructure is designed to scale. Any business on Stripe can opt in. Any agent with the Stripe CLI plugin can search. The network effects are built in.

Stripe Directory is not a product announcement. It is a bet on a future where payments are not a human action but a machine protocol.