Decision headers
How every response tells you what the policy did.
| Header | Value |
|---|---|
x-request-id | Unique id, e.g. req_93f1a1c7…. Also in the unrefused body field. |
x-unrefused-policy | Profile and version applied, e.g. eval-harness@v14. |
x-unrefused-input | Input-stage decision code. |
x-unrefused-output | Output-stage decision code. pending on streams (read the final chunk), n/a for embeddings. |
x-unrefused-retention | Always none. |
Decision codes
A code is one or more parts joined by ;:
| Part | Meaning |
|---|---|
pass | Nothing matched and nothing was changed. |
redacted=N | N values were redacted before the text left the gateway. |
flag=a+b | Classifiers a and b matched; the request proceeded. |
block=a | Blocked by classifier a. block=platform:… means the platform baseline. |
note=a | Matched under annotate. |
error=a | Classifier a was unavailable and its fail mode let the request continue. |
Examples: redacted=2, flag=toxicity, redacted=1;flag=toxicity, block=pii.
Spot an error or a gap? Tell us — and quote x-request-id if you have one.