SAW exposes three unauthenticated read-only endpoints for monitoring and orchestration purposes. UseDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/samkit511/SAW---Security-Analyst-Workspace/llms.txt
Use this file to discover all available pages before exploring further.
/health for liveness probes, /warmup for readiness probes, and /latest to inspect the most recently processed incident without sending a new log.
GET /health
Returns{"status": "ok"} as soon as the FastAPI process is accepting connections. No authentication is required. This endpoint is safe to poll at high frequency.
Always
"ok" when the process is alive and the HTTP server is accepting requests.GET /warmup
Returns{"status": "ready"} once the application has finished initializing. No authentication is required. Use this endpoint as a Kubernetes readiness probe or a container health check in Docker Compose.
Always
"ready" when the application layer is initialized and ready to accept triage requests.GET /latest
Returns the full decorated response object of the most recently processed incident. No authentication is required. The response is identical in shape to aPOST /ingest-log or POST /assistant/request success response, making this endpoint useful for dashboards and polling integrations that do not want to re-submit a log.
If no incident has been processed since the server started, the response is an empty object {}.
Human-readable name of the SAW system (
"Multi-Agent Security Operations Assistant").Unique request identifier prefixed with
req_.Unique identifier of the incident record created or updated by this request.
"COMPLETED" if all agents succeeded, "DEGRADED" if one or more agents failed during orchestration.One sentence per agent describing what each agent did.
Metadata block added by the response decorator.
/latest is served from an in-memory store and is reset when the server restarts. It is not persisted to the database.