api
Public API
Unauthenticated read-only endpoints over scientific records, the status vocabulary, the publication policy and the demonstration fixture.
What it is
Static documents generated at build time. No request-time execution, no database, no authenticated surface. Every response envelope has a published JSON Schema and is validated against it during the build.
What it lets you do
Fetch claims, changes, the status vocabulary, the publication policy and the demonstration records as JSON. No key, no signup, no client library.
See a claim decomposed into components, each with what actually supports it — including the parts supported by nothing — plus its registered falsifiers, its open evidence debt and everything that changed since the last version.
Recompute a record's digest from the record itself, check an artifact's bytes against its published hash, or check the whole site against one manifest.
Look up exactly what a status term means, in a versioned document, instead of guessing from the word.
Limitations
- Scientific endpoints return empty sets, by design.
- No authentication, keys, rate limits, SDKs or webhooks exist, and none are needed for a public read-only surface.
- A request to an unknown path is answered by the hosting layer, outside Tiffany's error contract.
Interfaces
| Kind | Reference | Note |
|---|---|---|
| http api | /api/index.json | Discovery document. |
| schema | /developers/openapi.json | OpenAPI 3.1, generated from the same registry the routes come from. |
Related
- documented by — Developer and API portal
- part of — The laboratory
Documentation
Machine record
Licence: CC BY 4.0.
Human and machine records are generated from one source in one pass and are tested to agree on availability, access, release state and limitations.