Models

This is one of the safest read-only endpoints to call first during integration.

GET /v1/models

Overview

Typical use cases

• Fetch the available model list at startup
• Verify that a target model is enabled in the current environment
• Build your own model selector in a dashboard or config UI

Authorizations

Authorization: Bearer sk_yeehoo_your_api_key

Response

A successful response usually returns a model list object.

{
  "object": "list",
  "data": [
    {
      "id": "gpt-image-2",
      "name": "gpt-image-2",
      "region": "all",
      "family": "image",
      "description": "General image generation",
      "capabilities": ["image_generation"],
      "pricing": {"unit": "image", "display": "per image", "credits_text": "use /v1/quote"},
      "schema": {"fields": [{"name": "resolution", "type": "string", "required": false, "default": "1K", "options": ["1K", "2K", "4K"]}]},
      "ui_hints": [],
      "enabled": true
    }
  ]
}

Response fields

Integration notes

• Do not infer capabilities from model names; read family and schema.fields
• There is no public /v1/models/{model}/schema; schema data is embedded in each list item
• For parameter differences across models, see Supported Models and Parameters
• If your frontend shows a dynamic model list, prefer refreshing it instead of hardcoding it