API overview

Base URL

All API requests are made to:

https://api.veto.tools

Every endpoint is prefixed with /v1/. For example:

https://api.veto.tools/v1/agents

Include your API key as a Bearer token in the Authorization header on every request:

Authorization: Bearer veto_<your-key>

API keys are prefixed with veto_. You can create and manage keys via the API Keys endpoints or the Veto dashboard.

All request bodies must be JSON. Set the Content-Type header accordingly:

Content-Type: application/json

The API allows 600 requests per minute per API key. Every response includes the following headers:

Header	Description
`X-RateLimit-Limit`	Maximum requests allowed per minute
`X-RateLimit-Remaining`	Requests remaining in the current window

When you exceed the limit, the API returns 429 Too Many Requests with a Retry-After header indicating how many seconds to wait before retrying.

curl https://api.veto.tools/v1/agents \
  -H "Authorization: Bearer veto_..."

List endpoints return a paginated envelope:

{
  "data": [...],
  "pagination": {
    "limit": 50,
    "offset": 0,
    "count": 10,
    "total": 42
  }
}

Field	Description
`data`	Array of results for the current page
`pagination.limit`	Maximum results requested
`pagination.offset`	Number of results skipped
`pagination.count`	Number of results in this page
`pagination.total`	Total number of matching results across all pages

Use limit and offset query parameters to paginate through results.

Errors follow a consistent shape:

{
  "error": {
    "code": "AGENT_NOT_FOUND",
    "message": "Agent not found in this workspace"
  }
}

See the Errors page for a full list of error codes.

Code	Meaning
`200`	Success
`201`	Resource created
`204`	Success, no content (e.g. after a delete)
`400`	Bad request — validation error
`401`	Unauthorized — missing or invalid API key
`403`	Forbidden — valid key, insufficient scope
`404`	Not found
`429`	Rate limit exceeded
`500`	Internal server error