Request for Assistance with $250 API Calls on 4.1 Mini

Edmund C. · 2025-10-16T22:25:02.824Z

hey guys I need some help. I cannot figure out how & why I just ran through $250 in api calls on 4.1 mini. Can someone help look at my table? Perhaps its sending data to multiple tables?

Request for Assistance with $250 API Calls on 4.1 Mini | Clay

Edmund C.
·
·
https://app.clay.com/workspaces/161098/workbooks/wb_0t2cv45JGeFT3TxT4wi/tables/t_0t2cv45KbYqMSmZRXbh/views/gv_0szvu2eJYquTfQEQRCi
Clay Support
APP
·
·
To investigate your $250 credit usage, check Settings → Credit Usage to see detailed logs of consumption by table and integration. [1] Right-click any enrichment column and select Run Info to review credit usage per process.
Common causes of unexpected usage include:
Automated features like auto-updates or scheduled runs
Duplicate enrichments on overlapping datasets
Recurring processes marked as "Recurring" in your usage logs
To check if your table sends data to multiple tables, look for Send table data or Write to Other Table actions in your table. [2] These can connect up to 10 tables across workbooks. [3]
Also check for infinite loops - when tables send data back and forth, causing continuous credit consumption. [4] Look for columns marked as "Recurring" to identify ongoing automated processes.
If you need further help analyzing your specific table, request human assistance by clicking on Talk to a person.
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
High credit usage can happen due to several factors:
Common causes:
Automated features like auto-updates or scheduled runs consuming credits repeatedly
Failed data validation still charging credits even for invalid results
Duplicate enrichments running on the same data multiple times
Infinite loops from circular table references or webhook triggers [1]
To check your table's credit usage:
1.
Right-click any enrichment column and select Run Info for detailed credit breakdown
2.
Go to Settings → Credit Usage to see table-level consumption [2]
3.
Look for columns marked as "Recurring" which indicate ongoing automated processes
For data sending between tables:
Our "send table data" feature has a maximum of 10 connected tables across workbooks. [3] Check if you have multiple table connections that might be duplicating enrichments.
Review your table history and credit logs to identify what's consuming credits unexpectedly.
Clay Support
APP
·
·
Was that helpful?
Edmund C.
·
·
no human
Clay Support
APP
·
·
I understand this is frustrating, so I’m connecting you to a human agent who can assist you further.
Intercom
APP
·
·
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon!
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!
Loading attachments
Edmund C.
·
·
I only have one claygent call and its only 4.1 mini
Edmund C.
·
·
https://app.clay.com/workspaces/161098/workbooks/wb_0t2cv45JGeFT3TxT4wi/tables/t_0t2cv45KbYqMSmZRXbh/views/gv_0szvu2eJYquTfQEQRCi
Edmund C.
·
·
I only have one claygent column w/ 4.1 mini and the credit usage happens as the same time I run this table
Edmund C.
·
·
is data being sent to other tables and using OAI credits there? this makes no sense.
Edmund C.
·
·
are the spend amounts in claygent not right?
Edmund C.
·
·
this is 100% coming from clay as i can see the contents of the calls
Loading attachments
Aditi S.
·
·
Hi Edmund - thanks so much for reaching out and for your patience here. To clarify - I believe your question is where the credit spend to your API key is coming from based on the table you shared. I can see that for your "Leadership Contacts" Claygent column, this ran for 6,625 rows on it's last run.
I am noticing that you didn't set a max cost to the provider, which may have impacted how much was charged to you on your API Key for this:
The default is the following if you don't select a specific request:
This may clear up why you see that particular cost on your API key end.
Loading attachments

16 comments