Models, Manufacturers, and Capabilities

Use the Models page as the current source of truth for available manufacturers, models, capabilities, limits, and public pricing.

Separate the concepts

• Manufacturer: the brand or organization associated with a model and used as the public model namespace.
• Model: the public unit selected in a request.
• Client protocol: the request and response dialect spoken by your SDK; it does not determine which internal provider channel serves the request.
• Provider channel: an internal route managed by the platform and not exposed for client selection.

A model from one manufacturer can be called through a compatible protocol associated with another ecosystem. Protocol compatibility and model ownership are separate dimensions.

Use the full model ID

Public model IDs use the form {manufacturer}/{model}. A short model name is accepted only when it is unique across all enabled models, so use the complete ID in production.

Tasks, modalities, and operations

A model's task determines the workflow, such as text generation, embedding, image processing, or video processing. Input and output modalities describe the data it accepts and produces. Operations and capability labels describe model-specific support such as tool calling, image editing, reference inputs, or video extension.

Do not infer support from the manufacturer name or a similar model. Check the selected model's declared operations, limits, execution modes, and price.

Test before integrating

Use the model page or Playground to verify output quality and available controls. Newly supported manufacturers and models appear in the catalog, so rely on it instead of a static list.