How to Track OpenAI API Costs in Large Clay Workspaces | Clay

How to Track OpenAI API Costs in Large Clay Workspaces

question: if you're is seeing significant openai costs coming in using an openai api key but unsure where in a big Clay workspace it's being used/charged, how can you find out where it's coming from? since the credit usage page in settings only appears to show clay credits used, and since in this case it's an openai api key being used and therefore no clay credits spent, is there any other way to identify where columns are running that are incurring these api key-based costs?

4 comments

Channeled
APP
·
·
Unfortunately, Clay's credit usage page doesn't show external API key usage, including OpenAI API costs. When you use your own API key, those charges are handled directly by the external service (in this case, OpenAI). To identify where the OpenAI API key is being used in your workspace, you'll need to review your workbooks and tables manually, focusing on areas using AI integrations. Look for columns or actions that might be utilizing OpenAI's services. If you need more detailed tracking or assistance in identifying the specific usage, you may want to request human assistance by clicking on "Talk to a person" for a more thorough investigation of your workspace.
Source: FAQ | Clay.com
Bo (.
·
·
Hey, Unfortunately, we can’t see detailed usage data tied to your OpenAI API key directly from within Clay. At best, we can check which tables had recent runs, but pinpointing the exact column or usage source is tricky. Do you know in which workspace it was? Happy to check To make this easier going forward, we recommend using separate OpenAI API keys for each workspace. That gives you clearer visibility in your OpenAI usage logs and makes it easier to trace where costs are coming from. Let me know if you want help setting that up.
Elias S.
·
·
would be very grateful if you could check which tables have recent runs! Here's the workspace – thank you! https://app.clay.com/workspaces/429280
Elias S.
·
·
Nevermind – found it! Thanks anyways!