Claygent Issues on Gemini: API Key Problems Persist

Claygent with Gemini requires Tier 2 access and only works with the Gemini 2.0 Flash model. Gemini 1.5 models may require additional access through Vertex AI or custom tiers. Check that your API key has Tier 2 access and ensure you're using the Gemini 2.0 Flash model specifically, not the 1.5 models.

Source: AI Tokens | Documentation | Clay University

Do you mind sending the link (url) to the table so we can take a look?

Hey — sorry you’re running into this. Since you’re in multiple accounts, we’ll need a bit more context to help troubleshoot. Can you send over the table URL where you’re seeing the issue, or let us know which account you’re trying to use Gemini in? That’ll help us pinpoint what’s going wrong. Let me know and we’ll take it from there.

Just to confirm — which column isn’t working with Gemini? Can I duplicate the table to test it on my end?

Can you double-check a couple things? I do see some rows are working, but others not which leads me to think they might be failing due to: Rate limiting or auth issues — if you’re using a Google API key (AIza...), Gemini can silently block requests if the key hits usage limits, billing caps, or if the payload is malformed. Can you check on their end?

- Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!

Good news! Happy to report that we heard back from the team and this issue should be fixed. Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.