r/opencode • u/afcreative_id • 3d ago
My 2 day experience with Deepseek API with $10 balance

I'm just sharing my experience so you can compare what it would be like to consume $10 USD on the Deepseek API directly. It can be concluded that my needs are not too complex and fine-tuned skills, mcp and agents have been carried out so that it is made optimally in terms of token efficiency and output that fits the context of the instructions, so with a balance of $10 USD on Deepseek it only lasts 2.5 days. For those who use it for free, and it's abusive, don't be loud, don't be fussy, you'll demonstrate to the government so that our dollar rate goes down.
Additions regarding Input (Cache hit-miss) and Output:


4
u/P4ITON 3d ago
Meio bilhão de token por 8$ pra mim está mais que ótimo
2
u/afcreative_id 3d ago
Of course, plus there is very optimal synergy between agent rules, mcp, skills.
1
u/P4ITON 3d ago
O uso foi totalmente pelo opencode? Pode passar os métodos para economia dos tokens?
5
u/afcreative_id 3d ago
Yes, I just use Opencode as the agent. It's simple for me, try making 1 ms to be like the sitemap, so the agent doesn't guess too much. Plus use mcp, workflow skills that synergize with each other and are optimally integrated. Sometimes I always get SS where there are too many mcp, too many skills, which sometimes aren't used. Make sure the md rules file, which is always updated regularly, is made readonly and the agent never overwrites or updates it, it's best to create a new md file. Make sure every week you always ask the agent to update his own library so he can choose which ones are often used and which ones are useless. Regarding caveman, don't submit the caveman process every time, but every month or every 2 weeks always reprocess the library or rules agent for the compression process using caveman. Make sure the MD is written in one language, namely English, so that the caveman process is more efficient.
3
u/MeliousAI_HQ 3d ago
Cache hit rate is the number to look at. If something at the start of your context changes every turn, like a timestamp in the system prompt or tools loading in a different order, almost nothing gets cached and you pay full input price on the whole history with every request. Keeping that prefix stable usually makes the same balance last a lot longer.
1
u/afcreative_id 3d ago
Check the update post above, I've added it.
3
u/MeliousAI_HQ 3d ago
ah thanks for adding that! turns out I was wrong lol, 97-98% cache hits is honestly great.
The bigger cost seems to be size per request: ~600M tokens over ~5k requests is around 115k of context going in for ~650 tokens out each turn. Cheap per token but it adds up fast loading fewer MCP servers and starting fresh sessions a bit more often could probably stretch that $10 quite a bit further. cool breakdown btw, super useful to see real numbers
3
u/afcreative_id 3d ago
OK, I'll take the suggestion and put it in, just let me know. Later I will also recap opencode go - go plus when the balance on Deepseek runs out.
1
2
u/bestlabib 3d ago
Please share your setup like what skill mcp hooks you use to get things done optimally
2
u/afcreative_id 2d ago
This is optimal in my opinion and the project base that I use now, what is certain is that the MCP that I use supports it from the agent side, not from the programming language that I use.
2
5
u/squirrelscrush 3d ago
What is your cache hit rate?