Documentation scope
An inventory of the gaps in these docs, with the reason for each. Written by us so you do not have to find them.
Known gaps covers gaps in the product. This page covers gaps in the documentation itself — the pages a developer portal of this kind usually has, that this one does not, and why.
| Missing | Why |
|---|---|
| An interactive API playground | Every endpoint requires a key, and keys are issued at onboarding. A playground that cannot execute anything is a decoration |
| A public sandbox you can sign up for | Same reason. Access is granted after an evaluation; there is no anonymous tier to attach a console to |
| Client libraries and SDK reference | The TypeScript SDK is private and issued at onboarding. Documenting a library nobody can install would be documenting a screenshot |
| An MCP server | Not built. The API is plain HTTP with an OpenAPI description, which is enough to generate a client today |
| A policy configuration reference | There is no policy object in the API. Policies are configured with us during onboarding, so there is nothing to reference yet |
| A changelog | We have not shipped a versioned release publicly. A changelog invented after the fact is fiction |
| Case studies and named customers | Inventing them is the specific thing this documentation exists not to do |
| A status page with uptime percentages | We collect availability measurements continuously, but a percentage a vendor computes about itself, from one vantage point, is not evidence |
What is here instead
The parts a stranger can check without an account: the public key set and a verifiable signed verdict, the OpenAPI description, the full error model including the behaviours that surprise people, and the boundaries of the primitive on limits of a signed verdict.
When entries leave this page
An entry is removed when the thing exists and is documented — never by rewording it. If you are evaluating us and one of these gaps is the blocker, say so at contact@saifuro.com: knowing which absence actually costs us an integration is more useful than our own ordering of them.

