Models

There is no fixed list of models. The catalogue is read from the inference network and cached briefly, so a model published this morning is runnable this morning. Search it here; pass what you find as model on an agent or a session, or as model to the model proxy.

The model object

string

Always model.

string

The model’s id. This is what model takes on an agent, a session and the proxy.

integer

Maximum context length in tokens, as the provider that will serve it publishes it.

integer

The longest reply this model may produce. It is also the output half of the pre-flight quote, so a model with a large allowance reserves more against your balance for the same prompt.

string[]

Which completion windows this model can run in. immediate is always present; priority and loose appear only for pool-hosted models.

string[]

Effort levels the model accepts, from what it publishes. Empty when it accepts none.

No price is published here, the same line GET /v1/media/models draws. What a call costs depends on the window it runs in and on which of the five token tiers its usage lands in; a single figure on this reply would be a guess. See the model router for how a call is metered, and Pricing.

List the catalogue

GET /v1/models — any valid key; no scope.

string

immediate, priority or loose. Narrows the list to models that window can actually serve — the same derivation the router refuses on, so a model listed for a window is never refused for it.

string

Free text, matched against a model’s id and name. Omit it to list them all.

number

Page size, 1–100. Defaults to 20.

string

The next_cursor of the previous page. Opaque — it is not a row id.

The catalogue runs to several hundred entries, so this reply is paged (Pagination). Nothing should assume one call returns the whole catalogue.

curl -fsSL "https://api.vetta.sh/v1/models?search=glm&limit=2" \
  -H "authorization: Bearer sk_live_..."

const page = await vetta.models.list({ search: "glm", limit: 2 });

vetta models list --search glm --limit 2

{
  "object": "list",
  "data": [
    {
      "object": "model",
      "id": "zai-org/GLM-5.2-FP8",
      "context_window": 1048576,
      "max_output_tokens": 32768,
      "supported_windows": ["immediate", "priority", "loose"],
      "efforts": ["high"]
    }
  ],
  "has_more": true,
  "next_cursor": "2"
}

Ordering is cheapest published input rate first, then by id, so a page boundary is stable within one read.

Retrieve one model

GET /v1/models/{id} — any valid key; no scope.

A model id contains a /, so it must be percent-encoded in the path: anthropic/claude-sonnet-5 becomes anthropic%2Fclaude-sonnet-5.

Use this when you already hold an id — the model an agent is set to, say — and want to know what it can do before you spend on it. It answers on the ids this route lists; a model the catalogue republishes under a different spelling is resolved for billing but is not itself an id you can retrieve.

curl -fsSL "https://api.vetta.sh/v1/models/anthropic%2Fclaude-sonnet-5" \
  -H "authorization: Bearer sk_live_..."

const model = await vetta.models.retrieve("anthropic/claude-sonnet-5");
console.log(model.supported_windows); // ["immediate"]

vetta models get anthropic/claude-sonnet-5

{
  "object": "model",
  "id": "anthropic/claude-sonnet-5",
  "context_window": 1000000,
  "max_output_tokens": 32768,
  "supported_windows": ["immediate"],
  "efforts": ["low", "medium", "high"]
}

Vetta Auto

vetta/auto is in the catalogue like any other id, and it picks the model per request. It serves immediate only. Because it publishes no rate card of its own, it is quoted against a price ceiling that is enforced upstream — a call that no model can serve within your budget is refused before it runs, never served at a higher price. See the model router.

Errors

Status	Code	When
400	`validation_failed`	`window` is not one of `immediate\|priority\|loose`.
404	`not_found`	No model with that id — including an id this deploy cannot serve.
501	`feature_not_configured`	This deploy has no inference network configured. An empty list would say “the network publishes no models”, which is a different fact.

A transient failure to reach the network answers 500 rather than a stale or empty catalogue. The failed read is not cached, so an immediate retry is the right response to one.

Next: the model router

How a call is routed, what the completion window changes, and how tokens are metered.

Introduction

Core resources

Platform

Identity

The model object

List the catalogue

Retrieve one model

Vetta Auto

Errors

Next: the model router

​The model object

​List the catalogue

​Retrieve one model

​Vetta Auto

​Errors

Next: the model router

The model object

List the catalogue

Retrieve one model

Vetta Auto

Errors