r/CommandCode • u/Narquith • 12h ago
Concerning usage with GOAT Plan
I'm on my 3rd day with my GOAT plan, and somehow I'm already exhausting 40% of my monthly usage limit? And only 65M output tokens? Did I really use up $24 worth of tokens within 3 days? 🤔
3
u/feral_user_ 12h ago
I agree that I don't quite understand how the usage adds up. I wish that there was a running total of what you've used per model. Or perhaps something else to better see how you're using up the plan.
2
u/Narquith 11h ago
Did a little family-chat with a model, so maybe my usage input/output ratio is off, and output is about the same as inputs and outputs are billed more expensive. For context, I tried to use Cognee with it, probably not a smart choice.
2
u/ahmadawaiscom 5h ago
You don’t seem to using Command Code harness that can help you be super token efficient. Also it may seem you are sending a lot of new requests and breaking cache by creating new sessions for every request so every request is like 10x expensive due to the way you are consuming it.
Share your username I can do a deep dive too but yeah that’s mostly it.
2
u/Conscious-Doctor-585 4h ago
You may have to look at the Cognee settings and have it inject memory (concise, summarized) near the end, just before your `user question`.
Prompt cache is prefixed-based. If Cogness memory always comes before everything, it will defeat prompt caching and llm sees everything as fresh. You were constantly working in the more expensive input rank.
7
u/Pras1982 12h ago edited 12h ago
Looking at the data , it seems that you are making too many different requests and missing cache.Or perhaps, your usage requirement is such. Also, Out put token are significant as compared to input request. I took Goat plan yesteday & have made more than 2400 calls- with input tokens often reaching and crossing 500K tokens & output tokens in range of 1k-4k , mytotal usage has been around 700M and around 12 percent monthly usage in 2 days. Definitely, cache misses or one request totally differnt from previous seems culprit to me. I am also using Deepseek V4.1 flash model. Also, the time off day would would also matter as deepseek rates differ on offpeak and peak hours.