Back to Models

Grok Imagine Image 2.0 APIActive

grok-imagine-image-2.0

No description available

By:xAIInput 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
Grok 官方渠道80% off
88.0%¥0.036/ M tokens¥0.036/ M tokensRead:¥-/ M tokensWrite:¥-/ M tokens200K0.0s

Related Models

More models from xAI

Compare models from other providers

Grok Imagine Image 2.0 API: price, model ID, and how to call it

Call Grok Imagine Image 2.0 through AI Code With. Use model ID grok-imagine-image-2.0 with 200K context. list price about $0.0250 / $0.0250 per 1M tokens before channel discounts.

Model IDgrok-imagine-image-2.0
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 grok-imagine-image-2.0. 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": "grok-imagine-image-2.0",
    "messages": [
      { "role": "user", "content": "What is the meaning of life?" }
    ]
  }'

FAQ

What is the Grok Imagine Image 2.0 model ID?

Send model "grok-imagine-image-2.0" in the API request. The page path /grok-imagine-image-2.0 is only the URL, not the model parameter.

How do I call the Grok Imagine Image 2.0 API?

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

How is Grok Imagine Image 2.0 priced?

Grok Imagine Image 2.0 is list price about $0.0250 / $0.0250 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 Grok Imagine Image 2.0 context window?

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