GET /v1/models
Lists every model your API key can access.
Response
Query Parameters
The Models API supports query parameters to filter the list of models returned.mode
Filter models by what they’re used for — a comma-separated list.
Response
output_modalities
Filter models by their output capabilities. Accepts a comma-separated list of modalities.
Examples:
Response
Model Object Schema
Each model in thedata array contains the following fields:
Architecture Object
input_modalities— the types of input the model accepts (text, image, audio, file).output_modalities— the types of output the model can produce.
Capabilities Object
The model’s supported features, when known — things likesupports_vision,
supports_function_calling, supports_reasoning, and, for reasoning models, which
reasoning effort levels they support (supports_none_reasoning_effort,
supports_xhigh_reasoning_effort, etc.). Omitted entirely if no capability data is
available for a model.
Pricing
pricing shows what you actually pay to use the model — already reflecting any
discounts, in USD per token (or per request, for models like rerank).
Fields
All values are USD amounts per token, formatted as strings:
Fields only appear when they’re relevant to a model — for example, image-output models
show
image_output, audio-capable models show audio/audio_output, and text-only
models show neither. For most models, pricing is omitted entirely if pricing isn’t
available.
Video and rerank models
For video generation and rerank models,pricing always appears, with null for any
field that doesn’t apply — since these models are often priced in ways (e.g. per-second
video) that don’t fit the standard per-token fields above.
overrides (long-context pricing)
Some models charge more once a request passes a certain prompt length. When that
applies, overrides lists the higher rates and the token threshold they kick in at:
Example response
capabilities is omitted entirely when
no capability data is available for it, while pricing still appears with null
fields:
GET /models (OpenAI format)
Dropping the v1 prefix returns a lighter, OpenAI-compatible model list — just the
id, object, created, and owned_by fields, matching the shape returned by
OpenAI’s own /models endpoint. Use this if you’re pointing an existing OpenAI SDK
or tool at ZnapAI and just need the standard model list.
Response
