Laboratory › Developers › API status
API status
Operational only. Nothing on this page is evidence about any claim, and none of it can change one.
| Family | State | Endpoints | Notes |
|---|---|---|---|
| Scientific records | Available | 3 | Fixtures excluded |
| Reference documents | Available | 9 | Fixtures excluded |
| Demonstration fixtures | Available | 7 | Fixtures only |
| Integrity and crawler documents | Available | 4 | Fixtures excluded |
| Resources and capabilities | Available | 4 | Fixtures excluded |
| Research, evidence, module, dataset and release endpoints | Planned | 0 | The first finding, module or dataset clears release review. |
| Authentication | Not yet available | 0 | A non-public tier exists, or a write path exists. |
| API keys | Not yet available | 0 | Authentication activates. |
| Rate limits | Not yet available | 0 | A request-time computed endpoint exists, or abuse makes anonymous access unworkable. |
| Webhooks | Planned | 0 | A consumer needs latency below the polling interval, or polling load becomes material. |
| SDKs | Not yet available | 0 | Authentication, pagination or request signing makes a correct client non-trivial to write by hand. |
| Interactive playground | Deferred | 0 | Authentication exists and constructing a correct request by hand becomes genuinely hard. |
| Developer accounts and organisations | Deferred | 0 | Credentials exist and more than one party needs to manage them. |
| General graph query | Deferred | 0 | An external replicator needs a question the bounded set cannot express, twice. |
Incidents
None recorded. Research-integrity incidents — a provenance break, a wrongly-classified release, a withdrawal that failed to propagate — are tracked separately from uptime and would appear in the scientific change record, not here. Conflating the two would let an infrastructure outage look like a scientific event, or worse, the reverse.
Current figures
- Scientific releases
- 0 — empty by design
- Demonstration fixtures
- 1 identity, 3 versions
- Public endpoints
- 27
- Published schemas
- 15 — all enforced at build time
- API contract version
2026-09-10- Ontology version
1.3.0- Runtime
- static files only; no database, no server-side execution, no authenticated surface
Machine-readable status · site status
If this site disappears
Downloaded bundles still verify against their own digests. That is the availability guarantee that was actually engineered for, rather than an uptime figure.
PreviousUse policy