Investigation Needed: $500 in OpenAI API Credits Burned

This is unusual and concerning. When using OpenAI with your own API key in Clay, the charges go directly to your OpenAI account rather than using Clay credits. AI models have varying credit costs in Clay, but when you use your own OpenAI API key, you're billed through OpenAI directly. Some AI enrichments can have variable costs depending on prompt complexity and token usage. I recommend checking your OpenAI account usage dashboard to see exactly what caused the spike. If you need further investigation into this unexpected charge, please request human assistance by clicking "Talk to a person" as they can help review your specific account activity in detail.

Source: Credits | Documentation | Clay University

Hey there Adnan thanks for reaching out, sorry to hear that this occurred, do you mind sending the link (url) to the table so we can take a look?

Sorry for the delay here, one last question just to confirm so we know what time search for this occurred during May 14th correct?

Hey, I took a look and it seems there were forced reruns on some columns, which triggered around 10,000 rows. A few of those columns—like Industry Check L1, Industry Check L2, and Job Title—also had downstream enrichments tied to them. Even if the original rows errored out or weren’t fully processed, the reruns and their dependencies would’ve still consumed OpenAI credits, which explains the spike. Let me know if you’d like help reviewing how to avoid this going forward.

Hey there Adnan jumping in back in here, if you wish to avoid situations like this in the future what you can do here, is ensure that the table's column "Auto-update" feature is turned off, this can be found in the bottom right-hand corner of the table.

Additionally, for a double layer of safety you can also turn off the "Auto-update" option for the columns as well here. This option is found inside of all integration setup menu, inside of the "Run Settings" field.