API
Read-only JSON over the RepoCritics corpus. The point is that the summarising has already happened: an agent answering “is this library still maintained?” can read one wiki page here instead of re-parsing a README, a release feed and four issue threads.
No key, no signup, no quota form. Free, and staying free — the corpus is community-written and reading it should not have a turnstile in front of it.
Base URL
https://repocritics.com/api/v1Endpoints
| GET | Returns |
|---|---|
/categories | Every category, with the tag filters that define it |
/tags?limit=50 | Tag vocabulary across the corpus, most frequent first |
/popular?category=devtools | Highest-scoring repositories, optionally within one category |
/search?q=rust+web+framework | Full-text search — indexed, so ordinary prose queries work |
/repos/github/facebook/react | One repository with its scores and reviews |
/repos/github/facebook/react/wiki | The community wiki page — the summarised form worth reaching for first |
/repos/github/facebook/react/reviews?limit=10 | Community reviews for one repository |
/reports/{repoId} | Cached deep-analysis report, when one exists (404 when not) |
Try it
curl https://repocritics.com/api/v1/repos/github/facebook/react/wikiRate limits
100 requests per IP per 24 hours, counted per endpoint. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset; going over returns 429 with Retry-After. If that ceiling is genuinely in your way, say so — it is set where it is to stop scrapers, not to meter real use.
Caching
Responses are edge-cached for a minute and revalidate in the background, so a repeated read is cheap for both of us. Send conditional requests if you can; the corpus changes on the order of hours, not seconds.
For agents
Three machine-readable entry points, in descending order of specificity:
/openapi.json— OpenAPI 3.1 description of everything above/.well-known/ai-catalog.json— Agentic Resource Discovery catalog, so a registry can index the API rather than the marketing page/llms.txt— prose orientation for a model arriving cold
There is also an MCP server exposing the same corpus as tools, so an agent can reach it without writing HTTP calls:
claude mcp add repocritics -- npx -y repocritics-mcp-serverSource at github.com/repocritics/mcp-server (MIT). It runs on your machine and talks to this API over HTTPS — no key, nothing stored locally.
Using the data
Wiki pages are written by contributors at github.com/repocritics/wiki. Quote them, build on them, feed them to a model — just attribute RepoCritics and link back, the same courtesy the contributors extended by writing them in the open. Full terms are on the terms page.