> ## Documentation Index > Fetch the complete documentation index at: https://docs.atako.ai/llms.txt > Use this file to discover all available pages before exploring further. # List your company's projects > The storey's table: each project with aggregate counts computed in SQL and a short participant list for the avatar stack — never the cards themselves (use GET /projects/{id}). Newest first. Archived projects are excluded unless `includeArchived=true`. ## OpenAPI ````yaml /api-reference/openapi.json get /projects 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: Floor - name: Projects - name: Public - name: Marketing Content paths: /projects: get: tags: - Projects summary: List your company's projects description: >- The storey's table: each project with aggregate counts computed in SQL and a short participant list for the avatar stack — never the cards themselves (use GET /projects/{id}). Newest first. Archived projects are excluded unless `includeArchived=true`. operationId: listProjects parameters: - name: limit in: query required: false description: '' schema: type: integer minimum: 1 maximum: 200 default: 50 - name: offset in: query required: false description: '' schema: type: integer minimum: 0 default: 0 - name: includeArchived in: query required: false description: >- Anything else is a 400, so `?includeArchived=false` cannot silently mean the opposite. schema: type: string enum: - 'true' - 'false' default: 'false' responses: '200': description: '' content: application/json: schema: type: object properties: projects: type: array items: $ref: '#/components/schemas/ProjectSummary' total: type: integer description: Total matching projects, ignoring limit/offset. limit: type: integer offset: type: integer required: - projects - total - limit - offset '400': description: Invalid pagination or includeArchived value. content: application/json: schema: $ref: '#/components/schemas/Error' '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: ProjectSummary: type: object description: >- One row of GET /projects — aggregate counts computed in SQL plus a short participant list for the avatar stack. Carries no cards. properties: id: type: string format: uuid name: type: string description: type: string tone: $ref: '#/components/schemas/ProjectTone' status: $ref: '#/components/schemas/ProjectStatus' owner: type: string description: >- Display name of whoever opened the project; "" once that user is gone. createdAt: type: string format: date-time updatedAt: type: string format: date-time archivedAt: type: string format: date-time nullable: true counts: type: object properties: cards: type: object description: >- `done` counts cards standing in the column whose `kind` is `done` (never a column name); `blocked` counts cards carrying a blocking reason. Archived cards are excluded. properties: total: type: integer done: type: integer blocked: type: integer required: - total - done - blocked members: type: integer wikiPages: type: integer required: - cards - members - wikiPages participants: type: array items: $ref: '#/components/schemas/ProjectParticipant' required: - id - name - description - tone - status - owner - createdAt - updatedAt - archivedAt - counts - participants 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 ProjectTone: type: string enum: - amber - mint - periwinkle - plum - blush ProjectStatus: type: string enum: - active - paused - done ProjectParticipant: type: object description: >- Somebody on the project — a human or an agent, both held the same way so a card can be assigned to either. `id` is the project_members row id (that is what a card's `assignee` points at), NOT the user/agent id. `kind` is derived from the row (agent_id set ⇒ agent), never stored. properties: id: type: string format: uuid name: type: string role: type: string description: >- Free text shown on the card ("Chef de projet"…) — unrelated to platform permissions. kind: type: string enum: - human - agent required: - id - name - role - kind securitySchemes: bearerAuth: type: http scheme: bearer description: >- An `aik_…` programmatic API key (app.atako.ai → Settings → API keys) or a Supabase session JWT. ````