OpenAI Enrichment Error: Usage Limit Hit Despite Tier 5 Status

Jeff T. · 2025-01-07T16:59:16.608Z

Getting an error on all my openai enrichments saying we hit our usage limit, but we're tier 5 and not even close to hitting that limit

OpenAI Enrichment Error: Usage Limit Hit Despite Tier 5 Status | Clay

9 comments

· Sorted by Oldest

Channeled
APP
·
·
To ensure reliable use of OpenAI in Clay, you need specific token per minute (TPM) requirements: ** 30,000 TPM for ChatGPT columns ** 450,000 TPM for ClaygentYou can verify your current API usage tier and limits at: 1. Check your usage: https://platform.openai.com/account/usage 2. Review your limits: https://platform.openai.com/account/limits 3. Confirm your tier status: https://platform.openai.com/docs/guides/rate-limits/usage-tiersEven if you're on tier 5, there might be other factors affecting your usage. Please check these links to verify your current usage and ensure your API key is properly configured.
Jeff T.
·
·
that didn't help
Channeled
APP
·
·
I apologize that my response wasn't helpful. You can rephrase your question, or talk to our team for further assistance.
Jeff T.
·
·
Clay is returning an error on gpt columns, stating i hit my usage limit. When I go into my OpenAI API dashboard, it's showing that to not be true
Channeled
APP
·
·
For Clay's GPT columns to work reliably, your OpenAI API key needs specific token per minute (TPM) requirements - specifically 30,000 TPM for ChatGPT columns. Even if you haven't exceeded your overall usage limit, you may be hitting the TPM rate limit.You can verify your current TPM tier at: https://platform.openai.com/docs/guides/rate-limits/usage-tiersIf you're experiencing this error, you'll need to ensure your OpenAI API key is on tier 2 or higher to meet the TPM requirements for Clay's GPT columns.
Jeff T.
·
·
no
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Jeff T.
·
·
I figured it out, you can close this ticket
Channeled
APP
·
·
Hi Jeff T.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Channeled
APP
·
·
To ensure reliable use of OpenAI in Clay, you need specific token per minute (TPM) requirements: ** 30,000 TPM for ChatGPT columns ** 450,000 TPM for ClaygentYou can verify your current API usage tier and limits at: 1. Check your usage: https://platform.openai.com/account/usage 2. Review your limits: https://platform.openai.com/account/limits 3. Confirm your tier status: https://platform.openai.com/docs/guides/rate-limits/usage-tiersEven if you're on tier 5, there might be other factors affecting your usage. Please check these links to verify your current usage and ensure your API key is properly configured.
Jeff T.
·
·
that didn't help
Channeled
APP
·
·
I apologize that my response wasn't helpful. You can rephrase your question, or talk to our team for further assistance.
Jeff T.
·
·
Clay is returning an error on gpt columns, stating i hit my usage limit. When I go into my OpenAI API dashboard, it's showing that to not be true
Channeled
APP
·
·
For Clay's GPT columns to work reliably, your OpenAI API key needs specific token per minute (TPM) requirements - specifically 30,000 TPM for ChatGPT columns. Even if you haven't exceeded your overall usage limit, you may be hitting the TPM rate limit.You can verify your current TPM tier at: https://platform.openai.com/docs/guides/rate-limits/usage-tiersIf you're experiencing this error, you'll need to ensure your OpenAI API key is on tier 2 or higher to meet the TPM requirements for Clay's GPT columns.
Jeff T.
·
·
no
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Jeff T.
·
·
I figured it out, you can close this ticket
Channeled
APP
·
·
Hi Jeff T.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: