Why am I getting this error if I've been using this key for several months? Re-creating a new key doesn't help either.
This error typically occurs when your OpenAI API key doesn't meet the required usage tier for Claygent web research. For reliable Claygent performance, you need 450,000 TPM (tokens per minute).
Even if you've used the key before, OpenAI may have changed tier requirements or your account status. Check your usage tier at OpenAI API Usage Limits.
If you're on tier 1 or free plan, upgrade to tier 2. You can also verify your API key at OpenAI API Keys and update it in our system.
Did that answer your question?
I have - Current tier Usage tier 4 and this error occurs on any OpenAI model
Since you're on tier 4 and the error occurs across all OpenAI models, this suggests an API key validation issue rather than tier limitations.
Try these steps:
Verify your API key at OpenAI API Keys - ensure it's active and correct
Update the key in Clay - even if it looks correct, copy the entire key again as a single missing character can cause verification errors
Check API key permissions - ensure the key has proper access to the endpoints you're trying to use
If the issue persists after updating the key, ask to speak to a human for further troubleshooting.
Is that what you were looking for?
I understand your frustration, and I’ll connect you to a human agent who can assist you further.
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!

Hey Oleksii! Thanks for reaching out. Happy to help. This is a bug with validating API keys. We've got engineers taking a look at it. Your records should still run as expected. We'll follow up as soon as the validation error is resolved.
Hey Oleksii! 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.
