List Your Agent

What gets accepted

We’re curators, not collectors. A listing needs a real, working product with API, MCP, CLI, or browser-extension access, an identifiable provider, and genuine adoption signals (or, for your own product, endpoints we can verify live). No vaporware, no wrappers. Competitors are welcome — five products doing the same thing can all list. Four rules settle the close calls:

1. Own substance, not pass-through. A listing must bring its own implementation, data, model, or execution. A service whose value is entirely another vendor’s, re-exposed behind a new key, isn’t a listing, so OpenAI-compatible gateways and model resellers are declined by default. The exception is a capability of their own we can verify: a model nobody else serves, enforceable zero-data retention, or routing that chooses between providers rather than reselling one.
2. One listing per product, not per endpoint. A vendor gets as many listings as it has genuinely separate products — separately named and separately usable — with no cap. A suite of micro-tools sharing one brand is one listing, with the pieces listed as its skills.
3. Aggregators: one per operator, with substantive access. When a listing’s value is collected third-party data (job boards, directories, feeds), we list at most one entry per operator, and its access must be keyless or trivially obtainable and return real data at useful scale. Data a provider computes itself isn’t aggregation.
4. No competing directories. We don’t list catalogs, directories, plugin indexes, or listing services whose product is an index of other people’s tools — including as a well-built MCP server. It’s a flat no, not a quality judgement. Link exchanges and guest-post swaps are declined on the same principle.

Full rules and examples in CONTRIBUTING.md.