Getting a Gemini API key is an exercise in frustration

Trying to implement their gRPC api from their specs and protobufs for Live is an exercise in immense frustration and futility. I wanted to call it from Elixir, even with our strong AI I wasted days then gave up.

I went through the same nightmare a couple of months ago; in frustration I sent a not very nice email to support. They did respond a week later, saying everything was "fixed". But by that time I had moved on, and will probably never come back.

But I wonder how it can happen that a bunch of obviously extremely smart people can create such absurd Rube Goldberg machines -- without the fun part.

there's prob a couple ppl out there with an Amex Black parked on a cloud acct, lol

Oh man let me add onto that!

4. If you read about a new Gemini model, you might want to use it - but are you using @google/genai, @google/generative-ai (wow finally deprecated) or @google-ai/generativelanguage? Silly mistake, but when nano banana dropped it was highly confusing image gen was available only through one of these.

5. Gemini supports video! But that video first has to be uploaded to "Google GenAI Drive" which will then splices it into 1 FPS images and feeds it to the LLM. No option to improve the FPS, so if you want anything properly done, you'll have to splice it yourself and upload it to generativelanguage.googleapis.com which is only accessible using their GenAI SDK. Don't ask which one, I'm still not sure.

6. Nice, it works. Let's try using live video. Open the docs, you get it mentioned a bunch of times but 0 documentation on how to actually do it. Only suggestions for using 3rd party services. When you actually find it in the docs, it says "To see an example of how to use the Live API in a streaming audio and video format, run the "Live API - Get Started" file in the cookbooks repository". Oh well, time to read badly written python.

7. How about we try generating a video - open up AI studio, see only Veo 2 available from the video models. But, open up "Build" section, and I can have Gemini 3 build me a video generation tool that will use Veo 3 via API by clicking on the example. But wait why cant we use Veo 3 in the AI studio with the same API key?

8. Every Veo 3 extended video has absolutely garbled sound and there is nothing you can do about it, or maybe there is, but by this point I'm out of willpower to chase down edgy edge cases in their docs.

9. Let's just mention one semi-related thing - some things in the Cloud come with default policies that are just absurdly limiting, which means you have to create a resource/account, update policies related to whatever you want to do, which then tells you these are _old policies_ and you want to edit new ones, but those are impossible to properly find.

10. Now that we've setup our accounts, our AI tooling, our permissions, we write the code which takes less than all of the previous actions in the list. Now, you want to test it on Android? Well, you can:

- A. Test it with your account by signing in into emulators, be it local or cloud, manually, which means passing 2FA every time if you want to automate this and constantly risking your account security/ban.

- B. Create a google account for testing which you will use, add it to Licensed Testers on the play store, invite it to internal testers, wait for 24-48 hours to be able to use it, then if you try to automate testing, struggle with having to mock a whole Google Account login process which every time uses some non-deterministic logic to show a random pop-up. Then, do the same thing for the purchase process, ending up with a giant script of clicking through the options

11. Congratulations, you made it this far and are able to deploy your app to Beta. Now, find 12 testers to actively use your app for free, continuously for 14 days to prove its not a bad app.

At this point, Google is actively preventing you from shipping at every step, causing more and more issues the deeper down the stack you go.

>Startup credits require multiple follow-ups, meetings, etc. And these reps have weird incentive structures (so they are trying to bypass each other to meet their quotas or whatever).

Man, I tried going for the credits. I've organised meetups and conferences for Google, gave talks, been a part of Google Startup campus for years now, have been invited to participate in GDE program, and as I'm making a GenAI startup I decided "well, maybe time to try getting those 300k cloud credits, I've given them so much I'll surely get it".

Well, the first person I talked to, said I'm denied, because they didn't even check the websites I added in the description. They said oh I need to add it to another field for their team to see, told me to update it, but there is no way to update it. Then we had a second call, they said it's okay I can ignore that and pointed me to another person who will be my "account manager".

That person was absolutely uninterested into what we're doing, what we want and what we plan to do. They did not even care about helping us much until we reached 15k monthly spend or so, giving a holier-than-thou attitude and sounding like they're making lunch during the call. I'd rather have the call with an LLM at this point.

Then even though our website says our product relies on AI, it is impossible without AI and I explained to him how and why we train custom models and use their GenAI products - the person decided we are not an AI company and can only get 2k in Cloud credits.

The interaction left such a sour taste in my mouth that I will _never_ use Google Cloud in our product, as I do not want to have to deal with the Account Manager.