The author documents an excessively frustrating ordeal attempting to acquire paid access to Google's Gemini 3 Pro model for use in a development project via the Gemini CLI. The core issue stems from Google's overly complex and bureaucratic billing and verification process, especially when compared to the streamlined developer onboarding offered by competitors like Anthropic (Claude) and OpenAI. The author details the confusion caused by the overloaded "Gemini" branding, the mandatory dive into the labyrinthine Google Cloud Console for billing setup, and the highly intrusive requirement to submit government ID and redacted credit card photos for payment verification—a process that took several days to resolve despite initial OTP verification. Even after billing was supposedly "in good standing," the API key initially returned a 403 PERMISSION_DENIED error until a final, unexplained email confirmed reinstatement. The author concludes that Google's system is designed for large organizations, not individual developers seeking efficiency, and suggests the experience was a complete waste of time, implying a preference for smaller, more developer-friendly providers until Gemini proves significantly superior.
Getting a Gemini API Key: A Bureaucratic Nightmare
0:00 Project Context: Author started a React side-project requiring LLM assistance for boilerplate CRUD code, intending to use Gemini 3 Pro via the CLI.
0:36 Overloaded Branding: "Gemini" refers confusingly to numerous products (chatbot, mobile app, CLI, Code Assist, underlying LLM), making service identification difficult.
1:05 Direct Comparison to Competitors: Anthropic/OpenAI offer simple consumer access (via URL) or API access (via developer console with clear payment forms); Google lacks these obvious "Buy Now!" options.
1:38 Initial Help Failure: Free Gemini chatbot failed to clearly direct the author on paying for Gemini 3 Pro access (which requires an API key, not a consumer plan), responding with "Something went wrong" when questioned about pricing.
2:10 API Key Creation (Easy Part): The author successfully generated an API key via Google AI Studio, which initially worked for basic access.
2:33 Billing Hell: Clicking "Set up billing" redirects to the daunting Google Cloud Console, requiring creation of a Billing Account, association with a project, and then adding a payment method.
3:08 Intrusive Verification: After entering OTP verification, Google demanded further verification: uploading a government ID and a redacted image of the credit card used.
3:45 Upload Failure: The ID upload form was highly specific, rejecting common formats (JPG, PDF) in favor of PNG, providing no instruction otherwise.
4:15 Resolution Delay: After submitting documents, Google stated verification would take "a few days."
4:32 Unexpected Resolution: Fifteen minutes later, a confirmation email arrived stating the billing account was "reinstated."
5:00 Post-Verification Confusion: Even after the email, the author had to re-associate the project with the billing account multiple times before the API key status changed from "Set up billing" to "Tier 1."
5:18 Final API Failure (403): Despite successful billing association, calls to Gemini 3 Pro via CLI and JavaScript failed with a 403 PERMISSION_DENIED error, and the AI Studio Playground showed an internal error.
6:03 Success After Email: Gemini 3 Pro finally functioned across all interfaces only after receiving a second email confirming the billing account was "in good standing."
6:35 Conclusion (Skepticism): The entire process took three hours and was deemed a waste of time. The author believes Google's system prioritizes bureaucracy and compliance for large organizations over developer efficiency, suggesting they don't actually want individual customers unless the product vastly outperforms competitors.