How the directory works

Every other AI directory is abandonware — maintainers stopped merging PRs months ago. We took a different approach. Paste our badge on your site, open a PR, our bot verifies in seconds and merges itself. If you’re running a coding agent, two prompts do the whole thing for you — no manual badge paste, no manual PR.

Easiest path

1. Hand these prompts to your coding agent

If you’re using Claude Code, Cursor, Codex, or Gemini Code Assist (or any agent that can read URLs and run shell commands), you don’t need to read the rest of this page. Paste these two prompts, in order, and the agent does the badge paste, the PR, and the submission for you.

Step 1 — audit prompt (no commits, no fetches, no POSTs):

Read https://github.com/Prompt-Frenzy/ai-directory/blob/main/README.md and find the submit handler in the Prompt-Frenzy/prompt-frenzy2 repo (the route serving POST /api/directory/submit). Summarise: (1) what gets committed to my repo, (2) what data leaves my machine and to which endpoint, (3) what the server does with that data, (4) anything I should know before running the submission. Make NO commits, fetches, or POSTs.

The agent reports back exactly what would happen. You read it, confirm, then move to step 2.

Step 2 — submission prompt (after you’ve approved the audit):

Submit <my tool URL> to the PromptFrenzy AI directory per https://github.com/Prompt-Frenzy/ai-directory/blob/main/README.md. Paste the badge HTML on the site's footer first (commit + push), then call POST /api/directory/submit with the YAML payload.

The agent commits the badge anchor to your repo, pushes, then POSTs the payload. Our server verifies the badge is live + dofollow before opening the directory PR. Same code path as the manual flow below — same badge requirement, same auto-merge.

Or do it by hand

The manual flow below is the same machinery, just operated by a human. No coding agent? Skip to the web form.

2. Paste this badge somewhere on your site

Anywhere visible to crawlers: footer, sidebar, or an /about page. Must be static HTML (no JS-rendered DOM — our verifier doesn’t run JavaScript), dofollow (no rel="nofollow" or rel="sponsored"), and on a domain you control.

Pink (default)

Brand-forward. Co-brand signal works hardest. Fits most sites.

Download SVG

<a href="https://www.promptfrenzy.com/directory" rel="noopener"
   target="_blank" title="Featured on PromptFrenzy AI Directory">
  <img src="https://www.promptfrenzy.com/badges/directory.svg"
       alt="Featured on PromptFrenzy AI Directory"
       width="220" height="44" loading="lazy" />
</a>

Monochrome dark

Subtle on light backgrounds — fits Stripe-style minimalist sites.

Download SVG

<a href="https://www.promptfrenzy.com/directory" rel="noopener"
   target="_blank" title="Featured on PromptFrenzy AI Directory">
  <img src="https://www.promptfrenzy.com/badges/directory-mono-dark.svg"
       alt="Featured on PromptFrenzy AI Directory"
       width="220" height="44" loading="lazy" />
</a>

Monochrome light

Subtle on dark backgrounds.

Download SVG

<a href="https://www.promptfrenzy.com/directory" rel="noopener"
   target="_blank" title="Featured on PromptFrenzy AI Directory">
  <img src="https://www.promptfrenzy.com/badges/directory-mono-light.svg"
       alt="Featured on PromptFrenzy AI Directory"
       width="220" height="44" loading="lazy" />
</a>

All three: 220×44 SVG, <1KB, system fonts, no tracking pixels. Same href, same anchor — the bot accepts any of them.

3. Open a PR with your tool’s YAML

Add a YAML file under tools/your-tool-slug.yaml in the directory repo. Use tools/_example.yaml as a template.

name: Your Tool Name
url: https://yourtool.com
description: One sentence (max 200 chars), factual, no superlatives.
category: image-generation
tags: [photo-editing, portrait]
pricing: freemium
badge_url: https://yourtool.com   # the page where you pasted the badge

4. Our bot does the rest

Fetches your badge_url and looks for the badge anchor
Comments on the PR with pass or fail — typically under 60 seconds
Auto-merges if it passes
Opens a tracking issue to follow your listing

If verification fails, the comment explains exactly what we couldn’t find. Fix and push — the verifier re-runs on the new commit.

No coding agent or GitHub account? Use the web form

Same code path as the agent prompts and the manual PR flow above — same badge verification, same auto-merge. Just operated by a person filling fields instead of an agent running curl.

Web form

Paste the badge on your site first (any of the variants above), then fill out the short form. The bot does the git work on your behalf. Open the form →

Advanced: one-call API (for agents that can’t fork)

Most fine-grained GitHub PATs — including the ones AI agents are typically issued — can’t fork to a third account. The agent prompts above sidestep this by committing to your own repo. If you’re scripting submissions from somewhere else, you can also call the endpoint directly:

POST /api/directory/submit

JSON payload + badge_url. The server uses the directory bot’s own write access to create the branch, commit the YAML, and open the PR. Returns 201 with pr_url + pr_number. Bad payloads return 400 with field-level details. Full endpoint spec.

The badge requirement is the spam filter, not the GitHub auth layer. Whichever path you take, the listing only goes live if our verifier sees the badge anchor live + dofollow on the URL you declare.

Re-checks and removal

When	What we check
On your PR	Initial badge present, dofollow, on the URL you declared
Daily for first 7 days post-merge	Catches paste-then-yank gaming
Weekly thereafter	Ongoing health check

After 3 consecutive failed checks your listing moves to failed state — still visible, but flagged. After 30 days in failed state without resolution your listing moves to /directory/removed — public, permanent.

To reinstate: re-add the badge and comment /reverify on your tracking issue. The bot picks it up within an hour.