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

How to find out why an LLM call failed or cost too much with Antirion

Read the route, status, tokens and cost of any request in the request log.

Who it is forA developer on call when an AI feature returns errors or an unexpected bill.

The problemWithout per-request records, it is hard to tell which model, key or route handled a failing or expensive call.

The outcomeThe developer finds the exact request, the route taken and the cost, and can reproduce it in the Playground.

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 if it is not already running.
  2. Open Request log in the console and filter or scan for the failing request by status, Model or key.
  3. Select the request and read its route taken, tokens, latency and cost in the details view.
  4. Open the Playground and resend a similar request to check whether the problem repeats.

Prompt for your agent

Using the eliasbiondo/antirion README, find the request in the Request log that matches <request description> and report its status, Model, key, tokens, latency and cost. Expected output: a short summary of that request. Verify that the reported values match the request details in the console.

Caveat. The request log only holds requests the gateway has handled, so calls that bypass the gateway will not appear.

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