API reference
BACKD listings are queryable over REST and MCP. Responses are first-party catalog data: what is listed, conviction scores, and community verdicts. This is not a claim that a model cited or recommended a company.
MCP
No API key. Tools: search_startups, get_startup, list_categories, get_rankings, get_trending.
claude mcp add backd --transport http https://backd.io/api/mcp
REST auth
Free tier. Send the key as Authorization: Bearer bd_live_… or X-Api-Key. CORS is open. Issue a key while signed in via POST /api/v1/keys. The raw secret is shown once.
curl "https://backd.io/api/v1/startups?query=ai&limit=5" \ -H "Authorization: Bearer bd_live_YOUR_KEY"
Endpoints
/api/v1/rankingssessionParams: limit, offset
All-time conviction board. No key. Fields: rank, score, back_percentage, pass_percentage, votes.
/api/v1/trendingsessionParams: limit, offset
Listings ordered by trending score. No key.
/api/v1/searchsessionParams: q, category, limit, offset
Name or tagline search. No key.
/api/v1/startupssessionParams: query, category, sort (trending|conviction|name), limit, offset
Published listings. No key. 60 requests/minute anonymous, 600 with a developer key.
/api/v1/startups/:slugsessionParams: none
One published listing. No key.
/api/v1/categoriessessionParams: none
Controlled category vocabulary.
/api/v1/keyssessionParams: JSON body { name? }
Signed-in session required. Returns the raw key once. A key raises the public read limit. It is not required to read.
Founders: listing is still the product. Browse the catalog.