The frozen API contract
IGRM's endpoints are not a moving target. This page is the machine-readable promise behind them: loading…, frozen . The full record is data/api_contract.json, generated once and committed, not regenerated by the daily pipeline — a frozen contract that rewrote itself every night would not be a contract. The generated OpenAPI 3.1 document serves software tooling; the Datasheet for Datasets records provenance, composition, recommended uses, and known limitations for reviewers. The on-demand API byte verifier checks the complete declared file set against its unsigned manifest and accepts an independently obtained manifest digest when a reader has one.
The promise
Loading…
Endpoints
| Endpoint | Format | What it is | Frozen fields |
|---|---|---|---|
| Loading contract… |
"Frozen fields" are the top-level keys (or CSV columns) promised not to be removed, renamed, or repurposed within this major version. New fields may appear on any payload at any time without notice here; that is additive and never breaks a consumer reading only the frozen set. For column-by-column construction of every field, see the codebook; for a plain-language description of each file, see the data page.
Versioning
This contract versions independently of methodology.md (which
tracks construct changes) and the igrm Python package (which tracks code). A
breaking change to any frozen field bumps the contract's major version and is announced here,
in the methodology changelog, and in the contract record. Contract v2 removed an operational
author queue that had been served outside the analytical API's scope; no research endpoint or
research data changed.