My Gemini Key won't auth. My old one had been working fine until yesterday, but it's showing I'm rate-limited this morning. I generated a new key, tested it in Terminal to confirm it works, and tried to Add Connection with it. When I try to Save and Test, the test is failing
For Gemini API keys in Clay, you need Tier 2 access and the Gemini 2.0 Flash model specifically. [1] Gemini 1.5 models may require additional access through Vertex AI.
Since your key works in Terminal but fails in Clay, double-check:
• You're using the complete API key (no missing characters)
• The key has proper tier access for Clay's requirements
Try Sculptor (top-right corner) to help diagnose the connection issue—it can analyze error messages and suggest fixes. Let me know if Sculptor helps or if you need further assistance.
Is that what you were looking for?
What is Tier 2 access?
Tier 2 access refers to Google's API usage tier that provides at least 450,000 tokens per minute (TPM). [1]
For Gemini specifically, Tier 2 is required to use the API in Clay, but it only works with the Gemini 2.0 Flash model. You can check your current tier and upgrade through Google's API console if needed.
Did that answer your question?
If you still need help understanding Tier 2 access or resolving your Gemini Key issue, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any specific problems you’re encountering?
Does Clay work with Vertex AI Studio keys?
For Gemini specifically, you need the standard Gemini API key with Tier 2 access and the Gemini 2.0 Flash model. If you're trying to use a Vertex AI Studio key, you might need to generate a regular Gemini API key instead through Google's standard API console. [3]
Was this information useful?
If you still need help with your Gemini Key or API access issues, I’m here to assist. Would you like to share more details about what you’re trying to resolve or understand?
So there's no way we can use our Gemini keys until we've accumulated $250 in billing on our GCP project? Tier 2 appears to be unavailable, even after entering billing information for a Tier 1 project
That's correct—Google's Tier 2 access typically requires meeting their billing thresholds, which can include the $250 spending requirement you mentioned. [1]
You have two alternatives:
• Use Clay credits instead—we manage all the tier requirements and scaling automatically, so you don't need to worry about API tiers. [2]
• Wait until your GCP project qualifies for Tier 2, then use your own Gemini key to potentially reduce costs. [3]
Clay credits are often the faster solution since there's no tier management needed on your end.
Is that what you were looking for?
Yes. It just makes me sad
I understand that can be frustrating. If you want to share more about your situation or have any other questions, I’m here to help.
