LaunchRepo.

Use case

Launch your AI tool on 100 AI directories with your own agent

AI tool directories are the one category that has kept growing. LaunchRepo ships 100 playbooks for them — plus the general launch platforms — and lets the agent you already use do the listing.

If you build an AI product, the directories that matter are mostly AI-specific: “best AI tools” lists, category pages, weekly roundups. There are many of them, they change often, and most ask the same questions in a slightly different order. LaunchRepo’s catalog tags 100 of its 346 platforms as AI tool directories, each with a playbook that says what to prepare, which fields block a submission and what “live” looks like there.

The specific pain: a category that never stops growing

AI directories are numerous, fast-changing and inconsistent. Doing them by hand means re-checking every one before you even start:

Dozens of near-identical forms
Name, one-liner, category, pricing model, “is there a free plan”, logo, screenshot — the same fields, different limits, different moderation.
Availability changes monthly
Free routes close, submission forms move, some directories switch to paid-only. A list from last quarter is already partly wrong.
Unclear what got published
Many AI directories accept a submission silently and publish weeks later, or never. Without a tracker you cannot tell which.

How the workflow fits an AI product

  1. Playbooks with the AI-specific fields

    Pricing model, free tier, model used, category tags — the playbooks list what each AI directory asks for so product.json can hold the answers once.

  2. Recheck before every attempt

    The runbook has the agent confirm the current free route and availability on the platform itself before submitting. A stale catalog entry becomes “unavailable” in the tracker, not a failed run.

  3. Honest facts only

    The agent never turns planned features into shipped ones and never invents customer counts or integrations. If a mandatory fact is unknown, the platform is recorded as blocked with the missing fact.

  4. Two waves: AI directories, then launch platforms

    Most AI products fit both the AI-specific directories and the general launch platforms. The tracker keeps both waves in one file with one set of states.

Which directory categories matter

The catalog tags every one of the 346 platforms with one category. The counts below are computed from the catalog at build time; how many platforms actually fit your product is something your agent checks per directory before it submits anything.

  • AI tool directories

    100 playbooks

    The core category for an AI product: directories, lists and roundups that only accept AI tools. Category fit is rarely the question here; completeness of the profile is.

  • Product launch platforms

    104 playbooks

    General launch platforms still matter for the launch day itself and for the first wave of attention beyond the AI niche.

  • Software and tool directories

    85 playbooks

    General tool directories that list AI products alongside everything else; worth a second pass once the AI-specific ones are done.

Example platforms from the catalog

Example platforms from the catalog that accept AI tools. Product Hunt has a public field guide on this site; the others are covered by the playbooks in the repository.

  • ToolPilotAn AI tool directory with an embedded form, tight word limits and a free-with-badge route.
  • Stork.AIAn AI tool directory that analyses your URL first; the free route needs its badge in your homepage HTML.
  • ToolDirsA tool directory with a 500-character description minimum and a free listing below the paid cards.
  • Product HuntStill the launch day most AI tools plan around; the playbook covers scheduling and the maker checklist.Field guide →
  • AlternativeToAn alternatives directory where AI tools are listed against the products they replace.

What LaunchRepo does not do

  • It does not pick “the best AI directories” for you. The catalog ships with a priority guide; your agent qualifies each platform against your product before submitting.
  • It does not guarantee that a directory publishes, links or ranks your tool. Many AI directories moderate slowly or only publish paid spots.
  • It does not run in the background. Your agent works in your session and hands CAPTCHAs, 2FA and paid decisions to you.
  • It does not cover agent usage. Tokens are billed by your provider; the software is a one-time payment.

Licence, in one sentence: pay once, then use it for an unlimited number of software products that you or your company own and operate, with as many agents as you like. Launching products for clients needs a separate licence.

Questions

How many of the 100 AI directories will list my tool?

Unknown until your agent tries. Every directory has its own rules and review queue; the tracker records submitted, pending review and live separately so the number you report is real.

Are the AI directory playbooks kept up to date?

The catalog does not pretend to be current: entries default to “recheck”, and the runbook has the agent confirm availability and the free route on the platform before every attempt. The changelog lists catalog releases.

Do the playbooks also cover general launch platforms?

Yes. The catalog holds 346 playbooks in six categories; AI directories are the largest single group after launch platforms, and an AI product usually fits both.

Which agent should I use for the submissions?

Any agent that reads files and drives a browser — Claude Code, Codex, Cursor or a browser agent. The agent pages on this site describe the setup for each.

Can I list several AI tools with one licence?

Yes, as many as you own and operate. Each gets its own product.json in the same workspace; the playbooks and the browser setup are shared.

Ready when your next launch is

The launch price is €99.98, once. It rises 20 % after every 20 sales; the pricing page shows the live price, what is in the repository and the licence in short.

See pricing