API Reference
Server-side endpoints
These endpoints power the AtlasBurn ingestion and enforcement pipeline. They are normally called by the SDK, the Edge Proxy, and the dashboard — but you can call them directly from custom integrations.
Base URL
https://api.atlasburn.comAuthentication
All endpoints require your organization API key in the AtlasBurn-API-Key header. Keys are prefixed abn_ and verified with HMAC-SHA-256.
POST /api/ingest
Raw telemetry ingestion endpoint. Accepts a single event or a batch.
Request
POST /api/ingest
AtlasBurn-API-Key: abn_xxxxxxxxxxxxxxxxxxxx
Content-Type: application/json
{
"events": [
{
"ts": "2026-05-18T12:34:56.789Z",
"provider": "openai",
"model": "gpt-4o-mini",
"endpoint": "/chat/completions",
"status": 200,
"tokens_in": 142,
"tokens_out": 318,
"cost_usd": 0.000421,
"latency_ms": 612,
"fingerprint": "sha256:b9c1...",
"stream": false
}
]
}Response
{
"accepted": 1,
"rejected": 0,
"guardrail_status": "ok"
}If a guardrail layer triggers as a result of this ingest call, the response will include "guardrail_status": "suspended" and the worker will begin returning 429 within the next request cycle.
POST /api/guardrails/enforce
Pushes or clears Cloudflare KV kill flags based on policy configuration. Used internally by the ingestion server and by the dashboard's Resume button.
Push a kill flag
POST /api/guardrails/enforce
AtlasBurn-API-Key: abn_xxxxxxxxxxxxxxxxxxxx
Content-Type: application/json
{
"org_id": "org_xxx",
"action": "suspend",
"layer": "dumb_loop_detector",
"ttl_seconds": 7200,
"reason": "fingerprint sha256:b9c1... seen 4 times in 60s"
}Clear a kill flag (manual override)
DELETE /api/guardrails/enforce
AtlasBurn-API-Key: abn_xxxxxxxxxxxxxxxxxxxx
Content-Type: application/json
{
"org_id": "org_xxx",
"reason": "manual_resume"
}Response
{
"ok": true,
"kv_key": "guardrail:org_xxx",
"state": "suspended",
"expires_at": "2026-05-18T14:34:56.789Z"
}Next steps
- Autonomous Guardrails — what triggers an enforce call
- Auto-Recovery — TTL semantics and override flow