The model catalog

The model catalog is the single source of truth for every model the platform supports — across chat, embeddings, images, audio, video, and more. Anything an agent or skill can point at is a catalog entry. This page is a reference for how those entries are shaped.

Anatomy of a catalog entry

Every entry is identified by a globally unique slug of the form <provider>/<model> (with an optional @<variant> suffix), for example:

Slug	Modality
anthropic/claude-opus-4-7	chat
openai/gpt-5	chat
openai/text-embedding-3-large	embedding
openai/gpt-image-1@hd-1024	image_generation
elevenlabs/eleven-turbo-v2-5	text_to_speech
deepgram/nova-3	speech_to_text
runway/gen-4	video_generation
cohere/rerank-3-5	rerank

Alongside the slug, each entry carries a provider, a family, a display name, and a modality — the primary discriminator that drives pricing units and which agents or skills may bind to it.

Modalities

The modality field is one of a fixed set. Each modality prices in its own natural unit:

Modality	Priced per
chat, code_completion	input / output token
embedding	input token
image_generation, image_edit	image (by resolution)
text_to_speech	character
speech_to_text	minute of audio
music_generation, video_generation	second of output
rerank	request

The runtime rejects a modality mismatch at resolve time — a chat skill cannot accidentally invoke an embedding model.

Capabilities

Chat-family entries carry capability flags the runtime and skills can match against:

• context_length and max_completion_tokens
• supports_function_calling, supports_vision, supports_streaming
• supports_json_mode, supports_prompt_caching, supports_batch

Modality-specific metadata (voices for TTS, resolutions for image and video, dimensions for embeddings) lives on the entry too, so a skill can declare "needs vision and tool use" and be matched to a capable model.

How the catalog is maintained

The catalog is refreshed automatically from upstream provider sources and merged with an operator-curated overlay for corrections and native-path tuning. When a provider changes a price, a new priced row is inserted with an effective-from date and the old one is closed — so historical usage keeps its original attribution and past runs stay costed correctly.

Entries also carry a deprecation lifecycle: an EOL'd model can point at a successor, and the runtime substitutes it transparently until you re-pin. A retired model is rejected outright.

Browsing it

See every entry available to your account — with per-model price and this month's spend — at /a/<account>/settings/models. Filter by modality first, then provider, capability, or price.

Where to go next

• Choosing a model to pick and pin one to an agent.
• Model dispatch for how a catalog slug becomes an actual runtime call.