Models for Agent API

Retrieve the list of models and their ids, available for use with the Agent API. This endpoint is useful when you want to see which models you can use when creating a temporary agent.

Before You Start

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

https://api.langdock.com/agent/v1/models

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

Example Request

const axios = require("axios");

async function getAvailableModels() {
  try {
    const response = await axios.get("https://api.langdock.com/agent/v1/models", {
      headers: {
        Authorization: "Bearer YOUR_API_KEY",
      },
    });

    console.log("Available models:", response.data.data);
  } catch (error) {
    console.error("Error fetching models:", error);
  }
}

Response Format

The API returns a list of available models in the following format:

Response Fields

string

Always ‘list’, indicating the top-level JSON object type.

array<Model>

Array containing available model objects.

Model object fields

string

Value to send as model on create, update, and completions. When the deployment name maps to one accessible row, id is that name (for example gpt-5). When several rows share the name, id is that row’s model UUID.

string

Deployment name for the row. Present on every row.

string

Always ‘model’, indicating the object type.

integer

Unix timestamp (ms) when the model was created.

string

Region where the model is available (e.g., “eu”, “us”, “global”).

boolean

Whether this model supports extended thinking mode.

Example response

{
  "object": "list",
  "data": [
    {
      "id": "gpt-5",
      "name": "gpt-5",
      "object": "model",
      "created": 1686935735000,
      "region": "eu",
      "supportsExtendedThinking": false
    }
    // …other models
  ]
}

Error Handling

try {
  const response = await axios.get("https://api.langdock.com/agent/v1/models", {
    headers: {
      Authorization: "Bearer YOUR_API_KEY",
    },
  });
} catch (error) {
  if (error.response) {
    switch (error.response.status) {
      case 400:
        console.error("Invalid request parameters");
        break;
      case 401:
        console.error("Invalid API key");
        break;
      case 500:
        console.error("Internal server error");
        break;
    }
  }
}

Send id in the model field when you create a temporary agent. Completions rejects a deployment name that maps to more than one accessible row. Unique names and existing Anthropic aliases still work.

const response = await axios.post("https://api.langdock.com/agent/v1/chat/completions", {
  agent: {
    name: "Custom Agent",
    instructions: "You are a helpful agent",
    model: "gpt-5", // Specify the model ID here
  },
  messages: [
    { id: "msg_1", role: "user", parts: [{ type: "text", text: "Hello!" }] },
  ],
});

curl https://api.langdock.com/agent/v1/chat/completions \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "agent": {
      "name": "Custom Agent",
      "instructions": "You are a helpful agent",
      "model": "gpt-5"
    },
    "messages": [
      { "id": "msg_1", "role": "user", "parts": [{ "type": "text", "text": "Hello!" }] }
    ]
  }'

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.

Overview

Completion API

Embedding API

Agents API

Integrations API

Skills API

Knowledge Folder API

Prompt Library API

Usage Export API

Workflow API

Scheduled Tasks API

User Management API

Billing API

Audit Logs API

Governance API

Compliance API

Models for Agent API

Before You Start

Base URL

Example Request

Response Format

Response Fields

Error Handling

​Before You Start

​Base URL

​Example Request

​Response Format

​Response Fields

​Error Handling

Before You Start

Base URL

Example Request

Response Format

Response Fields

Error Handling