I was exited to try out grok 4.5, but I am in EU ![]()
Same here, starting from around 2 AM GMT, It keeps taking API token pool. A bit annoyed with Cursor budget control in the last two days. A budget control incident yesterday, and now this issue.
Why I can see any other model in EU when they come out but not Grok 4.5? What is the exact problem?
Jul 9, 12:13 PM
On-Demand
grok-4.5-fast-high
482,9K tokens
26.2 requests…
this is the 50% ‘discount’… really?
![]()
I tested with VPN by the way (I’m in the EU) ![]()
Hey all,
I’ve tested it this afternoon and Grok 4.5 should now be pulling from the first-party model pool. Please rely on the stats under https://cursor.com/dashboard/billing!
Hi @KhanhDo,
It looks like you’re on an Enterprise plan, which doesn’t distinguish between an Auto + Composer (first-party) pool and an API pool—instead, you have a single, unified pool of credits. Depending on your specific plan, you may also have promotional credits that make certain requests (such as Composer 2.5) free, based on your team’s usage.
We want to make Grok 4.5 available worldwide. We have to comply with some notification requirements before making new models available. We will make Grok 4.5 available in the EU as soon as we can!
Great model and experience so far. Can the team share the rationale of 256k context window on Grok 4.5 in Cursor despite the official context window being 500k for the model? In Max mode this also does not change to my understanding.
I can’t even use it. Keep on getting an error message that says this model doesn’t accept custom API keys.
Request ID: eb37a125-56ec-4058-b40b-5ae5bca17937
{“error”:“ERROR_BAD_REQUEST”,“details”:{“title”:“Bad Request”,“detail”:“This model does not support custom API keys.”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:,“analyticsMetadata”:{“actionRequired”:“config”}},“isExpected”:true}
This model does not support custom API keys.
Bad Request This model does not support custom API keys.
Pretty messed up to pay for the Ultra plan only to be blocked from using this new model during the exact week its price is discounted. Yeah, I’m from the EU.
Hi @SymplexitySGL thanks for your forum post! You can manage your subscription here: https://cursor.com/dashboard/billing and you can switch to a plan like Pro, Pro +, and Ultra. Note that after you switch, you won’t be able to return to the request-based legacy plan.
Hi @egm Thank you for the post, this is a regulatory requirement of the EU that we need to abide by. Rest assured, we are doing everything we can to get it to you as soon as possible.
Also, as an Ultra Plan user you will have a TON of included usage on Cursor Grok 4.5 drawing from your 1st Party Model pool (previously named Auto+Composer). Even without the 50% discount / double usage promotion it will be a huge amount of usage.
Hi @Christian-von-Uffel, sorry for the blocker. I checked your request and found that Cursor is attaching your enabled custom OpenAI-compatible configuration to Grok 4.5. Grok 4.5 is a Cursor first-party model and does not accept custom API keys.
As a workaround:
- Open
Cursor Settings > Models > OpenAI. - Disable the custom API key and any custom base URL.
- Retry Grok 4.5.
You can re-enable those settings when switching back to a model served by your custom provider. We’re tracking this routing issue internally.
More information: https://cursor.com/docs/settings/api-keys
After getting used to reading Composer’s walls and walls of text, Grok 4.5 sure seems… quiet. Not a problem, but quite a drastic pull in the other direction for also being a Cursor product.
generally speaking, Cursor is not going to ban you for using a VPN unless the activity is abusive (e.g. account farming, account sharing, credit card fraud, etc).
@kevinn
Its a GREAT model
Unfortunately cursor currently has a bug
When Grok 4.5 launches subagents w/inherit from parent
It launches GPT subagents, hitting API pool usage rather than first party
Thus it can’t be used reliably for billing purposes
Not happy. Was saving the last bit of my API pool for refactor

