REST API

Authentication

There isn't any. Every endpoint is public and read-only.

No keys, no accounts

You do not need an API key, OAuth token, or account to call any endpoint. There is no signup and no rate-limit dashboard. Any Authorization header you send is ignored. The same applies to the MCP server and WebSub hub.

Read-only

Nothing here mutates state on our side. The REST endpoints are GET-only; the MCP endpoint accepts POST but exposes only read tools over the review dataset. You cannot create, edit, or delete reviews through this API.

Reasonable use

The dataset is small and cacheable — please treat it that way. Prefer conditional requests (ETag / If-None-Match) and the incremental /api/reviews/since/{date} endpoint over re-fetching the full dataset on a tight loop. If you need a live push instead of polling, subscribe via WebSub.

Attribution

Authentication is free; attribution is requested. If you republish or surface this data, please credit the source. See how to cite for the recommended attribution string, a BibTeX entry, and the schema.org Dataset reference.