Prefer the SDK endpoint
POST /sdk/v1/analyze/prompt
for direct integrations. The /scan endpoints are used by the platform tracing layer and,
unlike the SDK endpoint, do not accept an inline policies array — only the asset’s
configured policies are applied.Authentication
Your ARGUS API key.
Request body
Identifier of the asset whose configured policies should be applied.
Container for the content to analyze.
Optional session identifier used to group related interactions.
Optional end-user identifier.
Optional free-form metadata attached to the scan record.
Whether to persist this scan. Defaults to
true when omitted.Example request
Response
Internal scan event identifier for this request.
The definitive outcome of the scan. One of
passed, flagged, or blocked.Policies that found a violation. Empty when the verdict is
passed.Example response — 200 OK
Errors
| Code | Reason |
|---|---|
| 400 | Body failed validation, or scan_data.prompt was missing/empty. |
| 401 | X-API-Key header missing, or the key is invalid/inactive. |
| 429 | Rate limit exceeded. |

