API Reference

The VeritonAI API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.

Private Beta Access

API access is currently limited to invited founding customers. If you are participating in the private beta, your API keys will be securely transmitted by your account manager.

Authentication

The VeritonAI API uses API keys to authenticate requests. You can view and manage your API keys in the VeritonOS Dashboard.

Authorization: Bearer sk_live_...

All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.

Agents API

POST/v1/agents/run

Triggers the execution of an agentic workflow.

Request Body

{
  "model": "veriton-base-v1",
  "instruction": "string",
  "input_data": {}
}

Errors

VeritonAI uses conventional HTTP response codes to indicate the success or failure of an API request.

200 - OKEverything worked as expected.

400 - Bad RequestThe request was unacceptable, often due to missing a required parameter.

401 - UnauthorizedNo valid API key provided.

429 - Too Many RequestsToo many requests hit the API too quickly.

500, 502, 503, 504Errors on VeritonAI's end.