Skip to main content
The Models endpoint lists the models your organization can actually use, in the shape OpenAI clients expect from client.models.list(). Its purpose is narrow and worth stating: it exists so a tool that speaks the OpenAI format — n8n, the OpenAI SDKs, anything pointed at a custom base URL — can populate its model list instead of showing an error where that list should be.
Every model this endpoint returns is one your next request can actually use. It is the intersection of three things: the model catalogue, the models your deployment holds credentials and a route for, and the per-organization allowlist an administrator may have set. A model missing from the list is missing for one of those reasons.

Endpoint

Authentication:
The key’s assistant scope does not narrow this list. A scope says which documents a key answers from, and models are not assistants — see Authentication.

Response

string
The model ID. Pass this as model to Chat Completions or Chat.
string
The vendor behind the model — openai, google, anthropic or mistral — rather than ragen, so the value tells you something you did not already know.
integer
Always 0. The field is required by the OpenAI Model type and Ragen does not record model publication dates. A constant borrowed from OpenAI’s own response would look like a date and be wrong; 0 is visibly not one.

Examples

Retrieve one model

GET /v1/models/{id} returns a single model object, or 404 if the model does not exist or is not one your organization is allowed to use. The two cases answer the same way on purpose: an allowlist is another tier’s configuration, and distinguishing them would confirm which model IDs are real.

Errors

An empty list

If data comes back empty, an administrator has restricted your organization to models this deployment cannot serve. That is a configuration answer rather than an error, which is why it is an empty list and not a failure — check the organization’s allowed models against the instance’s configured providers.