Skip to main content
List the agents shared with this API key for invocation. The response does not include every agent in the workspace.
Disabled agents are included with disabled: true, but chat completions reject them with 403 and the code ASSISTANT_DISABLED until they are re-enabled.

Before You Start

  • API key scope: Requires the Read Agents scope, or the legacy Agent API (full access) scope.
  • Legacy Assistants API: This is the new Agents API with native Vercel AI SDK compatibility. If you’re using the legacy Assistants API, see the migration guide.

Base URL

Dedicated deploymentsReplace api.langdock.com with <your-deployment-url>/api/public in all requests.

Parameters

Examples

First page

Validation Rules

The API enforces the following validation rules:
  • API key access: The list contains only agents shared with this API key for invocation
  • Workspace match: Agents must belong to the same workspace as your API key
  • Omitted agents: Deleted and archived agents are left out. Projects are not included. Disabled agents stay in the list with disabled set to true. You cannot chat with them until they are re-enabled
Agents are ordered by creation time, newest first. Name, description, emoji, model, and input type come from the latest published version. If the agent has never been published, those fields come from the draft. When the agent uses Auto mode, model is auto. Each item includes fewer fields than Get agent details. owner is the current owner when that user still has an active membership in the workspace. If more than one owner remains, this is the most recently granted owner who is still an active member. It is null when no remaining owner is an active member. nextCursor is included only when another page exists. Send it as cursor to fetch the next page. A well-formed UUID cursor that does not match an agent returns 200 with an empty agents array.

Response Format

Success Response (200 OK)

Error Handling

Langdock intentionally blocks browser-origin requests to protect your API key and ensure your applications remain secure. For more information, please see our guide on API Key Best Practices.