Data and API
Machine access is a first-class concern: researchers and agents should consume the same structured records the website shows, with stable identifiers, explicit versioning and typed uncertainty (a level is a point, an interval, a lower bound, an explicit set or “not evaluable”; never a flattened integer).
Source: API, MCP and Agent Interface Specification §§1–5; Decision Register D-034.
Available now
| Endpoint | Returns |
|---|---|
GET /api/v1/rules | Published rules versions (currently pilot-1.0), engine version, reference-implementation provenance, θ and w. |
GET /api/health | Liveness with feature and adapter states only. |
Planned (not yet served)
GET /api/v1/incidents, /incidents/{id}, /incidents/{id}/assessments, /assessments/{id}, /trends/exceedance, dataset snapshots with checksums and coverage metadata, feeds and an MCP tool interface. The draft contracts (OpenAPI, JSON Schemas, MCP tools) are part of the specification pack, which is not yet published; they will be linked from here once they are reachable without an account. Until an endpoint is listed above it returns nothing; no incident data exists yet.
Licence and reuse
Intended: factual dataset CC0 1.0, methodology and documentation CC BY 4.0, software Apache 2.0, pending legal review; see about. Third-party sources keep their own rights: the dataset will store metadata, provenance and lawful excerpts or links, not republished works.
Source: Licensing, IP and Trademark Policy §§2–5.