3 followers
What do you think? …
Hi Product Hunt,
APIDirectory started in 2022 as a side project: a directory of about 1,400 public APIs with
screenshots. It sat there for two years while the interesting question changed. It used to
be "where do I find an API?". Now it's "who keeps the record straight, and can an agent use
it?". So this year I rebuilt it as a registry, in the boring, literal sense.
What it is
- Every API is a numbered record (APD-01441 and so on) of what the crawler actually
observed: link, auth model, spec format, pricing model, docs status, last crawl, endpoints
parsed from the API's own OpenAPI spec, and a changelog. 2,365 entries so far across 54
categories, 762 specs parsed. Dead links stay on the record, because the record says what
we saw.
- Unclaimed entries look provisional on purpose. If you own one, claim it with an email on
your domain (or a DNS record). The stamp flips to VERIFIED OWNER and the entry is yours to
maintain. Claiming is free.
- The whole index is free to use: web search, a JSON API (`/v1/search?q=weather`, no key),
and an MCP server at `apidirectory.com/mcp`, so Claude Code, Cursor or any MCP client can
search it and subscribe to an API in the same session.
When an owner wants to sell access, there are two ways:
1. The marketplace: buyers get one key on the listing, our gateway meters every call, bills
monthly, and we keep 8%. No monthly fee.
2. A white-label storefront: hosted docs and a try-it console generated from your spec,
instant keys, buyer accounts with usage, a status page we monitor independently, your own
domain, billing on your own Stripe. $79/mo flat, no revenue share. A $29/mo add-on makes
the storefront an MCP server of its own: one tool per operation of your spec, metered on
the buyer's key like any other call.
One rule that won't change: paid placement is always stamped, never blended into the
organic results. The registry is only useful if you can trust what's on it.
What I'd love your take on
1. What's missing from the index? Search for the APIs you use. If one isn't there, /submit
is free and takes a minute; I'll be approving all day.
2. If you own an API: would you sell through something like this? What would stop you?
3. Agent people: is search → subscribe → key what you'd expect from an MCP server, or is
there a step you'd want done differently?
Feel free to ask me anything about it, I'll be here all day. Thanks!
Hi Product Hunt,
APIDirectory started in 2022 as a side project: a directory of about 1,400 public APIs with
screenshots. It sat there for two years while the interesting question changed. It used to
be "where do I find an API?". Now it's "who keeps the record straight, and can an agent use
it?". So this year I rebuilt it as a registry, in the boring, literal sense.
What it is
- Every API is a numbered record (APD-01441 and so on) of what the crawler actually
observed: link, auth model, spec format, pricing model, docs status, last crawl, endpoints
parsed from the API's own OpenAPI spec, and a changelog. 2,365 entries so far across 54
categories, 762 specs parsed. Dead links stay on the record, because the record says what
we saw.
- Unclaimed entries look provisional on purpose. If you own one, claim it with an email on
your domain (or a DNS record). The stamp flips to VERIFIED OWNER and the entry is yours to
maintain. Claiming is free.
- The whole index is free to use: web search, a JSON API (`/v1/search?q=weather`, no key),
and an MCP server at `apidirectory.com/mcp`, so Claude Code, Cursor or any MCP client can
search it and subscribe to an API in the same session.
When an owner wants to sell access, there are two ways:
1. The marketplace: buyers get one key on the listing, our gateway meters every call, bills
monthly, and we keep 8%. No monthly fee.
2. A white-label storefront: hosted docs and a try-it console generated from your spec,
instant keys, buyer accounts with usage, a status page we monitor independently, your own
domain, billing on your own Stripe. $79/mo flat, no revenue share. A $29/mo add-on makes
the storefront an MCP server of its own: one tool per operation of your spec, metered on
the buyer's key like any other call.
One rule that won't change: paid placement is always stamped, never blended into the
organic results. The registry is only useful if you can trust what's on it.
What I'd love your take on
1. What's missing from the index? Search for the APIs you use. If one isn't there, /submit
is free and takes a minute; I'll be approving all day.
2. If you own an API: would you sell through something like this? What would stop you?
3. Agent people: is search → subscribe → key what you'd expect from an MCP server, or is
there a step you'd want done differently?
Feel free to ask me anything about it, I'll be here all day. Thanks!