Stripe.Directory

Product Introduction

1. Definition: Stripe.Directory is a specialized developer discovery platform and API directory integrated within the Stripe ecosystem. It functions as a structured search layer for identifying businesses, services, and tools available on the Stripe network, including Stripe Apps, Stripe Projects providers, and Machine Payments Protocol (MPP) services.
2. Core Value Proposition: It eliminates manual vendor discovery and integration overhead by providing developers and AI agents with a single, queryable interface to find, evaluate, and programmatically integrate partner services directly from the command line or via agent workflows. Its core value is accelerating the "search-to-integration" pipeline within the fintech stack.

Main Features

1. Universal Service Indexing: The directory indexes four distinct categories of Stripe ecosystem participants: Stripe Apps (Dashboard extensions), Stripe Projects providers (CLI-provisionable services), machine payments endpoints (pay-per-call APIs on mpp.dev), and businesses across the broader Stripe network. This creates a comprehensive catalog of actionable services.
2. Structured Search & CLI Integration: Developers execute queries like stripe directory search "web browsing api" via the Stripe CLI. The output is structured data (displayable in --format compact or --format json) containing provider slugs, App Store links, Projects catalog commands, and MPP endpoints, enabling immediate next-step actions.
3. AI Agent Enablement & Skill Integration: The product is built for agentic workflows. It provides structured JSON output (--format json) for machine parsing and offers a dedicated agent skill (npx skills add ... --skill stripe-directory). This allows AI agents to autonomously search, evaluate options against requirements, and initiate integrations using returned endpoints.
4. Direct Integration Pathways: Results include ready-to-use commands. For Stripe Projects providers, it outputs stripe projects catalog <slug> and stripe projects add <slug>. For MPP services, it provides the endpoint URL for immediate payment and consumption via mppx fetch <endpoint>, completing the integration loop within the terminal.

Problems Solved

1. Pain Point: Manual Vendor Discovery and Integration Fatigue. Developers building applications often spend excessive time researching third-party services (like databases or mailing APIs), verifying compatibility with Stripe, and writing boilerplate code for integration. This process is fragmented across documentation sites, marketplaces, and manual API configuration.
2. Target Audience: Full-stack Developers building SaaS products, AI Agent Architects creating autonomous systems, DevOps Engineers provisioning infrastructure, and Technical Founders rapidly prototyping applications that require Stripe-integrated services.
3. Use Cases:
   • Rapid Stack Assembly: A developer needs a serverless Postgres database. They run stripe directory search "serverless postgres", identify Neon from the results, and execute stripe projects add neon to provision it, all without leaving the terminal.
   • Autonomous Agent Integration: An AI agent tasked with "send a physical letter" is configured with the Stripe Directory skill. It searches "send mail", identifies PostalForm as an MPP-supported service, and uses mppx fetch to execute the payment and API call, completing the task end-to-end.
   • Ecosystem Partner Visibility: A startup offering an API service lists their MPP endpoint on Stripe, making their service directly discoverable and payable via Stripe's agentic infrastructure.

Unique Advantages

1. Differentiation: Unlike generic API directories (e.g., RapidAPI) or static documentation, Stripe.Directory is deeply embedded in the Stripe operational layer. It doesn't just list services; it provides the exact CLI commands and payment endpoints (mppx) needed to provision and pay for them, creating a closed-loop, "search-to-operation" experience. It bridges discovery with execution.
2. Key Innovation: The primary innovation is the unified integration of discovery with the Stripe Machine Payments Protocol (MPP). By indexing MPP endpoints and providing mppx commands directly in search results, it enables a new paradigm of "agentic commerce" where AI agents can autonomously transact with and consume API services, using Stripe as the settlement and orchestration layer.

Frequently Asked Questions (FAQ)

1. What is the Stripe Directory CLI command to find a service? The primary command is stripe directory search followed by your keywords in quotes. Use flags like --format json for structured output or --mpp-supported to filter for machine-payable services.
2. How does Stripe Directory differ from the Stripe App Marketplace? The Stripe App Marketplace is a consumer-facing store for Dashboard extensions. Stripe Directory is a developer and agent tool that indexes the entire ecosystem—including Apps, Projects providers, and MPP services—and provides structured data and integration commands via the CLI, targeting programmatic access over manual browsing.
3. Can I make my business visible in Stripe Directory search results? Yes, you can list your company in Stripe Directory by setting up a public Stripe Profile, ensuring your profile is not private, optimizing your description with relevant keywords, and allowing Stripe's crawler to index your website.
4. How do AI agents use Stripe Directory for autonomous integration? AI agents use the stripe-directory agent skill or direct CLI calls with --format json. They parse the structured results (including MPP endpoints and Projects commands) to compare services and execute the provided integration and payment commands without human intervention.
5. What are "machine payments endpoints" listed in Stripe Directory results? These are services on the Machine Payments Protocol (MPP) network (e.g., at mpp.dev) that expose APIs payable per call. Stripe Directory lists their endpoints, allowing you or your agent to use mppx fetch <endpoint> to review pricing and execute payment-integrated API calls.