Base URL
Authentication
All requests must include your API key in theAuthorization header as a Bearer token:
Endpoints Overview
| Method | Endpoint | Description |
|---|---|---|
| POST | /api/policies/{policyKey}/evaluate/conditions | Evaluate a conditions policy with structured input |
| POST | /api/policies/{policyKey}/evaluate/instructions | Evaluate an instructions policy (prompt + input) |
| POST | /api/policies/{policyKey}/evaluate/guardrails | Evaluate a guardrails policy with text input |
| GET | /api/escalations | List all escalations for your organization |
| GET | /api/escalations/{policyId} | List escalations filtered by policy ID |
| POST | /api/escalations/approve | Approve a pending escalation |
| POST | /api/escalations/decline | Decline a pending escalation |
Policy evaluation responses
The three policy evaluation endpoints (conditions, instructions, guardrails) return the same response shape: an envelope withmeta and result.
- meta —
code(HTTP status),message,errors(array of validation or evaluation messages when present). - result —
violated(boolean),decision(ALLOW, BLOCK, or ESCALATE),reason(optional),key(policy key evaluated).
SDK Reference
For a better developer experience, use our SDK instead of raw API calls. The SDK normalizes the API response to a simple result shape.