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

How to send every app's LLM calls through one endpoint with Antirion

Run one gateway that forwards OpenAI-style requests to your provider keys.

Who it is forA developer or small platform team whose apps call OpenAI or Anthropic directly and who wants one place to manage providers and keys.

The problemEach app holds its own provider keys and code paths, so switching models or providers means changing every app.

The outcomeApps call one base URL with a gateway key, and the model behind the name chat can be changed in the console.

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. Run docker run -p 8080:8080 -p 8081:8081 -v antirion-data:/var/lib/antirion eliasbiondo/antirion and copy the admin token printed on the first start.
  2. In the console at http://localhost:8081/ui/, open Providers, choose Add provider, paste your API key, run Test, then Add provider.
  3. Open Models, choose Add model, pick a model from the provider's list, name it chat, and click Add model.
  4. Open API keys, choose Create key, name it for your app, and copy the key, which is shown only once.
  5. Set your SDK base URL to http://localhost:8080/v1 and send a chat request with model chat.

Prompt for your agent

Using the eliasbiondo/antirion README, configure the OpenAI SDK in <project path> to use base URL http://localhost:8080/v1 and the gateway key in ANTIRION_API_KEY, then send a chat request with model chat. Expected output: a chat completion JSON response. Verify that the request appears in the Request log in the console.

Caveat. The README's getting-started path needs an OpenAI or Anthropic key, and other providers are set up the same way only where the console offers them.

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