Quickstart

1. Get an API key

API keys are created in the dashboard by a signed-in member of your organization. Keys cannot mint keys — creation happens where a person is signed in, never programmatically. The secret is shown once, at creation; store it then.

A key starts with the atk_ prefix and acts as your organization: every action runs against the organization's data and is billed to it.

2. Call the API

Every route lives under /api/v1 on the platform origin. Authenticate by sending the key as a bearer token:

Code
Authorization: Bearer atk_...

3. A first request

List your organization's agents:

Code
curl https://YOUR_PLATFORM_ORIGIN/api/v1/agents \
  -H "Authorization: Bearer $ATTEQ_API_KEY"

A missing or malformed header answers 401 missing bearer token; an unknown or revoked key answers 401 invalid or expired token.

Next

• How it fits together — which few operations a job needs, and in which order. Read it before the reference.
• Authentication — what a key is and what it may do.
• API Reference — every public operation, with schemas.
• For agents — the same surface as MCP tools, and machine-readable docs.