Configurable safety rails that inspect prompts and responses for harmful or non-compliant content.
Guardrails are gateway-level inspection layers that run on every request, between your application and the model. A request that fails a check is blocked before it reaches the model.
Custom content guardrails — configure them at Settings → Guardrails (/dashboard/settings/guardrails):
422 guardrail_blocked.These apply on both the chat surface and your API (/v1) traffic.
PII redaction is also active on every request under Algeria Law 18-07 — national IDs, phone numbers, CCP, RIB, and emails are detected and (per your Privacy setting) warned/redacted/blocked. See Sensitive Info Guardrail.
Each guardrail applies its configured action, set at account level in the dashboard:
| Action | Behaviour |
|---|---|
block | Return an error; the model is never called |
redact | Replace matched spans with [REDACTED]; continue normally |
flag | Allow the request and record the match in your audit trail |
Not yet available. Per-key guardrail overrides and a per-request
guardrailsobject in the chat request body are tracked to be built. Today guardrails are configured at account level in Settings → Guardrails; aguardrailsfield in a request is ignored.
Every guardrail trigger is recorded in your account's audit log with the request ID, the rule that fired, the action taken, and a timestamp. Audit logs are retained for 90 days and accessible via the dashboard.