> ## Documentation Index > Fetch the complete documentation index at: https://docs.cloudhumans.com/llms.txt > Use this file to discover all available pages before exploring further. # List agents > Every agent (assistant) configured for this tenant: the supervisor(s) that orchestrate and the react specialists they route to. Each row is trimmed for discovery — long prompt fields (system_prompt, tone_of_voice_prompt and similar) are OMITTED — and carries the `assistant_id` getAssistant takes, plus `deployment_role`, which is the value getAssistant's `role` parameter expects (`supervisor`, `react`, or `qna` for knowledge-base Q&A agents). Discover the tenants your credentials cover with listMyClaudiaProjects. ## OpenAPI ````yaml api-reference/specs/claudia/v1.json GET /v1/tenants/{tenant}/assistants openapi: 3.0.1 info: title: Claudia API version: 1.0.0 servers: - url: https://api.cloudhumans.com/claudia description: Production - url: https://api.cloudhumans.com/claudia/staging description: Staging security: - bearerAuth: [] tags: - name: MCP Servers description: >- The MCP servers your agents can call tools on. Registering one here is what makes its tools selectable in an agent; the credentials it needs are stored encrypted and never read back. - name: Knowledge Base Content description: Read, search and edit the content that answers your customers. - name: Content Quality description: Rewrites proposed for content that is answering your customers badly. - name: Playground description: >- Talk to one of your agents as if you were a customer, without touching a real conversation. - name: Project Settings description: >- Read and change how a ClaudIA project behaves — the settings screens of the ClaudIA app, as an API. - name: Content Improvements description: Answers Claudia proposes for questions your content does not cover yet. - name: Knowledge Bases description: The knowledge bases your account can manage. - name: Content Sources description: The sites Claudia crawls to keep a knowledge base in sync. - name: Agents description: >- The AI agents (assistants) configured for your tenant: the orchestrator (supervisor) and its specialists (react). Reads answer the same passthrough shape the platform stores; creates land as DRAFTS a human reviews and publishes in the app. - name: Agent Tools description: >- The tool catalog your agents can be given, aggregated across every MCP server registered for the tenant. This is the same catalog an assistant's mcp_servers[].tools whitelist is validated against. - name: Conversations description: >- Read access to a conversation's lean investigation summary — messages, status and resolution — and the execution trace behind one of its processed messages, without the internal processing state the hub UI's full read carries. paths: /v1/tenants/{tenant}/assistants: get: tags: - Agents summary: List agents description: >- Every agent (assistant) configured for this tenant: the supervisor(s) that orchestrate and the react specialists they route to. Each row is trimmed for discovery — long prompt fields (system_prompt, tone_of_voice_prompt and similar) are OMITTED — and carries the `assistant_id` getAssistant takes, plus `deployment_role`, which is the value getAssistant's `role` parameter expects (`supervisor`, `react`, or `qna` for knowledge-base Q&A agents). Discover the tenants your credentials cover with listMyClaudiaProjects. operationId: listAssistants parameters: - name: tenant in: path description: >- Tenant whose agents you are managing. Discover the tenants your credentials cover with `listMyClaudiaProjects`. A tenant your credentials do not cover is indistinguishable from one that does not exist. required: true schema: type: string - name: project in: query description: >- Project name to narrow the listing to. Optional: without it the answer covers every project your credentials reach on this tenant. Project names are globally unique; discover yours with `listMyClaudiaProjects`. required: false schema: type: string responses: '200': description: >- The tenant's agents, one trimmed row each. Free-form objects: the platform stores the agent configuration as a passthrough, so read the keys rather than assuming a shape. content: application/json: schema: type: array items: type: object additionalProperties: true description: >- Free-form object: the agent's stored configuration, in whatever shape the live config schema for its deployment accepts. Read the keys you need; do not assume a fixed set. '400': description: The request could not be answered as written. content: application/json: schema: $ref: '#/components/schemas/Error' '401': description: Missing, expired or invalid credentials. '403': description: The credentials hold no account allowed to manage this content. content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: >- No such resource, or none these credentials can reach — the two are deliberately indistinguishable. content: application/json: schema: $ref: '#/components/schemas/Error' '429': description: Rate limit applied by the API gateway. Back off and retry. components: schemas: Error: required: - error type: object properties: error: type: string description: What went wrong. example: 'Forbidden: token holds no claim for the requested account' description: Something the caller needs to fix. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT ````