Skip to main content
The ARGUS Runtime Security API lets you analyze prompts and LLM responses against guardrail policies in real time, verify API keys and assets, and record agentic trace events for observability.

​
Base URL

All requests are made to:

​
Versioning

Every endpoint is namespaced under the /sdk/v1 path prefix. The full path for a request is the base URL plus the versioned endpoint path, for example:

​
Authentication

All endpoints require an API key, passed in the X-API-Key request header:
​
X-API-Key
string
required
Your ARGUS API key. A request with a missing key returns 401 with {"error": "API key is missing"}. A request with an invalid or inactive key returns 401 with {"error": "Invalid or inactive API key"}.

​
Request conventions

  • Send request bodies as JSON with Content-Type: application/json.
  • The POST endpoints (analyze/prompt, analyze/response, events/record) take a JSON body.
  • GET endpoints (verify/api-key, verify/asset) take query parameters where applicable.
  • A body that fails schema validation returns 400 with the validation error.

​
Rate limits

Rate limits are enforced per API key, on a fixed window. Exceeding a limit returns 429 with {"error": "Rate limit exceeded"}. The platform /scan endpoints carry no dedicated override and fall under the default limit.

​
SDK API vs. Platform API

The API has two surfaces:
  • SDK API (/sdk/v1/*) — the public surface for direct integrations. Analyze endpoints accept an inline policies array so callers can override the asset’s configured policies per request.
  • Platform API (/scan/*) — the internal endpoints used by the ARGUS platform’s tracing and guardrail system. They apply the asset’s configured policies and do not accept an inline policies array. Use these only if you are integrating with the platform tracing flow; otherwise prefer the SDK API.
Both surfaces share the same X-API-Key authentication and the same verdict-based response shape (request_id, verdict, policies_violated).

​
Endpoints

​
SDK API

​
Platform API

​
Policy semantics

Guardrail policy names, verdicts, and the shape of policies_applied / policies_violated are defined in the SDK reference. See Enumerations for the canonical PolicyName, Verdict, and Action values, and Types for the Policy, AppliedPolicyInfo, and ViolatedPolicyInfo structures. A machine-readable OpenAPI 3.1 contract for these endpoints ships alongside this documentation as api-reference/openapi.json.