my open ai keys aren't working, been using them for a while and suddenly clay is showing this error. It has the funds. Even connected a new account
The "Could not verify the OpenAI API key" error usually means either the API key is incorrect or your OpenAI account doesn't meet the tier requirements for Claygent.
For Claygent web research, you need Tier 2 or higher (≥450,000 TPM) on your OpenAI account. [1] Even with funds, if you're on a free plan or Tier 1, it won't work.
First, double-check your API key at https://platform.openai.com/account/api-keys and update it in Clay. Then check your usage tier at https://platform.openai.com/settings/organization/limits to see if you need to upgrade to Tier 2.
If you need to upgrade your tier, you'll need to contact OpenAI support directly.
Did that answer your question?
yes, but everything is correct, like i said, the key was used since a while and i am on Tier 3 already
Since your API key was working before and you're on Tier 3, this sounds like a temporary verification issue. Try updating your API key in Clay even if it's the same one - sometimes re-entering it resolves verification problems.
You can grab your key from https://platform.openai.com/account/api-keys and paste it fresh into Clay's settings. If that doesn't work, there might be a temporary issue with OpenAI's API verification system.
Did that answer your question?
nope
I'm sorry for the trouble you're experiencing. 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!

ok
Hi Ankit - this seems to be an annoying UI bug on our end that the team is actively trying to fix. However, this won't stop you from running the column successfully. Could you save and run on 10 rows to test this out? Please let us know if you face any issues. Thank you!
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.
