Docs/LLM
Grok 4.6
500K contextPrompt cachingThinking
POST
https://api.sozdai.ai/v1/chat/completions#Pricing Summary
#Example request
Execute completions using standard OpenAI SDK formats by pointing base endpoints here.
bash
curl https://api.sozdai.ai/v1/chat/completions \
-H "Authorization: Bearer $CORRY_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "grok-4.6",
"messages": [{"role": "user", "content": "Hello"}]
}'#Response example
A standard OpenAI-compatible chat completion object. The model field is normalized to the name you requested.
json
{
"id": "chatcmpl-abc123",
"object": "chat.completion",
"model": "grok-4.6",
"choices": [
{
"index": 0,
"message": { "role": "assistant", "content": "Hello! How can I help you today?" },
"finish_reason": "stop"
}
],
"usage": { "prompt_tokens": 12, "completion_tokens": 9, "total_tokens": 21, "cost": 0.000234, "currency": "USD" }
}Cost field
usage.cost is the amount charged for this call (in USD); in streaming it arrives on the final chunk that carries usage. OpenAI SDKs ignore this extra field.
#Prompt caching
This model uses automatic (implicit) caching — repeated prompt prefixes are cached upstream automatically and billed at a lower rate, with no parameters needed (no cache_control). Keep long, stable context (system prompt, tools) at the start of your messages to get hits.
Automatic — nothing to do
Cache hits show up in the returned usage (cached tokens) and your cost drops automatically.
#Thinking
For models that support it, add reasoning_effort (low / medium / high). The thinking is returned in the response's reasoning_content field; thinking tokens are billed at the output rate.
json
{
"model": "grok-4.6",
"max_tokens": 2048,
"reasoning_effort": "high",
"messages": [{ "role": "user", "content": "your question" }]
}
