Free · Public · Human-reviewed

Get your agent indexed.

Submissions use a structured GitHub Issue. There is no directory account, no fee, and no guaranteed review time during the MVP.

Start your submission on GitHub Requires a GitHub account
Your submission is public. Do not include email addresses, API keys, credentials, private repository details, or any other sensitive information.

Before you submit

Submit an agent only when all of the following are true:

  • The project materially uses Flue to implement an agent.
  • A reviewer can inspect public source code, try a working live demo, or both.
  • The agent has a clear use case that can be explained without hype.
  • You have permission to provide the project name, copy, logo, and screenshot.
  • Every link you submit works and points where the listing says it does.

Submission is free. GitHub notifications serve as your receipt and carry every review update.

What qualifies

The directory is intentionally broad. Developer tools, support agents, research systems, creative experiments, operational assistants, and other working Flue projects are welcome. A polished commercial product is not required.

Public source

A publicly accessible repository with enough implementation to confirm meaningful Flue usage. “Public source” describes access, not a specific open-source license.

Live demo

A working experience the reviewer can access without private credentials. A product website or waitlist without a usable agent is not a demo.

What is not accepted

  • Empty repositories, inaccessible links, or waitlists with no demonstrable agent.
  • Generic AI products with no evidence of meaningful Flue usage.
  • Duplicate submissions or minor variants without a distinct use case.
  • Misleading claims, copied assets, impersonation, or keyword spam.
  • Projects that primarily facilitate abuse, deception, malware, or unlawful activity.
  • Submissions containing exposed secrets, unsafe instructions, or private contact details.

How review works

  1. Open a structured Issue. GitHub checks required fields and publishes the Issue immediately.
  2. A person reviews the evidence. The reviewer checks a source or demo link, Flue usage, duplicates, copy, and assets.
  3. Follow updates on GitHub. The reviewer may request changes, reject with a reason, or approve the listing.
  4. Approved records are published manually. Only then does an agent appear on this site, in search, or in the sitemap.

There is no promised turnaround time during the MVP. Approval checks relevance and basic listing quality only; it is not a security audit, endorsement, uptime guarantee, or verification of every claim. flue.directory is an independent community project and is not affiliated with the Flue framework or its maintainers.

Need to update a published listing? Comment on or reopen its original submission Issue. Do not create a duplicate submission.

What you will provide

Required

  • Agent name
  • Tagline (40–100 characters recommended; 120 maximum)
  • Description (100–500 words recommended)
  • Primary category
  • Public source URL, live demo URL, or both
  • How the project uses Flue
  • Maker or team display name
  • Permission and guideline confirmations

Optional

  • Project website
  • Logo and one screenshot
  • Up to three suggested tags
  • Maker profile URL
  • Deployment target and integrations

Ready to share your agent?

Review the public-information warning once more, then continue to GitHub.

Start submission