Skip to main content
Two methods. The catalogue is read live from the network, so it is cursor-paged like every other listing — and a model published this morning is listed this morning.

list

GET /v1/models. The window filter answers “what could I run in this window?”; search matches free text against the id and the name. Hundreds of models are catalogued, so page it — limit defaults to 20 and caps at 100. Each entry:
string
The model id you pass as model on agents.create.
integer
Native context size in tokens.
integer
The longest reply this model may produce, and what the pre-flight quote is bounded by.
Window[]
The window configurations this model can serve.
("low" | "medium" | "high")[]
The effort levels this model accepts.

retrieve

GET /v1/models/{id}. One entry, for the id you already hold — checking what an agent’s pinned model can do without paging the catalogue to find it. An id this deploy does not serve is a not_found error, so this is also how you validate one before you run it.
vetta/auto is in the catalogue like any other id, and picks the model per request. It serves the immediate window only, and is quoted against a price ceiling then billed at the rate of the model that answered — see Vetta Auto.