Most AI directories grow by accepting submissions. That is a product choice. It also explains why so many boards feel interchangeable: the same logo wall, the same one-line blurbs, the same tools that shipped a landing page and never a pricing page that still loads.
If the job is “help someone open the right official site and know what the tool is for,” volume is the wrong scoreboard. The useful work is deciding what not to keep.
Here is the reject list I actually use when evaluating an AI or developer tool for a curated directory. None of these require a fake “I used it for three weeks” story. They are checks against public pages anyone can open.
1. Marketing-only, no task surface
Reject when the homepage is slogans, hero video, and a waitlist — and there is no clear input → output for a real job.
“AI-powered productivity for modern teams” is not a product description. A usable listing needs at least one concrete loop: paste a repo and get a PR draft, upload a PDF and get structured text, pick a model and get an API key that works. If you cannot name the loop after two minutes on the site, the directory entry will not help the next reader either.
2. Pricing that cannot be verified
Reject when pricing is “Contact us” with no public bands, or when the pricing URL 404s / redirects into a broken CMS.
Directories that list “Freemium” without a checkable plan page teach people the wrong habit: trusting a badge instead of a bill. If the official pricing page is gone, stale, or only available after a sales call, say so — or skip the listing until the page exists again.
3. No docs worth linking
Reject when there is no docs root, no GitHub README that explains install, and no API reference for a tool that markets itself as an API.
A directory link is often the last stop before someone wastes an afternoon. Official docs (or a maintained README with install, auth, and limits) are part of the product. “Coming soon” docs are not docs.
4. Clone spam and skin swaps
Reject near-duplicates that only swap the brand color and the LLM logo on the homepage.
The tell is structural: same feature bullets in the same order, same screenshot chrome, same “multi-model” claim with no routing or eval detail. Listing ten clones does not help a developer choose; it trains the board to rank whoever paid for placement first. Keep the clearest official product in the category; drop the rest until one of them shows a real difference (local-only mode, open weights, a distinct workflow, a license you can quote).
5. Star-count theater and borrowed trust
Reject when the pitch is mostly GitHub stars, Product Hunt badges, or “trusted by 10,000 teams” with no link to a primary source you can open.
Stars measure attention, not safety, uptime, or whether the license allows what you need. Same for download counters. They can sit in a “popularity” note. They should not be the reason a tool survives curation.
What a kept listing actually needs
The bar for keeping something is boring on purpose:
- A live official URL (not a Medium mirror, not a random Notion dump).
- A one-sentence job a stranger could act on.
- Enough scope notes that a reader knows platform, account, or license traps before they click through — without pretending the directory audited the vendor’s security program.
- A category that matches the job (coding assistant ≠ model gateway ≠ image app), so people are not scrolling a junk drawer.
That is why curated boards stay smaller than submission-fed ones. The empty slots are a feature.
WarpNav’s AI coding tools shelf is built around that filter set: Cursor, Claude Code, Aider, Windsurf, and similar tools sit there because each one has a checkable official surface and a named job — not because a form accepted another logo. The rest of the site follows the same idea across model apps, gateways, and open-source roundups: fewer rows, clearer official doors.
A short checklist before you trust any AI directory
- Does the entry link to an official domain you can verify?
- Can you state the tool’s job without copying the homepage slogan?
- Is pricing or licensing visible without a sales call?
- Are docs (or a real README) one click away?
- Would removing three near-clones make the category easier to use?
If a directory cannot survive those five questions, it is a billboard with search traffic — not a map.
Coverage is easy. Saying no is the product.
Top comments (0)