Live data from Hacker News

LLMCap – A proxy that hard-stops LLM API calls when you hit a dollar cap

llmcap.io

21–25 of 25 posts

Re: LLMCap – A proxy that hard-stops LLM API calls when you hit a dollar cap

#21

LiteLLM already provides this feature, no need of another proxy

i did try litellm hosted locally for privacy.

it was so bugged, the mcp page broke its postgres, many openai compatible type generic providers but not knowing what works. discovered logging was truncated by default, too late. my fault for that last one.

moved off it after the trivy incident.

Re: LLMCap – A proxy that hard-stops LLM API calls when you hit a dollar cap

#22
I've got a local one you can to do this for free with through openrouter

Even has a GUI.

$ uvx capit serve

https://github.com/day50-dev/limit-model-spending

* Free to use

* Everything is stored local.

* Anthropic skills are included for easily extending it to additional tools or providers.

Please ask for features or file bugs. Thanks!

Btw, I'm terrible at marketing even when I'm giving stuff away.

Re: LLMCap – A proxy that hard-stops LLM API calls when you hit a dollar cap

#23
post #6

We self-host LiteLLM which allows to set the budget per day/week, and it's free.

LiteLLM is a great option if you're comfortable running infrastructure. LLMCap is for teams who want enforcement without self-hosting or maintenance overhead.

Re: LLMCap – A proxy that hard-stops LLM API calls when you hit a dollar cap

#24
post #8

Proxying == Logging suspicions guard-sdk does the same locally https://guard-sdk.js.org

Valid concern. Your provider API key is never stored — it passes through as a header on each request and is discarded immediately. LLMCap only stores token counts and costs per request. No key retention.
Post reply on HN