Get many entries at once

Up to 50 entries in one request: the batch form of GET /api/v1/entities/{vhid}. Each key is answered exactly as that route answers it, in the order asked: the entry (status: "ok", the same body), or status: "not_found" where it would answer 404. A deleted entry and a key that names nothing look the same. An old name or a merged entry’s key answers with the entry it now leads to; entity.vhid says which. A key repeated is answered once. The answer is 200 whatever each key answers: only the request itself is refused. A Wikidata QID is not a key here, as it is not at the single read: GET /api/v1/search?q=Q42 finds the entries linked to an item. A key that contains a comma (only an old name can) cannot be asked for in a batch: use the single read.

Rate limit. Each key counts as one read against the IP address’s budget, so 50 keys cost what 50 single reads cost, and the request is refused (429) when the budget cannot cover it. A response the edge already holds costs nothing.

Any origin may read it: Access-Control-Allow-Origin: *, methods GET and OPTIONS, no credentials. An OPTIONS preflight answers 204. No key is needed. A request that sends one (Authorization: Bearer) has it checked, so a wrong, revoked or expired key is refused 401, and is counted against the key’s read limit; it gets the same answer, marked no-store.