Confirmation of Charges vs. Data Generation Issues

Laney L. · 2026-01-09T19:27:53.887Z

Hi Friends - I wanted to confirm if I was indeed charged credits with no data generated. There are quite a few of these instances, and I thought to share these two as example. Please let me know what other data point is needed. Also, when I share the workspace link, I wasn't sure if it's public or only to clay staff.

Confirmation of Charges vs. Data Generation Issues | Clay

10 comments

· Sorted by Oldest

Clay Support
APP
·
·
I'd be happy to help look into this credit charge issue. To investigate further, could you please share the workspace link or workspace ID where you're seeing these charges? (Don't worry - workspace links shared with Clay support are only visible to our team, not public.)
Laney L.
·
·
workspace ID is 557536
Clay Support
APP
·
·
Yes, workspace links shared with us are only visible to our team, not public. [1]
Regarding credit charges with no data - this is actually expected behavior. Credits are consumed when enrichment processes run, even if they don't return valid data. AI columns specifically incur costs for every row processed, regardless of output quality. [2]
While I don't have full information about your specific workspace charges, the "Response: null" results you're seeing suggest the enrichment ran but didn't find data. This still consumes credits because our system made the API calls to attempt the enrichment.
To better understand your credit usage, you can check the "Run Info" by right-clicking on the column - this shows credits spent on that specific column. [3] You can also view detailed credit usage under Settings > Credit usage in your workspace. [4]
If you believe there's an error with these charges, I'd recommend asking to speak with a human who can investigate your specific workspace in more detail.
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help understanding your credit charges or have more questions about your workspace, I’m here to assist. Would you like to provide more details about what you’re trying to resolve or understand?
Laney L.
·
·
i'd appreciate speaking to a human about this as it's not an isolated incident. shavings make a pile
Clay Support
APP
·
·
Got it — I’m connecting you to a human teammate now.
Clay Support
APP
·
·
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!

image.png(93 kB)
Bo (.
·
·
Hi,
Yes, that’s expected. Claygent is charged for the work it performs, not for whether it returns data. It’s an AI agent that consumes tokens while running a task, so credits are used each time it executes, even if the final output is empty.
This is different from deterministic providers where you’re charged only when data is returned. Here, the cost comes from the processing itself.
Also, when you share a workspace link, it’s only accessible to Clay staff unless you explicitly share it with others.
Let me know if you have more questions.
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.

Still need help here? Reply back and someone will jump back in.

Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!

Clay Support
APP
·
·
I'd be happy to help look into this credit charge issue. To investigate further, could you please share the workspace link or workspace ID where you're seeing these charges? (Don't worry - workspace links shared with Clay support are only visible to our team, not public.)
Laney L.
·
·
workspace ID is 557536
Clay Support
APP
·
·
Yes, workspace links shared with us are only visible to our team, not public. [1]
Regarding credit charges with no data - this is actually expected behavior. Credits are consumed when enrichment processes run, even if they don't return valid data. AI columns specifically incur costs for every row processed, regardless of output quality. [2]
While I don't have full information about your specific workspace charges, the "Response: null" results you're seeing suggest the enrichment ran but didn't find data. This still consumes credits because our system made the API calls to attempt the enrichment.
To better understand your credit usage, you can check the "Run Info" by right-clicking on the column - this shows credits spent on that specific column. [3] You can also view detailed credit usage under Settings > Credit usage in your workspace. [4]
If you believe there's an error with these charges, I'd recommend asking to speak with a human who can investigate your specific workspace in more detail.
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help understanding your credit charges or have more questions about your workspace, I’m here to assist. Would you like to provide more details about what you’re trying to resolve or understand?
Laney L.
·
·
i'd appreciate speaking to a human about this as it's not an isolated incident. shavings make a pile
Clay Support
APP
·
·
Got it — I’m connecting you to a human teammate now.
Clay Support
APP
·
·
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!

image.png(93 kB)
Bo (.
·
·
Hi,
Yes, that’s expected. Claygent is charged for the work it performs, not for whether it returns data. It’s an AI agent that consumes tokens while running a task, so credits are used each time it executes, even if the final output is empty.
This is different from deterministic providers where you’re charged only when data is returned. Here, the cost comes from the processing itself.
Also, when you share a workspace link, it’s only accessible to Clay staff unless you explicitly share it with others.
Let me know if you have more questions.
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.

Still need help here? Reply back and someone will jump back in.

Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!