Get LLM

Fetch a single LLM record from DialNexa’s supported model catalogue, including provider, context window, and supported features.

GET /llms/{id}

Get an LLM

cURL

curl --request GET \
  --url https://api.dialnexa.com/v1/llms/{id} \
  --header 'Authorization: Bearer <token>'

200

{
  "id": "llm_gpt4o",
  "name": "GPT-4o",
  "provider": "openai",
  "description": "Best overall performance for complex conversations.",
  "is_default": false
}

Returns the full record for a single LLM in DialNexa’s supported model catalogue. The response includes the model’s stable id, the upstream provider (for example OpenAI, Anthropic, Google, or a hosted open-weights model), the display name, the context window size, and which conversational features are supported (such as function calling and JSON mode).

When to use this

Use this endpoint when you have an llm_id saved on an agent configuration or in your own database and you need to resolve it into a human-readable label, confirm the model is still active, or check what features the model supports before sending an agent update.

• Agent build UIs typically fetch this when rendering the LLM selection for an already-saved agent so the dropdown can display the correct provider, name, and capability badges.
• Migration tooling that retires a deprecated model uses this to confirm the target model still exists before bulk-updating agents.
• Cost-aware dashboards read the provider and tier from this endpoint to attribute spend per model in internal reports.

If you need the full list of available LLMs, call List LLMs instead. That endpoint is the canonical catalogue and is paginated.

Path parameters

Parameter	Description
id	The LLM ID, for example llm_gpt4o.

Errors

• 404 Not Found is returned when the id does not match a supported LLM. This usually means the model has been deprecated and removed, or the ID was mistyped.
• 401 Unauthorized is returned when the API key is missing, malformed, or revoked. See Authentication.

Request

curl "https://api.dialnexa.com/v1/llms/llm_gpt4o" \
  -H "Authorization: Bearer YOUR_API_KEY"

Response

{
  "id": "llm_gpt4o",
  "name": "GPT-4o",
  "provider": "openai",
  "context_window": 128000,
  "supports_function_calling": true,
  "supports_json_mode": true
}

Related endpoints

• List LLMs: fetch every LLM the platform currently supports.
• Update Agent: change the LLM assigned to an existing agent.
• LLMs and conversation behavior: guidance on choosing an LLM for your use case.

Authorizations

Authorization · string · header · required

Pass your API key as a Bearer token in the Authorization header.

Path Parameters

id · string · required

Response

200

application/json

Success.

id · string

Example:

"llm_gpt4o"

name · string

Example:

"GPT-4o"

provider · string

Example:

"openai"

description · string

Example:

"Best overall performance for complex conversations."

is_default · boolean

Example:

false