stripe-directory

SKILL.md

Stripe Directory Search

Turn a vague market need into a short, relevant shortlist with stripe directory search. Use this even when the user never says “Stripe Directory” — any request to find vendors, tools, partners, or providers for a vertical, workflow, pain point, or job-to-be-done.

Most requests are discovery — find and compare services. That is the core job below. Some services are also MPP-supported (MPP = Machine Payment Protocol), meaning you (the agent) can pay their HTTP 402 (Payment Required) endpoint and consume them directly. When the user actually wants to use or buy a service, present those results and offer to purchase — see “Purchasing” at the end.

Process

Clarify only what’s missing: buyer/vertical, job-to-be-done, must-have capability, geography (only if it matters).

Search iteratively: stripe directory search "<query>" --format json

Short noun phrases, one angle per query; run 1-3, then broaden/narrow on results.

Angles to cover: vertical → workflow → pain point → adjacent. Two examples:

services/trades: vertical (electrician software, electrical contractor) → workflow (field service management, dispatch invoicing estimates) → pain point (job scheduling, quote automation) → adjacent (home services automation, contractor crm).

SaaS/software: vertical (b2b saas billing, developer tools) → workflow (subscription management, usage-based metering) → pain point (failed payment recovery, revenue recognition) → adjacent (analytics dashboards, customer onboarding).

Hard constraints → filters: --countries-supported=US, --has-stripe-app=true, --link-supported=true, --stripe-projects-supported=true.

If the user wants to use/buy a service, also pass --mpp-supported in at least one search to find results you can pay for programmatically.

Sparse niche? Raise --limit and try the next --page before concluding it’s empty.