Patrick Collison's announcement tweet was characteristically understated: "Very early experiment but I think this will be cool."
He linked to stripe.directory. The tech community moved on quickly. Most people filed it under "Stripe doing Stripe things."
That was the wrong read.
Stripe Directory is not a business listing. It is a discovery and payment primitive — specifically built for a world where AI agents need to find services and transact with them autonomously, without a human authorizing each payment or clicking through a checkout form designed for browsers.
What Broke Before Stripe Directory Existed
The current model for AI agents that need to accomplish tasks involving third-party services is kludged together:
Discovery: The agent searches the web, scrapes documentation, or relies on hard-coded integrations. None of this is reliable at scale. Sites change. APIs require authentication that agents don't have. Structured service discovery doesn't exist as a standard.
Understanding: Even when an agent finds a service, understanding what it offers in machine-readable form requires either a well-documented API or parsing unstructured marketing text. There's no standard for "here is what my service does and what it costs" in a form agents can reason about.
Payment: This is the wall. An agent that needs to pay for something hits checkout flows designed for humans — forms, captchas, 2FA, credit card fields. The workarounds (stored tokens, API billing by proxy) are fragile and require pre-setup by the user.
Stripe Directory addresses all three in a single system.
The Three Components
1. Business Profiles
Businesses create free profiles at dashboard.stripe.com/profiles. Each profile includes:
- Website
- Stripe Apps support status
- Machine Payments endpoint (if configured)
The profile is what makes a business discoverable in the directory. Getting a handle early is the first action most businesses should take.
2. Search
Discovery works via web (stripe.directory) or CLI:
stripe directory search "data enrichment"
Results come back as structured data — not HTML to parse, not a page to scrape. The agent gets a list of businesses, their metadata, and their Machine Payments endpoints directly.
3. Machine Payments Endpoints
This is the load-bearing innovation.
A Machine Payments endpoint is a structured API spec that tells an agent exactly how to initiate a payment to a specific business. It's analogous to OAuth in the sense that it's a standardized handshake — but for payments, not authentication.
When an agent finds a business via directory search, it can check whether that business has a Machine Payments endpoint. If yes, the agent can transact without:
- Loading a checkout page
- Filling in form fields
- Solving a captcha
- Waiting for human approval
The payment flows through the Stripe network, and critically — payments between connected Stripe accounts are free. That removes the per-transaction cost friction that makes micro-transactions economically unworkable.
Why Free Inter-Network Payments Change the Math
Agent commerce has an economics problem: the tasks agents complete often involve small transactions. An agent that books a $3 API credit, requests a $2 data enrichment, or schedules a $5 processing job through a service with 2.9% + $0.30 standard Stripe fees loses money on the transaction.
At $3, standard processing takes ~$0.39. That's a 13% fee on a micro-transaction. At $0.50, it becomes prohibitive.
By making intra-network payments free, Stripe collapses this friction. Agents can complete micro-transactions for cents-level services without the economics requiring minimum purchase thresholds or bundled billing.
The business model implication: Stripe captures value when transactions leave the network (external payments at standard rates) while making internal commerce free to drive adoption. Every business that creates a Directory profile and configures Machine Payments is deeper in the Stripe ecosystem.
Jeff Weinstein's Three Signals
Stripe's product lead Jeff Weinstein was more explicit in his announcement than Collison:
"get listed in the Directory so other businesses, and agents, can find your products and services. Payments are free between businesses over Stripe. More things soon."
Three signals from that statement:
"And agents" is the operative phrase. This is not a business-to-business listing optimized for human sales discovery. Agents are first-class participants.
"Payments are free between businesses" is the economic unlock, not just a feature. It's a structural change that makes the directory useful for use cases where standard payment fees would kill the economics.
"More things soon" suggests the directory is infrastructure for something larger — likely a richer capability schema standard, authentication delegation, or deeper agent orchestration features. What's live today is version one of something Stripe sees as a bigger platform.
The Gap That Remains
No capability schema. Directory profiles tell you a business's website and whether they have a Machine Payments endpoint. There's no structured way to express "this API returns B2B contact data" or "this service analyzes uploaded PDFs and returns summaries." For agents to discover services by capability — not just by keyword — a richer metadata standard is needed. Stripe hasn't announced one.
No authentication delegation. Machine Payments handles the payment. It doesn't handle the authorization an agent needs to access a user's data at a third-party service — that's still OAuth or API keys, separately managed. A complete agent-to-service handshake needs both.
Early inventory. The directory is only as valuable as the businesses listed in it. Right now it's a very early experiment. The practical value for agent builders depends on whether the services they want to integrate with create profiles and configure Machine Payments endpoints.
What the Pattern Tells Us
Stripe won the SaaS payments era by being the infrastructure developers actually reached for. They didn't win by having the best payment processing technology in isolation — they won by making payment integration the easiest thing to do, so every new SaaS company just used Stripe by default.
The Directory move is the same pattern applied to agentic commerce. The question for agents navigating a service-rich web is: how do I find what I need, understand what it costs, and pay for it? Stripe is trying to be the answer to all three by controlling the directory and the payment rail simultaneously.
Who benefits from creating a profile right now:
| Business Type | Why Register | Priority |
|---|---|---|
| API data providers (enrichment, verification, lookup) | High agent demand for data; Machine Payments makes per-call billing work | High |
| SaaS with API billing | Get discovered as agent-accessible services | High |
| Professional service firms | Low urgency; agents rarely buy human services | Low |
| Enterprise software | Usually pre-integrated via sales cycles | Low |
If you sell API access, data, or compute services — and you're already on Stripe — creating a profile and configuring a Machine Payments endpoint is a meaningful early-mover decision.
The Practical Step Right Now
- Go to
dashboard.stripe.com/profiles - Claim your business handle
- Fill in your profile
- Configure a Machine Payments endpoint if you offer API services
The directory is early. The inventory is thin. But the businesses that get listed now will be indexed by agents when agent-initiated discovery becomes a real acquisition channel.
Collison said "very early experiment." The implication is: the experiment will keep going.
Related
- AI agents directory — autonomous agents that can discover and use services
- AI tools directory — full landscape of AI tooling and APIs
- MCP servers — model context protocol integrations for agents