đź’¸ Do you track how much you spend on AI?
by•
I opened our invoices this morning... and closed them right away hehe
Claude Max for the whole team, the API on top for our agents, a few other tools here and there...
It adds up so fast!
And the funny part is that a lot of it is the same thing paid twice. Two of us asking our agents to read the same repo, the same files, the same context.
That's actually one of the reasons we started building Murmell :)
So I'm curious:
Do you track your AI spending?
Do you have a budget for it?
Or do you just close your eyes when the invoice comes?..
50 views
Replies
yeah i just dont look too closely, between claude code and a couple apis it's probably more than my actual app revenue some months lol
@jaewon_seo more than the app revenue, that hurts hehe... Is it mostly Claude Code or the APIs? And are you building solo or with a team?
For the AI inside the product, yes, per request rather than per invoice. Every flashcard generation costs the user one credit, and if the model returns nothing usable the credit goes back. That forces you to know what a single call costs, because you're the one eating it when it fails.
The invoice view hides that. A monthly total going up could mean more users or a model getting worse at your task, and those need opposite fixes.
@hamanovich love the credit going back when the model fails, that keeps you honest! And you're right, the invoice hides everything... Do you also track it per model? Like when you switch models, do you see the cost per flashcard change a lot?
@moss_ab_mirande_ney Not on a dashboard, honestly. I measure it when I switch, then stop looking until the next switch
Moving to the newer cheap tier roughly halved the per-card cost on the default path, so the switch paid for itself before I'd even checked quality.
The surprise was the opposite direction though. Pairs where neither language is English go to the expensive model, because the cheap one got translations wrong noticeably more often there. So the cost per flashcard depends more on the language pair than on volume.
@hamanovich wait that's such a good insight, the language pair matters more than the volume! Do you route it automatically or did you hardcode which pairs go to the expensive model?
@moss_ab_mirande_ney Hardcoded. One rule: if neither language is English, it goes to the expensive model. No per-pair list, no runtime routing.
It came out of evals, not intuition. I run a sample of hundreds generated cards past a separate model acting as a judge, and the non-English pairs kept failing on meaning far more often than anything with English on one side.
Spanish to Portuguese probably doesn't need the expensive tier, Bengali to Japanese definitely does, and both get the same treatment. I'd rather pay a bit too much on the easy pairs than ship a wrong translation to someone who can't spot it yet.
the same repo read twice by two people seems like the real leak here. a monthly invoice wont show that, id guess per task tracking would. does murmell flag that overlap while its happening?
@hitensethiya exactly, the invoice never shows it... In Murmell the agents work in the same shared context, so the repo doesn't get read twice, and you see live what each agent is doing. How do you track it today, per task or not at all hehe?