DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to cap LLM spend per team, project or key with Antirion

Set dollar or token budgets and get alerts before a budget runs out.

Who it is forA team lead or finance-minded engineer who shares LLM access across teams and needs spend limits before the bill arrives.

The problemShared provider keys let one project spend far more than planned, and the cost is only visible after the invoice.

The outcomeEach project uses its own key with a budget, and the cost ledger shows what each model call cost.

What you need first

  • Docker installed on the machine that will run the gateway
  • An API key from OpenAI or Anthropic
  • A web browser to open the console at http://localhost:8081/ui/

Steps

  1. Start the gateway with docker run -p 8080:8080 -p 8081:8081 -v antirion-data:/var/lib/antirion eliasbiondo/antirion.
  2. In the console, open API keys and choose Create key once for each project, naming each key after its project.
  3. In the console, open the budget settings for the key, team or project and set a limit in dollars or tokens. (inferred, check the README)
  4. Check that the Model price fields match your provider prices, since the list price applies when they are left blank.
  5. Open Request log, select a request, and review its cost in the cost ledger.

Prompt for your agent

Using the eliasbiondo/antirion README, create one gateway key per project and set a dollar budget on each key in the console. Expected output: a list of keys with their budgets. Verify that a test request from one key shows its cost in the cost ledger.

Caveat. The README names where budgets apply but not the exact console menu, so the budget step needs to be checked in the running console.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page