> ## Documentation Index
> Fetch the complete documentation index at: https://docs.linkedcamp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List AI agents

> **Read-only.** It changes nothing.

AI agents configured for this account. CHAT agents reply to prospects in the inbox, CONTENT agents draft LinkedIn posts, and the rest are specialised assistants. Start here when the user asks about automated replies, and show them `agent_get` so they can judge the fit before anything is attached. An agent writes replies; a persona (`persona_list`) decides who qualifies; a knowledge base (`kb_list`) is the material an agent draws on. Attaching one to a campaign is `campaign_update` — and it answers real prospects by itself, so never attach one unasked. Requires the "Agents" permission on the plan.



## OpenAPI

````yaml /api-v2/openapi.json post /agent_list
openapi: 3.1.0
info:
  title: LinkedCamp API
  version: 2.0.0
  description: >-
    Version 2 of the LinkedCamp API. Every endpoint is a POST to `/{endpoint}`
    with its arguments as a JSON object, and returns JSON.
servers:
  - url: https://api.linkedcamp.com/v2
security:
  - ApiKey: []
  - Bearer: []
tags:
  - name: Account
  - name: Notifications
  - name: Reference
  - name: Campaigns
  - name: Campaign audience
  - name: Sequences
  - name: Blocked dates
  - name: Leads
  - name: Lead notes
  - name: Activities
  - name: Tags
  - name: Blacklist
  - name: Conversations
  - name: Messages
  - name: Saved replies
  - name: Templates
  - name: Merge fields
  - name: Personalised images
  - name: LinkedIn accounts
  - name: Email accounts
  - name: AI agents
  - name: Knowledge base
  - name: Personas
  - name: Analytics
  - name: Posts
  - name: Posting schedule
  - name: Tasks
  - name: Appointments
  - name: Reminders
  - name: Automations
paths:
  /agent_list:
    post:
      tags:
        - AI agents
      summary: List AI agents
      description: >-
        **Read-only.** It changes nothing.


        AI agents configured for this account. CHAT agents reply to prospects in
        the inbox, CONTENT agents draft LinkedIn posts, and the rest are
        specialised assistants. Start here when the user asks about automated
        replies, and show them `agent_get` so they can judge the fit before
        anything is attached. An agent writes replies; a persona
        (`persona_list`) decides who qualifies; a knowledge base (`kb_list`) is
        the material an agent draws on. Attaching one to a campaign is
        `campaign_update` — and it answers real prospects by itself, so never
        attach one unasked. Requires the "Agents" permission on the plan.
      operationId: agent_list
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                type:
                  type: string
                  enum:
                    - CHAT
                    - VOICE
                    - CONTENT
                    - CAMPAIGN
                    - REPORTING
                  description: Filter by type.
                keyword:
                  type: string
                  description: Free-text search.
                withStats:
                  type: boolean
                  default: false
                  description: Include conversation and booking counts.
              additionalProperties: false
      responses:
        '200':
          description: >-
            The result, as JSON. Writes answer `{ "ok": true, "message": ...,
            "data": ... }`.
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
        '400':
          description: >-
            The body is not valid JSON, an argument is invalid, or the request
            was refused.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: No API key, or the key was rejected.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: >-
            Your plan, permissions or access tier don't include this, or a
            record belongs to another account.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: A record named in the arguments does not exist.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '422':
          description: >-
            The request was valid but the operation was refused, such as
            launching a campaign that is not ready.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '502':
          description: The service failed or could not be reached. Reads are safe to retry.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '504':
          description: >-
            The operation timed out. A write may still complete; read it back
            before retrying.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Error:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - code
            - message
          properties:
            code:
              type: string
              enum:
                - UNAUTHENTICATED
                - FORBIDDEN
                - PLAN_REQUIRED
                - VALIDATION
                - INVALID_JSON
                - NOT_FOUND
                - METHOD_NOT_ALLOWED
                - UPSTREAM
                - TOOL_ERROR
            message:
              type: string
            hint:
              type: string
              description: What to do about it, when there is something to do.
  securitySchemes:
    ApiKey:
      type: apiKey
      in: header
      name: X-Api-Key
      description: Your LinkedCamp API key.
    Bearer:
      type: http
      scheme: bearer
      description: Your LinkedCamp API key as a bearer token.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.