Grok 4.5 API: Endpoint & Pricing
Grok 4.5 is available on LLM.API as an OpenAI-compatible chat endpoint—route xAI quality through one key with transparent token pricing.
What is Grok 4.5?
On LLM.API, Grok 4.5 (grok-4.5) serves as a xAI conversational model for products that need 500K tokens context windows and predictable token pricing. xAI's latest Grok for chat, coding, agentic tools, and lower hallucination risk.
Can you self-host Grok 4.5?
No. We found no public weights for Grok 4.5 on Hugging Face, so there is nothing to download, quantize or serve on your own GPUs: no VRAM budget, no vLLM or GGUF build to plan for. The only way to run it is over an API.
Skip the deploy — use LLM.API as your endpoint
No GPUs, no quantization trade-offs. Same model, OpenAI-compatible, with custom volume discounts on request.
Providers
LLM.API routes Grok 4.5 to the providers below, with discounted effective rates versus list price.
List price by provider
InputOutputProvider list prices; the LLM.API discount applies on top.
| Provider | Pricing | Context | Capabilities |
|---|---|---|---|
| in $2; out $6 per 1M tokens | 500K tokens | vision, tools, streaming, reasoning, JSON, structured |
Prices and availability from the LLMAPI catalogue, updated nightly. Last updated 11 Oct 2026.
Try this model
Test Grok 4.5 right here — free to start.
Suggestions for your first prompt
Code snippet
Call Grok 4.5 through the OpenAI-compatible API — POST /v1/chat/completions.
Switching from OpenAI? Change 2 lines.
- base_url="https://api.openai.com/v1"
- api_key="YOUR_OPENAI_KEY"
+ base_url="https://api.llmapi.ai/v1"
+ api_key="YOUR_LLMAPI_KEY"Everything else stays the same — SDK, message format, tools, streaming. Set model to grok-4.5 and the call runs unchanged.
curl https://api.llmapi.ai/v1/chat/completions \
-H "Authorization: Bearer $LLMAPI_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "grok-4.5",
"messages": [
{"role": "user", "content": "Give me three crisp launch checklist items."}
],
"reasoning_effort": "medium"
}'from openai import OpenAI
client = OpenAI(
api_key="YOUR_LLMAPI_KEY",
base_url="https://api.llmapi.ai/v1",
)
resp = client.chat.completions.create(
model="grok-4.5",
messages=[
{"role": "system", "content": "You are a precise product assistant."},
{"role": "user", "content": "Give me three crisp launch checklist items."},
],
reasoning_effort="medium",
)
print(resp.choices[0].message.content)import OpenAI from "openai";
const client = new OpenAI({
apiKey: process.env.LLMAPI_KEY,
baseURL: "https://api.llmapi.ai/v1",
});
const resp = await client.chat.completions.create({
model: "grok-4.5",
messages: [
{ role: "user", content: "Give me three crisp launch checklist items." },
],
});
console.log(resp.choices[0].message.content);stream = client.chat.completions.create(
model="grok-4.5",
messages=[{"role": "user", "content": "Write a haiku about latency."}],
stream=True,
)
for chunk in stream:
delta = chunk.choices[0].delta.content
if delta:
print(delta, end="", flush=True){
"model": "grok-4.5",
"messages": [
{"role": "system", "content": "You are a precise product assistant."},
{"role": "user", "content": "Give me three crisp launch checklist items."}
],
"reasoning_effort": "medium"
}ENDPOINTS
Supported endpoints & features
Base URL https://api.llmapi.ai/v1 · model ID grok-4.5 · OpenAI-compatible.
POST /v1/chat/completionsChat Completions — supported
| Feature | Status | How to set it |
|---|---|---|
| Function calling (tools) | Supported | tools, tool_choice |
| Parallel tool calls | Not supported | parallel_tool_calls |
| JSON mode | Supported | response_format: {"type": "json_object"} |
| Structured outputs | Supported | response_format: {"type": "json_schema", …} |
| Streaming | Supported | stream: true |
| Vision (image input) | Supported | image_url content parts |
| Web search | Not supported | web_search |
| Reasoning effort | low · medium · high | reasoning_effort: "medium" default medium |
ERRORS
Errors & fallback routing
| Code | What it means | What to do |
|---|---|---|
401 | Missing or invalid API key. | Send Authorization: Bearer YOUR_LLMAPI_KEY and check the key is active. |
429 | Rate limited, or the upstream provider is throttling the request. | Back off and retry with jitter; the gateway also retries the request on another provider where one is available. |
5xx | Upstream provider error or timeout. | Retry; fallback routing sends the retry to the next healthy provider for this model. |
When a provider fails or throttles, the request is routed to the next provider serving this model — the ones listed in the providers table above.
Grok 4.5 in production
What the model is good at.
Conversational UX
Maintains coherent multi-turn assistant behavior for product chat surfaces. Relevant for `grok-4.5` workloads on LLM.API.
Multilingual drafting
Drafts and translates professional content across major business languages. Grounded in the model's chat role rather than generic chat claims.
Tool-ready dialogue
Works well in agent loops that call functions, browsers, or retrieval APIs. Relevant for `grok-4.5` workloads on LLM.API.
Safety-aware replies
Supports product policies with refusals and cautious handling of sensitive topics. Relevant for `grok-4.5` workloads on LLM.API.
Structured outputs
Can produce JSON-friendly or schema-oriented responses when prompted carefully.
What you get when you call Grok 4.5 through LLM.API.
Unified AI Routing
Reach Grok 4.5 and sibling models through one OpenAI-compatible endpoint.
One endpoint, every model.Cost Control
Compare provider price points and keep spend visible as you scale Grok 4.5.
More performance, less spend.Reliability Layer
Practical: Retry and route across configured providers when a single upstream blips.
Never go dark on users.Observability
Practical: Trace prompts, tokens, and errors for Grok 4.5 alongside the rest of your stack.
See every token, everywhere.Drop-in SDKs
Production: Keep using familiar OpenAI client patterns with base URL https://api.llmapi.ai/v1.
Think tasks, not models.Model Breadth
Production: Swap Grok 4.5 for chat, media, or embedding alternatives without rewriting auth.
Scale from 1 to millions.
When to Use — When NOT to Use
Use it if...
- You want OpenAI-compatible chat completions through a single LLM.API key (Grok 4.5)
- You need provider failover options exposed for this model id (Grok 4.5)
- Your prompts benefit from the model's family strengths (reasoning, speed, or cost) (Grok 4.5)
- You need a general-purpose text model for assistants, agents, or content workflows (Grok 4.5)
Avoid if...
- You require on-prem only deployment with no cloud inference
- You need pure embedding, OCR, or media generation instead of chat
- Your use case depends on unpublished proprietary benchmarks not listed here
- You need guaranteed real-time hard latency SLAs without benchmarking the provider
BENCHMARKS
Grok 4.5 benchmark scores
Intelligence index
Scale: 0-100 index points
Output speed
Scale: 0-400 tokens per second
Reference price per 1M tokens
Bars compare input and output list prices for this model.
Higher is better. The median covers every model tracked by Artificial Analysis.
Measured throughput; the full dial is 300 tokens per second.
Provider list prices, before the LLM.API discount.
Independent scores published by Artificial Analysis (source). Reference prices are provider list prices, not LLM.API pricing.
COMMUNITY
What developers say about Grok models
Summarised from publicly published developer and community reviews of this model family. Opinions are the sources’, not LLM.API’s, and may not be specific to Grok 4.5.
- API reviews highlight the very large context window, fast responses, and competitive agentic coding scores.
- Head-to-head write-ups against Gemini Flash focus on hybrid reasoning modes and API latency rather than raw benchmark wins.
- Community sentiment is mixed on consistency between reasoning modes; testers advise pinning a mode per workload.
SOURCES
Frequently Asked Questions
What modalities does Grok 4.5 support?
Grok 4.5 accepts text, image and produces text according to its architecture metadata on LLM.API.
How do I call Grok 4.5 via API?
Send OpenAI-compatible requests to https://api.llmapi.ai/v1 with model "grok-4.5" and your LLM.API key. See the code snippet on this page.
Does Grok 4.5 support streaming?
Yes—at least one listed provider advertises streaming.
What is the context length for Grok 4.5?
Reported context for Grok 4.5 is 500K tokens. Always verify the active provider row if multiple providers are listed.
Can I use tools or structured outputs with Grok 4.5?
Tool and/or structured-output flags appear on one or more providers for this model—confirm in the providers table.
Which providers serve Grok 4.5?
LLM.API currently lists: novita, xai. Availability can vary by region and account.
Where is the canonical page for Grok 4.5?
https://llmapi.ai/models/x-ai-grok-4-5/
How is Grok 4.5 priced on LLM.API?
Listed pricing metadata shows: In $2.00 / 1M tokens · Out $6.00 / 1M tokens. LLM.API may offer discounted effective rates (illustrative ~30% callout vs list when available).. Confirm live rates in the LLM.API dashboard or docs before production budgeting.
What are limitations of Grok 4.5?
Like other API models, Grok 4.5 can be wrong, incomplete, or uneven on edge cases. Validate outputs for high-stakes use. Media/OCR/STT models additionally depend on input quality.
COMPARE
Competitive Models
Grok 4.6
Input$2 / 1MOutput$6 / 1MList price per 1M tokens.
$2 in / $6 out per 1M tokens, 500,000 context — the closest current alternative to Grok 4.5.
GPT-5.2
Input$1.75 / 1MOutput$14 / 1MList price per 1M tokens.
$1.75 in / $14 out per 1M tokens, 400,000 context — the closest current alternative to Grok 4.5.
Qwen 3.8 Max
Input$2 / 1MOutput$6 / 1MList price per 1M tokens.
$2 in / $6 out per 1M tokens, 1,000,000 context — the closest current alternative to Grok 4.5.
Get one key to every model
Swap your API key. Keep your code.