Documentation

The product profile

One profile per product holds every fact a directory form asks. Your agent fills forms from it and from nothing else, so what is in it, and what is not, decides how far a submission gets.

What it is

The profile is a set of product.json keys stored on your account. You edit it on the dashboard (Product profile), and your agent reads it with get_product_profile and writes it with save_product_profile. A save is merged onto what is stored for the same website, so your agent sends only what changed, and a dashboard save never drops a key the form does not show.

The product is identified by its website. Free and Launch accounts hold one product, Pro any number. Empty stays empty: nothing is invented, so a field you have not answered is asked about, never guessed, and your agent may save only facts you confirmed.

The submission pack

Ten fields that nearly every directory form asks. The dashboard counts how many are filled and lists the missing ones, and the profile marks them as required (a draft still saves without them).

  • Product name
  • Product URL
  • Contact email
  • Tagline
  • Short description
  • Long description
  • Categories
  • Pricing
  • Pricing line
  • Logo

Length matters: a short description of about 200 characters and a long one of 500 to 600 fit most forms, and the editor counts characters as you type. A logo is a square image (a location, either a URL or a path in your repository); a cover image is landscape, about 3:2.

Asked once

Directories ask for facts about the company and the person that no repository holds. Your agent asks you for all of them in one message, then saves them, so no form has to stop to ask. These are the ones it checks for:

  • Your name as directories should show it
  • Country
  • Year founded
  • Team size
  • Company LinkedIn page (URL, or none)
  • X profile
  • Whether you will show a directory's badge on your site
  • Whether you would pay a directory that has no free route
  • The longest wait for a free listing you accept (a month, two, four, or any)

What the product is

Pick everything that fits. Directories accept or refuse on this, so leaving one off is the main reason a directory says you are out of reach when you are not. With none chosen, the type is read from the project type and nothing is filtered on a guess.

  • SaaS or web app
  • AI tool
  • Developer tool
  • Has an MCP server
  • Mobile app
  • Desktop app
  • Browser extension
  • Integration or plugin
  • Online shop
  • Local business
  • Affiliate program
  • Template, theme or starter kit
  • Built with Bolt.new
  • A custom GPT (GPT Store)

Some directories also take only certain regions (region:eu includes the UK); the company's country decides those.

The badge answer

Many free listings ask for the directory's badge or a link back on your site, and take the listing down if it comes off. Will you put one on your site? Your answer (show_badge) decides the plan instead of being asked at every form:

  • Yes: those directories are offered, and your agent adds the snippet to your footer for you to review and deploy.
  • No: directories whose free listing needs a badge are marked not a fit, with the reason, and left out of the plan.
  • Not answered: they are listed with "you have not said", and the dashboard asks.

Your agent never edits your site without showing you the change, and committing and deploying stay yours.

Longest wait and skipped directories

Some free queues run for months. Longest wait you accept (max_wait_days: a month, two or four; unset means any wait) leaves out a directory whose stated wait for a free listing is longer, marked not a fit with the wait and your limit. A directory that does not state its wait is never judged on a guess.

When you take a directory off the plan (your agent records it as skipped), it is remembered in your profile (skipped_directories), so planning again does not bring it back. It shows as not a fit, with the reason; ask your agent to submit there, or record another status for it, to put it back.

What it already has

Tick what is true today. A directory that needs something you have not ticked is marked one step away or not a fit, and an absent key means "not yet".

  • A live URL anyone can open
  • Signup open without a sales call
  • A public pricing page
  • A square logo
  • A cover or screenshot image
  • A short demo video
  • A public code repository
  • Docs or a README
  • A privacy policy page
  • Paying customers
  • A LinkedIn company page

Company and founder

Stageidea, prototype, beta, live
Pricing modelfree, freemium, paid, subscription, one time
Companyname, country, team size, funding, incorporated or not, launch date, year founded, city, and the company's LinkedIn page (a URL, or none)
Founderfirst and last name, contact email and phone (in international format; a playbook reformats it where a form wants another), bio, X profile, LinkedIn, GitHub and website
Other answersthe project type and use case forms ask, and how people hear about it (the referral source)

Story and categories

Some directories, mostly developer and launch platforms, ask for a story. Seven sections map onto them: inspiration, what it does, how it was built, challenges, accomplishments, lessons learned and what's next. The tech stack is a list of tags.

Features and use cases are two short lists, one item per line (features and use_cases). Directories that ask for them, usually as bullet lists, get these instead of text your agent writes on the spot, so every directory shows the same claims. Your agent can draft them from your README, and you edit them here.

Categories are a list, plus a category selection for dropdowns: the preferred category, acceptable synonyms and a secondary one, so your agent picks the closest option a directory offers instead of the first one.

How answers decide the match

Product typeNarrows the catalog to directories that take that kind of product. A software listing site does not take web apps; an AI-only list rejects other tools; a local-business site needs a local business.
Region and countryRegional directories are left out for products outside the region.
Badge answerFree listings that need a badge are offered, or marked not a fit, or asked about.
Longest waitA directory whose stated free wait is longer than your limit is marked not a fit. An unstated wait is not guessed.
Free or paidA directory with no free route is on the plan, marked not a fit (free only, or a fee above $30 when you chose small ones), or held back until you answer.
What it hasA public repository, a pricing page, a square logo and the like are checked against each directory's requirements.
Domain ratingA directory's minimum DR is compared with yours. A known gap is a not a fit with the numbers; an unknown one is a check listed for you.
Team size, LinkedIn pageCompared with directories that ask for a minimum team or a company page.

A known gap is stated as a verdict ("needs a domain rating of 30, and yours is 12"); a requirement your profile cannot answer is listed as a check, so nothing is hidden and nothing is assumed.

Let your agent fill it

The quickest way is to say to your agent: "Fill in my LaunchDistro product profile from this project." It reads your repository and site, reuses wording that already exists, shows you the profile, asks once for what no repository holds, and saves it. The dashboard has the same request as a copyable prompt (Product profileand the Overview checklist). Then Directories shows where the product qualifies. See the tools involved: product profile tools.

Your next 10 directory submissions are free.

Add it to Claude or Cursor, describe your product once, and watch the first form fill itself.