Questions about cursor's charging model and model calling strategy (gemini 2.5 pro, claude 3.7, and more)

Hello, how did gemini-2.5-pro-max work on your project before? Which is better than the Claude 3.7 thinkig? :waving_hand:

better at what?

model preference is highly dependent on the task

Can you give a positive explanation if you can?

Hey, did you find a solution to this?

I haven’t, but I did notice that 2.5-pro-max isn’t listed in the Gemini API docs and I can’t remember if it was before or not

I’m also not able to get max to work either with a paid API key + cursor pro. Are you able to get gemini-2.5-pro-preview -03-25 working with agent mode? I’m getting a warning that preview doesn’t have agent support. I’ve been using exp until about 2pm, when I get error message about quota limits being hit. I’d like to get some version of the gemini 2.5 working in agent mode, so any tips or konami codes would be helpful!

I put in a request for 2.5 preview agent support: [REQUEST] agent support for gemini-2.5-pro-preview-03-25 via API keys

1 Like

Hey, I am confirming with the team if we have a bug here stopping Max from working with an API key, this is definitely a use we want to support!

@danperks Is it possible to add agent support for preview in addition to experimental? I’m paying for Gemini API access and Cursor Pro. In the paid tiers for Gemini, the API quota for experimental is undefined and craps out randomly through the day. Preview has a defined quota and seems like it should be more stable. According to Google’s docs, the two models, experimental and preview, should be identical. Preview is just the paid version.

In 0.49, we have added a Google API Key section, so you should be able to add your key in there, and add the model you want as a custom model!

Thanks for the update.
Now I can call ā€˜Gemini‑2.5-pro-max’ with my Google API key, but I still randomly running into rate‑limit errors. From what I can see in the GCP console, the requests seem to be redirected to gemini‑2.5‑pro‑exp endpoint.
Because exp has tighter rate-limits than preview, it would probably be better if calls the preview endpoint whenever a Google API key is provided.
(On my side, requests explicitly sent to preview go through even when the rate‑limit error appears.)
If cursor is already set up this way and I’ve misunderstood, apologies—just hoping this feedback helps.

1 Like

Ah, I wasn’t clear - I am already using my own Google API key and already pay for Cursor Pro. I would like agent support for preview, which is the better supported version of exp.

1 Like

sounds like I’m not the only one with the same issue as you. I created this post Allow Selection Between gemini-2.5-pro-preview and -exp for Max Mode with API Key which I believes contains the same issue we are both experiencing.

2 Likes