RebbeHub for developers
RebbeHub is the open, community-edited index of Chabad Torah and media: every sefer and printing, every sicha and letter, every farbrengen and recording, the scans and the texts of each. All of it is open to read through the API, with no account and no key, and everything people can do on the site - suggest a fix, fix a line, sync a paragraph - a script or an AI agent can do through the API too, under the same review.
- API:
https://api.rebbehub.org/v1, described in full by OpenAPI 3.1 and the interactive reference. - For AI agents:
/llms.txtand an MCP server athttps://api.rebbehub.org/mcp. - TypeScript:
@rebbehub/client, a small typed client generated from the OpenAPI document. - Everything at once: weekly signed dumps (SQLite, JSON Lines, Parquet), a git mirror, webhooks and OAI-PMH for libraries.
Where to start#
- Getting started: your first requests, in curl and TypeScript.
- The data model: what an item is, ids and paths, Hebrew dates.
- Tokens and signing in: a personal API token, to act as yourself.
- Sending suggestions: how a change is made, checked and reviewed.
- Conventions: versions, errors, pages, caching, CORS; and rate limits.
- Rights: what may be copied, and what is only listed. Read this before you copy words or files anywhere.
The promises#
- Ids never change.
rh-7k2m9q4dnames the same item for good; paths (/likkutei-sichos/12/3) are readable and may move, with redirects. - /v1 changes only by adding. Fields and routes are added, never renamed or removed without a new version; see Stability.
- Machine output is labelled. Words a machine read (OCR) or heard (transcription), links it found and summaries it wrote say so (
machine: true,checked: false,origin) until a person checks them. Keep the label wherever you show them. - Rights are kept. Words whose source does not allow copies are listed but withheld (
withheldsays why), everywhere: the API, the dumps, the MCP server.
The code is AGPL-3.0; catalog facts are CC0; community text is CC BY-SA 4.0; texts from other sources keep their own licence (each text's licence).
Get started
Using the API
- The endpointsA guide to the routes, by what they are for
- API referenceEvery route, with examples, tried from the page
- Sending suggestionsHow a change is made through the API, checked and reviewed
- Rate limitsHow much, per address and per token, and being a good citizen
- WebhooksEvery approved change posted to you, signed
The catalog
Tools
For AI agents and machines
Hand an agent /llms.txt (where everything is) or /llms-full.txt (every page here and every route, in one file), or connect it to the MCP server.