Billing Console Issues with Custom API Key for Clay 4.1 Models

Hi there, I noticed that when selecting the new 4.1 models in Clay, if you have your own API key set, the billing console still uses gpt-4o-2024-08-06 meaning it's actually using the 4o model. This doesn't seem to be the case when using the clay-provided key that uses credits

🎫1

8 comments

Emilio L.
·
·
Bruno R. Clay S.
Channeled
APP
·
·
We don't have specific information about why the billing console shows "gpt-4o-2024-08-06" instead of the 4.1 model when you use your own API key. This could be a technical discrepancy or a display issue in our system. When you use your own API key, you're billed directly through the provider's platform rather than through Clay credits. This means the cost isn't reflected in Clay's billing console, but rather in your OpenAI account. To better assist you with this issue, could you provide more details about when you first noticed this discrepancy and if it's affecting your usage or billing in any way?
Source: Use AI integration overview | Documentation | Clay University
Channeled
APP
·
·
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Michael W.
·
·
Still occuring as of today
Channeled
APP
·
·
We don't have specific information about why the billing console shows "gpt-4o-2024-08-06" instead of the 4.1 model when you use your own API key. This could be a display issue in our system. When you use your own API key, you're billed directly through OpenAI's platform rather than through Clay credits. The cost isn't reflected in Clay's billing console but in your OpenAI account. To help us investigate this issue further, could you provide more details about when you first noticed this discrepancy and if it's affecting your usage or billing in any way?
Source: Use AI integration overview | Documentation | Clay University
Bruno R.
·
·
Hi Michael, thanks for your message and sorry about this! Can you share the url to the table where you're seeing the calls misrouted to the 4o when selecting models from the 4.1 series? Will take a closer look at what may be happening here, but have not been able to reproduce the same issue on my end so it would be super helpful to see a column where this occurred so I can investigate this issue closer.
Channeled
APP
·
·