Gemini rate limits are managed by Google, not Clay. To increase your limits, you'll need to upgrade your API tier directly with Google. [1]
We've implemented retries and smarter pacing to better handle rate limits and reduce errors. For immediate relief, try processing smaller batches of data to stay within your current limits.
If you need any more help with the Gemini rate limiting or anything else, please let me know. Would you like to provide more details about what you're trying to resolve or understand?
Yea - I believe this might be due to the rate limits of Gemini, which stems from Google-sides. Unfortunately, theres no quick fix as of currently; I recommend trying other models or implement slower- steadier pacing requests!
Unfortunately, no current way to optimize it except in small manual batches. However, this is something that we are currently working/focusing on improving!