DNAngelX
07/29/2025, 9:40 PMDNAngelX
07/29/2025, 9:44 PMjson
{
"role": "bot",
"message": "Guten Tag, mein Name ist Mia vom Kundenservice der BT Group. Wie kann ich Ihnen helfen?"
},
{
"role": "user",
"message": "Tell me, how are you?"
},
{
"role": "bot",
"message": "Thank you for asking. I'm here and ready to support you. How can I assist you today?"
}
✅ Own Key Call (4f004ae9-...)
json
{
"role": "bot",
"message": "Guten Tag, mein Name ist Mia vom Kunden der BT Group. Wie kann ich Ihnen helfen?"
},
{
"role": "user",
"message": "Hello, Mia. How are you?"
},
{
"role": "bot",
"message": "Hello. I'm doing well. Thank you. How can I help you today?"
}
🧠 These are semantically identical conversations – same length, same system prompt, same structure.
🚨 This Indicates a Severe Accounting Problem
• Token usage with your key almost doubles even for tiny calls.
• With longer calls, the token cost difference scales up drastically, indicating something is deeply off.
• According to your own logs, 21,586 prompt tokens were used for a 15-second call with no tools, no long chat history.
• With our own OpenAI key, the exact same content only used 10,811 prompt tokens – and was free under OpenAI’s token quota.
🧭 Our ask
Please investigate:
• How tokens are being calculated internally
• Whether prior instructions or tool metadata are accumulating or duplicated
• Whether a full LLM call payload (visible to us) could be exposed for debugging
We’re fully prepared to assist with debugging this issue – but at the current rate, token usage (and therefore pricing) is non-viable for production-grade deployments.DNAngelX
07/29/2025, 10:12 PMChiranjeet Mishra
07/30/2025, 10:33 AMDNAngelX
08/06/2025, 8:41 AMChiranjeet Mishra
08/06/2025, 8:01 PMDNAngelX
08/14/2025, 8:55 AMChiranjeet Mishra
08/15/2025, 6:53 AMDNAngelX
09/01/2025, 12:40 PM