Hey everyone! I just got some news about the Gemini 2.5 rollout and wanted to share. Looks like we’re gonna have to pay for using the Gemini API now. The price is supposed to be similar to other quick models we use. Google should be telling everyone the exact price soon.
But here’s the good part - they’re gonna pay us back for all the Gemini 2.5 Pro stuff we’ve used up until today! That should be sorted out by tomorrow.
I know they messed up by not telling us about this earlier. I guess they’re trying to make up for it by covering what we’ve used so far. That way we all know what we’re getting into with the costs and stuff.
Anyone else heard about this? What do you guys think? Let me know if you’ve got questions!
thx for the heads up! kinda bummed we gotta pay now, but at least google’s coverin what we used. wonder how the pricing compares to other APIs? hope it’s not too crazy or itll be hard to justify using gemini. guess we’ll see when they release the details. fingers crossed it’s reasonable!
I appreciate the update on Gemini 2.5. While the transition to a paid model is disappointing, it’s not entirely unexpected given the industry trends. Google’s decision to reimburse previous usage demonstrates some goodwill. However, the lack of clear communication beforehand is concerning. It’s crucial to have transparent pricing information to properly evaluate whether Gemini remains a viable option compared to alternatives. I’ll be closely monitoring the official announcement to assess the impact on my projects and budget. Hopefully, the pricing structure will be competitive enough to retain users who have invested time in integrating Gemini into their workflows.
Thanks for sharing this info, RunningRiver. It’s always a bit of a shock when a free service starts charging, but I guess it was inevitable with Gemini’s capabilities. I’ve been using it for a few projects, and the results have been impressive.
While I’m not thrilled about having to pay, I’m glad Google is reimbursing us for past usage. That gives us a clean slate to evaluate whether it’s worth continuing with Gemini or exploring alternatives.
One thing I’m curious about is how the pricing will be structured. Will it be per-query, based on compute time, or some other metric? That could make a big difference in how cost-effective it is for different use cases.
I’ll definitely be keeping an eye out for the official announcement. Hopefully, they’ll provide some detailed documentation on the pricing model so we can make informed decisions about our API usage going forward.