qualify_project
Given a product, work out which platforms it qualifies for right now, which it could qualify for after supplying something (with the exact list of what is missing), and which are structurally out of reach. It also hands back recommended: the run in the order it should be worked, so the plan comes out of the directory rather than out of what you remember of the web. That order is decided by goal and budget, and when they have not been answered the response says what it assumed and carries the questions to put to the maker: ask them, call again with the answers, and store them with update_project so nobody asks twice. Needs no account: describe the product inline. Every field is optional and an unanswered field becomes a gap to fill rather than a rejection.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | ||
| docs | No | ||
| goal | No | What this run is for, which decides the order of it. `already-live` means the product is out and wants listings, links and traffic now, so the run leads on fast approvals, dofollow links and strong domains. `launching-later` means there is a launch date ahead, so it leads on the platforms with months of queue. Ask the maker rather than guessing: absent, it is inferred from `stage` and the response says so. | |
| name | No | ||
| stage | No | ||
| budget | No | Whether platforms that charge to list may appear in the run. Absent means `free-only`, which is the assumption that cannot cost anybody anything. `freemium` platforms are in the run either way: their submission is free, and paying to skip their queue is a separate question at the form. | |
| launchAt | No | ISO 8601 date the maker is launching on, when they have named one. | |
| demoVideo | No | ||
| categories | No | Every audience and form factor this product belongs to, not just the main one. A product is often several at once, and one missing tag is one directory it never hears about: a repository holding a browser extension and a web app is `extension` and `web`, and an open-source AI dev tool is `open-source`, `ai` and `dev`. Look at what the product actually ships before you answer: a manifest.json means `extension`, an ios or android target means `mobile`, a public repository means `open-source`, an mcp server is `mcp`, a workspace with several of those means all of them. Then answer what it is commercially, which is a separate question and the one most runs lose platforms on: most launch boards say what they take by who ships it, not by what it runs on, so a subscription mobile app is `mobile` and `saas`, anything a solo maker or small team shipped is `indie`, and something sold to companies is `b2b`. Leaving those off does not make the run safer, it makes it shorter. Tags: agent-skill, ai, b2b, christian, community, content, design, dev, directory, extension, free, hardware, indie, local, marketing, marketplace, mcp, mobile, no-code, open-source, prelaunch, productivity, saas, turkish-founders, web. | |
| coverImage | No | ||
| logoSquare | No | ||
| openSignup | No | ||
| publicRepo | No | ||
| pricingPage | No | ||
| domainRating | No | ||
| pricingModel | No | ||
| livePublicUrl | No | ||
| privacyPolicy | No | ||
| monthlyTraffic | No | ||
| acceptsBacklink | No | ||
| payingCustomers | No |