DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to mirror the whole bot directory into your own catalog with Botdirectory AI

Pull the canonical raw feed once and store every listing in your own system.

Who it is forA developer or team lead who wants the full directory inside an internal tool, search index, or dataset.

The problemCopying listings by hand does not scale, and paging through search results is slower than one bulk request.

The outcomeA local copy of every listing in the directory, which can be refreshed or searched without visiting the site.

What you need first

  • A browser or HTTP client to read the site and API
  • Git and a GitHub account to contribute by pull request
  • Node.js with pnpm to run the local validation and build
  • An agent or Grok Bot or Rakazo account to run a copied prompt

Steps

  1. Request the canonical raw feed at https://botdirectory.ai/api/bots.json.
  2. Save the response to a local file with a timestamp in its name.
  3. Parse the JSON and load each listing into your own store, keyed by its slug or name. (inferred, check the README)
  4. Compare the count and names against the previous snapshot to list what was added or changed. (inferred, check the README)
  5. Run pnpm install and pnpm build only if you also want a local copy of the site source, then check that your store matches the feed.

Prompt for your agent

Fetch https://botdirectory.ai/api/bots.json, save it as bots-<date>.json, and report the total number of listings and the names of up to 5 listings that are new since the last saved file. Verify that the count in the saved file matches the number of entries parsed.

Caveat. The feed reflects whatever the directory publishes at fetch time, so keep dated snapshots if you need an audit trail.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page