Home ／ grok-4.5
Claude Code Relay Setup for grok-4.5
The verified model identifier is grok-4.5, and the pricing data lists it under Grok (xAI). The supplied service record does not document a Claude Code version, a Claude Code configuration path, a relay base URL, or an API key format, so those values should be confirmed from the relay operator before you edit a local setup.
Where do you change the base URL and API key in Claude Code?
The exact Claude Code location cannot be stated from the supplied facts. No Claude Code version, settings-file path, supported environment-variable names, or relay endpoint is provided. Treat any page that fills in those details without verification as a configuration guess, not as a reliable setup instruction.
Start by identifying the configuration surface used by your installed Claude Code version, then enter the relay's documented base URL and API key there. Do not use https://api.openlux.ai/api/pricing as the chat endpoint: the supplied source describes that address as the panel's pricing interface, not as a model request endpoint. The relay base URL is Not yet measured, and the key value is intentionally not published here.
What should the Claude Code configuration contain?
At minimum, the setup needs three values to be checked together: the relay base URL, the relay API key, and the model identifier grok-4.5. A field-level worksheet is: base URL = [relay operator's documented base URL]; API key = [your relay API key]; model = grok-4.5. The first two placeholders cannot be replaced from the supplied record.
Keep the model value exactly as grok-4.5. The pricing data records this model with vendor Grok (xAI), type text, input price $2 per 1 million tokens, output price $6 per 1 million tokens, and cache-hit price $0.5 per 1 million tokens before any group multiplier. Those values describe the pricing record only; they do not establish Claude Code configuration syntax or endpoint compatibility.
How can you verify that Claude Code is using grok-4.5?
Verification requires an actual Claude Code request whose selected model is grok-4.5 and whose request reaches the intended relay. The supplied facts do not include a health-check endpoint, a request example, response headers, request IDs, or expected latency, so there is no verified command or success response that can be published as a universal test.
Use a small, non-sensitive prompt and inspect the request and response details exposed by your Claude Code version or relay dashboard. Confirm three points: the request was accepted, the selected model is grok-4.5, and the response came from the relay rather than another provider configuration. Record latency as Not yet measured unless you run and document your own test.
What Claude Code problems can cause an API error?
The most important troubleshooting distinction is whether the failure is local configuration or remote service behavior. A wrong base URL, an empty or expired key, an unsupported authentication header, or a model value that does not match grok-4.5 can all prevent a request before model execution. The supplied record does not define Claude Code's error taxonomy, so these checks should be treated as investigation steps rather than confirmed mappings for a specific error message.
Do not diagnose an API error from the pricing interface. The recorded pricing data was pulled at 2026-08-04T16:16:08Z, but that timestamp does not prove current request availability. The service's rate limit, timeout behavior, retry policy, error body, and availability are Not yet measured in the supplied facts. Preserve the complete error response and request time when escalating the issue.
How do you switch between grok-4.5 and other models in Claude Code?
Model switching should change only the model selection while retaining the verified relay URL and the intended key, unless the relay operator documents separate credentials or groups. grok-4.5 is one listed model, but the supplied table contains only the 150 highest-volume models and states that 302 additional models are not shown. Its omission from a visible list would therefore not prove that a model is unavailable.
Before switching, confirm the exact model identifier exposed by the relay and use that identifier without renaming it. Do not infer compatibility from a model's vendor, type, or listed price. The supplied facts do not document aliases, Claude Code-specific model menus, fallback behavior, per-model routing, or a supported multi-model configuration file, so those details remain Not yet measured.
Still stuck? Full documentation and support are at learn more.
- How do you call the grok-4.5 API?Setup steps and copy-pasteable code
- grok-4.5: direct API or gateway?Point-by-point, including the limitations
- grok-4.5 API — frequently asked questionsWhat people actually ask when integrating
- Where to Buy Grok 4.5 API Access and What It Costs in 2026Buy Grok 4.5 access
- Can You Pay for Grok 4.5 API Without an International Credit Card?Grok 4.5 payment options
- How Does an API Relay Work for grok-4.5?Understand API relay architecture
- Which Model Offers Better API Value Than grok-4.5 in 2026?Compare grok-4.5 API costs
- Can grok-4.5 API Access Get Suspended?Understand suspension and relay risk
- grok-4.5 Free API Access: What Is Confirmed for 2026?Free-tier verification
- How to handle “this organization has been disabled” when calling grok-4.5Fix account-disabled API errors
Get started
Confirm the group multiplier, access endpoint, and grok-4.5 availability in the panel before running a minimal request test
Create an account and generate a key
Official site: OpenLux official site
Last updated 2026-08-05 | Written and maintained by OpenLux.
Latency and pricing figures come from our own measurements. Where they differ from the vendor's site, the vendor's live page wins.