7 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
The article details the author's frustrating experience trying to obtain a Google Gemini API key for a coding project. After navigating a confusing array of Google services and verification steps, the author ultimately gained access, but not without significant hassle and delays.
If you do, here's more
The author shares their frustrating experience of trying to obtain a Gemini API key for Google’s Gemini 3 Pro while building a React app. Initially, the author found the Gemini product ecosystem confusing, with multiple similar offerings—like the Gemini chatbot, CLI, and various AI features across Google products—making it hard to find a straightforward purchasing path. Unlike competitors like Anthropic and OpenAI, which have clear interfaces for buying API credits, Google’s setup felt convoluted.
After some trial and error, the author managed to create an API key through Google AI Studio. However, the process took a turn when they attempted to set up billing. Instead of a simple payment method entry, the author had to create a Billing Account, associate it with a project, and navigate through multiple layers of verification. This included uploading a government ID with strict format requirements, which added to the frustration. Even after completing the verification, the author encountered a 403 Forbidden error when trying to access the Gemini 3 Pro model, indicating permission issues despite having followed all the necessary steps.
The entire ordeal reflects not just the challenges of using Google’s services but also their complex and often opaque processes that can deter users from effectively utilizing their products.
Questions about this article
No questions yet.