> ## Documentation Index > Fetch the complete documentation index at: https://docs.aiybiz.com/llms.txt > Use this file to discover all available pages before exploring further. # Live-activity feed history ## OpenAPI ````yaml /api-reference/openapi.json get /agents/{agentId}/activity openapi: 3.1.0 info: title: Atako API version: 0.1.0 description: >- The Atako customer API — manage AI agents, their files, integrations, billing, and your company/team, programmatically. ## Authentication Every non-public endpoint takes a Bearer token that is either: - a **programmatic API key** (`aik_…`) — create one at [app.atako.ai](https://app.atako.ai) → Settings → API keys (company-admin only), or - a **Supabase session JWT** — what the web app itself sends; not practical to obtain outside a browser session. ```bash curl https://api.atako.ai/agents -H "Authorization: Bearer aik_..." ``` An API key acts as its owning user, with all of that user's permissions — there is no separate key scope in this release. ## Other Atako HTTP surfaces (not covered by this spec) - **Atako MCP server** — `POST /mcp` (auth: same Bearer token as above) exposes a read-only Model Context Protocol tool catalogue for AI clients (Claude Code, Claude Desktop, Cursor, ChatGPT). See [docs.atako.ai/developers/mcp/overview](https://docs.atako.ai/developers/mcp/overview). - **Content API** (`cak_…` key, `/content/*`) — a separate, more restricted key type for headless CMS-style access to blog/news/use-case content. Not documented here. ## Errors Errors use a JSON envelope: `{ "error": string, "code"?: string }`. `error` is either a short human-readable message or a SCREAMING_SNAKE_CASE code, depending on the route — treat it as an opaque string to match against, not a stable enum across the whole API. ## Rate limits Authenticated routes: 6000 requests/min per user (`authRateLimit`). Public GET routes: 60/min per IP. A handful of sensitive public POST routes (newsletter signup, email-exists, invitation preview) are limited to 10 requests / 15 min per IP. ## Pagination List endpoints use either simple `limit`/`offset` query params (marketing content — a plain JSON array response, capped at the documented max) or `page`/`limit` (credit transactions). Neither returns a total count today; fetch until a page comes back shorter than `limit`. servers: - url: https://api.atako.ai description: Production security: [] tags: - name: Agents - name: Messages - name: Activity - name: Agent Options - name: API Keys - name: Files - name: Cron Jobs - name: Sub-Agents - name: Interagent Messages - name: Integrations - name: Subscriptions - name: Users - name: Company - name: Teams - name: Public - name: Marketing Content paths: /agents/{agentId}/activity: get: tags: - Activity summary: Live-activity feed history operationId: listActivity parameters: - name: agentId in: path required: true description: Agent id schema: type: string - name: limit in: query required: false description: Max 100. schema: type: integer minimum: 1 maximum: 100 default: 50 - name: before in: query required: false description: Newest-first page cursor. schema: type: string format: date-time - name: after in: query required: false description: Oldest-first, SSE-resume mode. schema: type: string format: date-time responses: '200': description: >- Chat-origin events are scoped to the caller's own conversation; cron/subagent/system/integration events are agent-wide. content: application/json: schema: type: object properties: events: type: array items: $ref: '#/components/schemas/ActivityEvent' required: - events '401': description: Missing, malformed, or invalid bearer token / API key. content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: Not found, or the caller is not authorized to access this resource. content: application/json: schema: $ref: '#/components/schemas/Error' security: - bearerAuth: [] components: schemas: ActivityEvent: type: object description: One entry of the live-activity feed (GET /agents/{agentId}/activity). properties: id: type: string format: uuid agentId: type: string format: uuid eventId: type: string seq: type: number ts: type: string format: date-time origin: type: object description: >- Discriminated on `kind`: 'chat' | 'cron' | 'subagent' | 'system' | 'email' | 'webhook' | 'interagent', each with kind-specific extra fields (conversationKey, cronJobId, subAgentId, threadId, endpointId, contextId, …). properties: kind: type: string enum: - chat - cron - subagent - system - email - webhook - interagent required: - kind additionalProperties: true turnId: type: string type: type: string enum: - turn.started - turn.finished - thinking.step - tool.started - tool.finished - plan.updated - subagent.started - subagent.finished - integration.call - llm_call category: type: string enum: - web - files - memory - code - integration - planning - delegation - llm - other labelKey: type: string labelParams: type: object additionalProperties: type: string status: type: string enum: - running - ok - error durationMs: type: number detail: type: object description: >- Event-type-specific extra data (tool name/args/result previews, token counts, todos, integration call info, error message, …). additionalProperties: true required: - id - agentId - eventId - seq - ts - type - labelKey Error: type: object description: >- Atako's standard error envelope. `error` is either a short human-readable message or a SCREAMING_SNAKE_CASE code (routes are inconsistent about which — treat it as an opaque string and match on it exactly if you need to branch on error type). Some routes add extra fields alongside `error` (see the operation's own error responses). properties: error: type: string code: type: string description: >- Present on some routes; a stable machine-readable code duplicating or refining `error`. required: - error additionalProperties: true securitySchemes: bearerAuth: type: http scheme: bearer description: >- An `aik_…` programmatic API key (app.atako.ai → Settings → API keys) or a Supabase session JWT. ````