They'll get to it when it becomes strategically important to.
Why making it easier to pay them isn't always strategically important, I'm not sure.
1. cart out in front of the horse a bit on this one, lame hype building at best
2. Not at all what I want the team focusing on, they don't seem to have a clear mission
Generally Google PMs and leaders have not been impressive or in touch for many years, since about the time all the good ones cashed out and started their own companies
hmmm
> 2. Not at all what I want the team focusing on, they don't seem to have a clear mission
allow anyone to build with Google's latest AI models, be the fastest path from prompt to production with Gemini
I want to release a service using computer-use but am worried about 429 quota errors if I have actual users.
I've been using the AI Studio with my personal Workspace account. I can generate an API key. That worked for a while, but now Gemini CLI won't accept it. Why? No clue. It just says that I'm "not allowed" to use Gemini Pro 3 with the CLI tool. No reason given, no recourse, just a hand in your face flatly rejecting access to something I am paying for and can use elsewhere.
Simultaneously, I'm trying to convince my company to pay for a corporate account of some sort so that I can use API keys with custom tools and run up a bill of potentially thousands of dollars that we can charge back to the customer.
My manager tried to follow the instructions and... followed the wrong ones. They all look the same. They all talk about "Gemini" and "Enterprise". He ended up signing up for Google's equivalent of Copilot for business use, not something that provides API keys to developers. Bzzt... start over from the beginning!
I did eventually find the instructions by (ironically) asking Gemini Pro, which provided the convenient 27 step process for signing up to three different services in a chain before you can do anything. Oh, and if any of them trigger any kind of heuristic, again, you get a hand in face telling you firmly and not-so-politely to take a hike.
PS: Azure's whatever-it-is-called-today is just as bad if not worse. We have a corporate account and can't access GPT 5 because... I dunno. We just can't. Not worthy enough for access to Sam Altman's baby, apparently.
Passing along this feedback to the CLI team, no clue why this would be the case.
But also the (theoretical) production platform for Gemini is Vertex AI, not AI Studio.
And until pretty recently using that took figuring out service accounts, and none of Google's docs would demonstrate production usage.
Instead they'd use the gcloud CLI to authenticate, and you'd have to figure out how each SDK consumed a credentials file.
-
Now there's "express mode" for Vertex which uses an API Key, so things are better, but the complaints were well earned.
At one point there were even features (like using a model you finetuned) that didn't work without gcloud depending on if you used Vertex or AI Studio: https://discuss.ai.google.dev/t/how-can-i-use-fine-tuned-mod...
I google `gemini API key` and the first result* is this docs page: https://ai.google.dev/gemini-api/docs/api-key
That docs page has a link in the first primary section on the page. Sure, it could be a huge CTA, but this is a docs page, so it's kinda nice that it's not gone through a marketing make over.
* besides sponsored result for AI Studio
(Maybe I misunderstood and all the complaints are about billing. I don't remember having issues when I added my card to GCP in the past, but maybe I did)
100% agree
That said, while setting up the Gemini API through AI Studio is remarkably straightforward for small side projects, transitioning to production with proper billing requires navigating the labyrinth that is Google Cloud Console. The contrast between AI Studio's simplicity and the complexity of production billing setup is jarring, it's easy to miss critical settings when you're trying to figure out where everything is.