https://developers.digitalyser.io/docs/operations/changelog Every change to the public contract, dated. en https://developers.digitalyser.io/docs/operations/changelog digitalyser-contract-2026-09-10 Thu, 10 Sep 2026 00:00:00 GMT Added: - Response bodies are documented. Fifteen of eighteen operations now carry a response schema. The three that do not are the capability operations: invokeCapability returns the payload of whichever capability was invoked, so it has no fixed shape. - Eighty-three fields carry a description, and forty-five carry an example — concentrated on what a reader cannot guess: what a null score means, which clock a freshness field measures, and why a cohort verdict does not qualify an individual axis. - Enum values are published on 128 fields. Where a field accepts a closed set, the contract now lists it instead of declaring a bare string. - The contract is downloadable at /openapi.json (/openapi.json) — the same document the server publishes, importable into Postman, Insomnia, Bruno or a client generator. - Developer portal published at developers.digitalyser.io, with a cookbook (/docs/cookbook), a glossary (/docs/guides/glossary) and flow diagrams (/docs/guides/flows). - Public status page at status.digitalyser.io (https://status.digitalyser.io), with capability-level probes and an incident feed.