Explain an anomaly

get

https://api.doit.com/anomalies/v1/{id}/explanation

Returns a likely-cause explanation for the specified anomaly, alongside the deterministic facts and evidence references it was generated from. The explanation itself is AI-generated; it is always returned separately from the deterministic facts, and is marked as such in the explanation object. Generation is ephemeral: no conversation is persisted on your behalf.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Responses

200OK - Anomaly explanation returned.

400Bad Request - The server cannot process the request, often due to a malformed request.

401Unauthorized - Invalid API key.

403Forbidden - The client is not authorized to perform the request.

404Not Found - The requested resource does not exist.

429Too Many Requests.

500Internal Server Error - Something went wrong with the DoiT API server.

503Service Unavailable — minting the ephemeral console-iam token or calling Ava failed. This is a dependency-availability failure, not a client error: retry after the interval indicated by the Retry-After header.