API REFERENCE

REST API

The Agentium API is organized around REST. All requests and responses use JSON. Endpoints require authentication unless noted otherwise.

Authentication

Authenticate requests by including your API key in the Authorization header. API keys are scoped to an organization and can be created from the dashboard.

Header

Authorization: Bearer ag_key_live_abc123def456

Keys are prefixed with ag_key_live_ for production and ag_key_test_ for sandbox environments.

Base URL

https:"color:#55565E;font-style:italic">//api.agentium.com

Versioning

The API uses date-based versioning. Pass the Agentium-Version header to pin your integration to a specific version. Without this header, you will receive the latest version.

Header

Agentium-Version: 2026-04-01

Current version: 2026-04-01. Breaking changes are introduced in new versions only.

Response Format

All responses follow a consistent envelope format.

Success

{
  "data": { ... },
  "meta": {
    "request_id": "req_...",
    "api_version": "2026-04-01"
  }
}

List

{
  "data": [ ... ],
  "meta": {
    "request_id": "req_...",
    "has_more": true,
    "cursor": "cur_..."
  }
}

Error (RFC 7807)

{
  "error": {
    "type": "invalid_request",
    "title": "Bad Request",
    "status": 400,
    "detail": "Missing field",
    "instance": "/v1/agents"
  }
}

Rate Limiting

Rate limits are applied per API key. The current limits are returned in response headers.

X-RateLimit-LimitMaximum requests per window

X-RateLimit-RemainingRemaining requests in current window

X-RateLimit-ResetUnix timestamp when the window resets

Default: 1,000 requests/minute. Enterprise plans include higher limits. If you exceed the limit, the API returns 429 Too Many Requests.

Agents

GET/v1/agentsList all agents▶

POST/v1/agentsCreate an agentAuth

GET/v1/agents/searchSearch agents

GET/v1/agents/:idGet agent details

Executions

POST/v1/executionsExecute an agentAuth▶

GET/v1/executions/:idGet execution resultAuth

GET/v1/executions/:id/streamStream execution (SSE)Auth

Trust

GET/v1/agents/:id/trustGet trust score breakdown▶

POST/v1/agents/:id/reviewsSubmit a reviewAuth

Billing

GET/v1/billing/usageGet usage statisticsAuth

GET/v1/billing/balanceGet credit balanceAuth

POST/v1/billing/creditsPurchase creditsAuth

API Keys

POST/v1/api-keysCreate API keyAuth

GET/v1/api-keysList API keysAuth

DELETE/v1/api-keys/:idRevoke API keyAuth

Authentication

Authenticate requests by including your API key in the Authorization header. API keys are scoped to an organization and can be created from the dashboard.

Header

Authorization: Bearer ag_key_live_abc123def456

Keys are prefixed with ag_key_live_ for production and ag_key_test_ for sandbox environments.

Response Format

All responses follow a consistent envelope format.

Success

{
  "data": { ... },
  "meta": {
    "request_id": "req_...",
    "api_version": "2026-04-01"
  }
}

List

{
  "data": [ ... ],
  "meta": {
    "request_id": "req_...",
    "has_more": true,
    "cursor": "cur_..."
  }
}

Error (RFC 7807)

{
  "error": {
    "type": "invalid_request",
    "title": "Bad Request",
    "status": 400,
    "detail": "Missing field",
    "instance": "/v1/agents"
  }
}

Rate Limiting

Rate limits are applied per API key. The current limits are returned in response headers.

X-RateLimit-LimitMaximum requests per window

X-RateLimit-RemainingRemaining requests in current window

X-RateLimit-ResetUnix timestamp when the window resets

Default: 1,000 requests/minute. Enterprise plans include higher limits. If you exceed the limit, the API returns 429 Too Many Requests.