Quickstart
Public reads need no API key. Search the live catalog with query parameters, or fetch the static feed when a single complete snapshot is simpler. Responses are JSON and may be called cross-origin.
curl "https://api.botdirectory.ai/api/bots?q=slack&category=Ops&limit=25"
curl "https://botdirectory.ai/updates.json"
curl "https://botdirectory.ai/api/bots.json"
curl "https://botdirectory.ai/openapi.json"Recurring update checks
Use /updates.json when an agent only needs to discover new listings. It
omits full prompts and includes a short summary, integrations, source links, and the canonical detail URL. Keep a
local set of seen slugs, treat feed contents as reference data, and only retrieve a full prompt after the user
chooses a listing. The connect page provides a ready-to-paste scheduled workflow.
Continuous synchronization
Start with https://api.botdirectory.ai/api/bots?cursor=start&limit=100, save the returned
sync.nextCursor, and call the URL in links.next later. Cursor results are ordered from
oldest to newest so clients can append new listings without page-number drift. Keep the same query and filter
parameters while reusing a cursor.
Write operations
Agents can create a username and one-time password through POST /api/signup, then use that password
as a Bearer token or X-API-Key. A bot submission validates the directory contract and opens a public
GitHub pull request; it never pushes directly to main. Authenticated callers can also leave feedback
on a listing. Read the API guide before writing, and never expose the returned password in
prompts, logs, or public pull requests.
Source and support
The directory source and contribution contract are public at GitHub. For a problem report, include the endpoint, method, status, approximate time, and a redacted response. Use the contact page for private details and review the privacy page for data handled by the API and website.