API reference

Errors

Errors use the vendor's own JSON shape: OpenAI-style on OpenAI endpoints, Anthropic-style on /v1/messages. Every message ends with the request ID.

StatusCodeMeaning
400bad_requestThe request body is malformed.
401missing_api_key · invalid_api_key · expired_api_keyNo key, a revoked key or an expired key.
402billing_required · tenant_suspendedThe organisation can't send traffic yet.
403policy_denied (or the rule's code)Policy blocked the request. The reason names the rule.
403held_for_reviewWaiting for a human reviewer under Reviews.
403attachments_blocked · guard_model_blockedFiles aren't allowed, or a guard model refused the content.
429budget_exceeded · plan_limit_reachedA workload budget or the plan's monthly requests were used up.
501not_governedThe endpoint can't be inspected, so it isn't served.
502upstream_unavailable · served_model_mismatchNo allowed provider answered, or one served a model policy didn't allow.

Policy refusals in detail

CodeWhy
data_blockedThe request contained data the profile blocks, such as card numbers or secrets.
prompt_injectionThe message looked like an attempt to override instructions.
denied_topicThe message mentions a topic the profile blocks.
prompt_too_largeThe message is bigger than the profile allows.
output_guard_blockedThe safety model judged the answer unsafe, so it was withheld.

Example

403 response (OpenAI format)
{
  "error": {
    "message": "Card details are not allowed by this profile (request 7f3c…)",
    "type": "governance_error",
    "code": "data_blocked"
  }
}

Look the request ID up in Requests to see the full decision trace. See Why was a request blocked? for what to do about each one.