Grok 4.5 EU Release Date and Live Status

Grok 4.5 EU release date is now July 17, 2026, for API console access, according to xAI's official release notes. For EU teams, the next question is not whether Grok 4.5 has arrived, but whether their exact API, Cursor, Office add-in, or gateway workflow is ready for production use.

Key Takeaways:

• Grok 4.5 is now available in the API console for EU users, according to xAI's July 17, 2026 release note.
• EU API console access is open, but Cursor, Office add-ins, and gateways still need separate account-level checks.
• xAI's developer page lists Grok 4.5 API usage, pricing, tools, and supported surfaces with no EU restriction attached, and Cursor's community update says Grok 4.5 is now available in the EU.
• Cursor, Office add-ins, and gateways should still be verified inside the exact account, tenant, or provider workflow before production use.

Hi guys, I'm Vera. I would treat this like a live operations tracker, not a launch recap. I have seen teams lose time because one person could access a new model in an editor while another could not see it in the API console. For a team rollout, "available" only counts when the exact channel your workflow uses is working, priced, logged, and approved.

Short Answer: Grok 4.5 EU Status

As of July 29, 2026, the short answer is no longer mixed for the xAI API console: xAI's release notes say Grok 4.5 became available in the API console for EU users on July 17, 2026. The remaining work is channel verification, not waiting for EU API console access.

xAI's Grok 4.5 developer page presents the model as available through the xAI API console, Grok Build, Cursor, Office add-ins, and model gateways, with the model aimed at coding, agentic tasks, and knowledge work.

The channel-level reality is now more specific. xAI's release notes state that Grok 4.5 became available in the API console for EU users on July 17, 2026. Cursor also has a staff update saying Grok 4.5 is now available in the EU. Office add-ins and gateways still need separate verification inside the actual tenant, marketplace, or gateway account.

So the safest live status is: Grok 4.5 is available to EU users in the xAI API console, while Cursor, Office add-ins, and gateways should still be checked in the exact account, tenant, or provider channel before production use.

Live Availability by Channel

The useful tracker is not "Can someone somewhere use Grok 4.5?" The useful tracker is "Can our team use Grok 4.5 in the channel our workflow depends on?"

API console

Status: available for EU users, based on xAI's July 17 release note.

The xAI release notes state that Grok 4.5 is now available in the API console for EU users. The Grok 4.5 developer page lists grok-4.5 as the model name and describes API use through Responses API and Chat Completions, with function calling, web search, X search, and code execution.

The same release notes carry the commercial detail a migration actually needs. Grok 4.5 is priced at $2 per million input tokens and $6 per million output tokens, with configurable reasoning effort (low, medium, or high, defaulting to high). Requests whose prompt reaches 200K tokens are billed at long-context rates of $4 and $12 per million, and that higher rate applies to every token in the request, not just the tokens past the threshold. Budget from the tier your prompts actually land in rather than the headline number.

For a team, the question now shifts from "Is EU API console access open?" to "Is our exact account ready for migration?" Before switching production apps, internal tools, evaluation scripts, or gateways, confirm the model appears in the console, the API key can call it, pricing is understood, logs are available, and regional or data-use policies are approved. If the model is still missing from your console or editor after July 17, that is an account, tier, or region question rather than a rollout question, and our Grok 4.5 region and access troubleshooting guide walks through where to look.

Cursor

Status: available in the EU, based on Cursor's July 16 community update.

Cursor's release discussion says Grok 4.5 is now available in the EU. That makes Cursor another positive channel signal, alongside xAI's July 17 API console update.

Still, EU teams should check whether the model appears in each user's model picker, whether plan limits apply, whether Cursor has extended or ended the promotional pricing that was posted through July 21, and whether company policy allows the model for customer or proprietary code. "Available in Cursor" does not automatically approve it for regulated repositories.

Office add-ins

Status: announced as part of Grok 4.5's Office work story, but tenant-level EU availability should be verified.

The Grok 4.5 developer page lists Office add-ins as a supported surface, with Grok 4.5 as the default model in Word, PowerPoint, and Excel add-ins. The Word product page describes a Microsoft 365 add-in that can draft, restructure, and tighten wording inside Word.

For EU teams, the practical check is Microsoft 365 tenant availability, admin deployment policy, regional marketplace access, and which Grok model the add-in actually uses after sign-in. An add-in can exist while a specific model, tenant, or account tier remains delayed. We cover what the PowerPoint add-in actually does, and where it stops short, in the Grok 4.5 PowerPoint plugin walkthrough.

Gateways

Status: listed by xAI and visible through at least some gateway providers, but EU routing depends on the gateway.

The xAI Grok 4.5 page references gateway availability, including providers such as OpenRouter, Vercel, Cloudflare, Snowflake, and Databricks Mosaic. Vercel also announced Grok 4.5 on AI Gateway, with the model slug xai/grok-4.5.

Gateways are useful for fallback, usage tracking, and routing rules, but they are not a shortcut around governance. Check the gateway model list, EU routing mode, provider terms, data retention options, and whether the request still routes to a non-EU provider region.

Official Timeline and Update Log

July 8, 2026: xAI release notes list Grok 4.5 as available on the xAI API, with configurable reasoning effort.

July 16, 2026: Cursor community staff posts that Grok 4.5 is now available in the EU.

July 17, 2026: xAI release notes state that Grok 4.5 is now available in the API console for EU users.

July 17, 2026: The Grok 4.5 developer page is updated with the model name grok-4.5, API examples, pricing, supported tools, and where the model runs.

July 29, 2026: Based on xAI's July 17 release note, this tracker now treats EU API console access as available. Teams should still run their own account-level checks for Cursor, Office add-ins, gateways, pricing, logging, and production approval.

Next update should check four things: API key call success from an EU account, Cursor model picker visibility, Office add-in model label after sign-in, and gateway model availability under EU routing settings.

What EU Teams Can Run Today

EU teams can run Grok 4.5 today where the channel is enabled for their accounts. Based on xAI's July 17 release note, direct API console access is now a public "yes" for EU users. Cursor, Office add-ins, and gateways should still be treated as account-level checks, not blanket status.

If a team needs work to continue today, keep a fallback model approved. Do not pause development, research, or reporting workflows just because Grok 4.5 is available in one channel while another channel still needs account-level verification.

A practical rollout pattern is simple: test the xAI API from an EU account first, compare outputs against your current approved model, evaluate one Cursor or Office add-in workflow in a controlled account, and use gateways only after routing, logging, and retention settings are checked.

Access is only half of a switch decision. Budget approval is the other half, and Grok 4.5 does not price its full context window flat: rates double at 200K prompt tokens, and cached tokens count toward that line. Price the workflow before you commit to it, using the tier and tool-call breakdown in Grok API pricing.

How MoClaw Fits This Workflow

MoClaw fits as a fallback workflow layer for teams that care less about one model switch and more about keeping recurring digital work moving. It should not be described as an xAI product, Grok replacement, or official Grok gateway. The fit is operational: research, browser work, files, schedules, logs, and human review while model access changes.

For teams monitoring Grok 4.5 Europe availability, MoClaw's AI workflow automation is relevant because it frames work around recurring browser tasks, reports, scheduled delivery, and review records. MoClaw's AI research assistant is the better reference when the fallback task is ongoing model tracking, source monitoring, or competitive research.

The useful team question is not "Can MoClaw replace Grok 4.5?" It is "Can we keep the workflow running while model access, region settings, or gateway routing changes?"

Trade-Offs and Claims to Verify

Before publishing or acting on any Grok 4.5 EU release claim, verify the exact channel. API console access, cursor model access, Office add-ins, and gateways are different surfaces with different owners.

Check model slug, region availability, pricing, rate limits, data retention, tenant controls, logging, fallback routing, and whether the model is allowed for customer data. If switching from another model, run a small regression set first: same prompts, same source files, same expected outputs, and a human review of differences. We walk through what to measure in that regression set, and how the published benchmarks actually stack up, in Grok 4.5 vs Claude.

The biggest risk is no longer treating EU API console access as unavailable. The bigger risk is assuming API console availability proves every connected channel is ready for production.

FAQ

Can teams subscribe to status-change alerts?

Yes, but alerts should be channel-specific. Subscribe to xAI release notes, Cursor release discussions, gateway changelogs, and internal admin notifications. A single vendor announcement is not enough for EU rollout tracking if your workflow spans API, editor, Office, and gateway surfaces.

What should teams archive before access changes?

Archive baseline prompts, model IDs, system instructions, test outputs, error logs, approvals, pricing notes, and any gateway routing rules. If a model switch changes behavior, those records help the team decide whether the change came from model quality, context, routing, or configuration.

Who should approve switching models after access opens?

The workflow owner should approve business fit, the technical owner should approve integration behavior, and security or legal should review sensitive data use when needed. For coding tasks, the engineering reviewer should inspect diffs and tests before Grok 4.5 becomes a default.

How often should this tracker be updated?

Update it whenever xAI changes the release notes or developer page, Cursor posts a rollout change, Office add-ins show a new model label, or a gateway updates its model list. During fast rollout periods, daily checks are reasonable. After access stabilizes, weekly checks are usually enough.

Grok 4.5 EU Release Date Is a Channel-by-Channel Rollout

The Grok 4.5 EU release date is no longer pending for the API console. xAI's July 17, 2026 release note says Grok 4.5 is now available in the API console for EU users, but EU teams still need channel-level proof before changing production workflows.

Vera Note: This article tracks Grok 4.5 availability by channel based on publicly available information as of July 29, 2026. xAI's release notes say Grok 4.5 became available in the API console for EU users on July 17, 2026. Access can still vary by account, tenant, gateway, and platform, so verify current availability in official documentation and your own settings before making production changes.