There are a few possible reasons why you're still seeing Clay Credits being used despite using your own API keys:
1. Some columns might still be using Clay's shared API keys instead of your own. Double-check each integration to ensure you've properly connected your personal API keys.
2. Certain AI models in the "Use AI - Content Creation" category that use Clay's shared key will consume credits based on token usage. These have variable credit costs depending on prompt complexity.
3. You might be using services where you haven't provided your own API key, so Clay's default shared key is being used instead.
To verify, check your workspace settings to confirm all integrations are using your own API keys. For any integration without your personal key connected, Clay will use its shared key and charge credits accordingly.
Hey there, thanks for reaching out! Just responded to you in a separate thread, let me know how else we can help and if this continues to happen in the future!
.png){kind=logo}
