Back to Models

GPT Image 2.6 Sunburst APIActive

gpt-image-2.6-sunburst

No description available

By:图片生成Input Type:Output Type:

AI Code With channel availability

The same model is billed by channel discount. Copy a channel code to set your preference.

ChannelCache Hit RateContext
OpenAI 图片 API 渠道
72.0%¥0/ M tokens¥0/ M tokensRead:¥-/ M tokensWrite:¥-/ M tokens200K0.0s

Related Models

More models from 图片生成

Compare models from other providers

GPT Image 2.6 Sunburst API: price, model ID, and how to call it

Call GPT Image 2.6 Sunburst through AI Code With. Use model ID gpt-image-2.6-sunburst with 200K context. list price about $0 / $0 per 1M tokens before channel discounts.

Model IDgpt-image-2.6-sunburst
ProtocolsOpenAI Chat Completions
Context200K
Max output65.54K

Next: Get API key · Image model setup · All model prices · All model prices

cURL example

Set model to gpt-image-2.6-sunburst. The page slug is only the URL, not the API parameter.

curl https://api.aicodewith.ai/v1/chat/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $AICODEWITH_API_KEY" \
  -d '{
    "model": "gpt-image-2.6-sunburst",
    "messages": [
      { "role": "user", "content": "What is the meaning of life?" }
    ]
  }'

FAQ

What is the GPT Image 2.6 Sunburst model ID?

Send model "gpt-image-2.6-sunburst" in the API request. The page path /gpt-image-2.6-sunburst is only the URL, not the model parameter.

How do I call the GPT Image 2.6 Sunburst API?

Use one AI Code With API key against https://api.aicodewith.ai/v1/chat/completions, and set model to gpt-image-2.6-sunburst. Supported protocols: OpenAI Chat Completions. See Image model setup.

How is GPT Image 2.6 Sunburst priced?

GPT Image 2.6 Sunburst is list price about $0 / $0 per 1M tokens before channel discounts. The public page shows available channel discounts; billed usage follows your prepaid balance and the live channel.

How long is the GPT Image 2.6 Sunburst context window?

GPT Image 2.6 Sunburst has about 200K input context and up to 65.54K output tokens. Treat that as capacity, not a reason to fill every request.