Magpie Setup

This guide shows how to add Aiberm as a provider in magpie. After you add it once, Claude Code, Codex, Gemini CLI, OpenCode, and the other agents magpie supports can all pick models from Aiberm.

magpie is an open-source gateway that runs on your machine (by default at 127.0.0.1:3425). It speaks the OpenAI, Anthropic, and Gemini APIs and translates among them, including streaming and tool calls. Agents talk only to magpie. Your Aiberm API key stays in magpie; the agents’ config files get the address of the local gateway and a local token instead.

Prerequisites

• An Aiberm account (sign up)
• An Aiberm API key (create one)
• magpie 0.1.8 or later (import links need it)

Downloads for macOS, Windows, and Linux are on the download page. On macOS or Linux you can also install from a terminal:

curl -fsSL https://usemagpie.ai/install.sh | sh

On Linux the script installs the desktop app when GTK 3 and WebKitGTK 4.1 are present, and the terminal build otherwise. If the download cannot reach GitHub, pass a proxy: curl -fsSL https://usemagpie.ai/install.sh | sh -s -- --proxy http://127.0.0.1:7890.

Aiberm endpoints

Fill in both the Chat and the Anthropic URL. Claude Code’s requests go to the Anthropic URL unchanged, and magpie sends Claude models from other agents there too. Other requests go to the Chat URL, translated when the agent speaks a different API. Aiberm accepts both protocols for its chat models.

Leave the Responses and Gemini URLs empty. Aiberm’s Responses (/v1/responses) and Gemini (/v1beta) endpoints do not serve every model; Claude models, for example, are not available through them. Without those URLs, magpie translates Codex’s Responses requests and Gemini CLI’s requests itself, so Codex and Gemini CLI can use any Aiberm model.

Option 1: import link (recommended)

On a machine where magpie is installed, open the link below. magpie shows a confirmation dialog with the provider name, its endpoints, and a field for your API key, and warns you which hosts your prompts and key will be sent to. Nothing is saved until you press Add.

Add to magpie

The link intentionally has no API key. A public page should never carry a secret; paste your own key in the dialog. The key is stored only in ~/.config/magpie/providers.json on your machine, readable by your user alone. The web link keeps its parameters after #, and browsers never send that part to the server.

Without a desktop (for example over SSH), pass the same parameters to the terminal build. It shows the same summary and asks before adding:

magpie import 'magpie://import?name=Aiberm&id=aiberm&chat=https%3A%2F%2Faiberm.com%2Fv1&anthropic=https%3A%2F%2Faiberm.com&website=https%3A%2F%2Faiberm.com&keys=https%3A%2F%2Faiberm.com%2Fconsole%2Ftoken'

Option 2: add it in the app

1. Open magpie, go to Providers, and press ＋ Add provider.
2. Choose Custom (any compatible URL). magpie has no Aiberm preset.
3. Fill in the form:

4. Save. magpie requests https://aiberm.com/v1/models and offers the returned models in every agent’s picker. Before saving, Fetch models lets you pick which ones agents see, and Test models checks the key and URLs.

With Models empty, the list comes from /v1/models, so models Aiberm adds later show up when you fetch the models again (or run magpie provider refresh aiberm). The list includes every model your key can use, among them image, speech, and embedding models that coding agents cannot use; pick only the ones you need. Set a comma-separated list only when the automatic list is wrong. Model ids are listed on the pricing page and in the Models List, for example claude-sonnet-5-5, gpt-5.6-sol, or google/gemini-3.1-pro.

Pick a model for each agent

Open Agents. Each row is an agent installed or configured on this machine. Click the model, choose one under aiberm, or type aiberm/ plus a model id.

magpie claude aiberm/claude-sonnet-5-5
magpie codex aiberm/gpt-5.6-sol
magpie opencode aiberm/claude-sonnet-5-5
magpie gemini aiberm/google/gemini-3.1-pro

magpie changes only the keys it owns. Comments, ordering, and indentation in the agent config are left as they are. A session that is already running keeps the model it started with. Start a new session to pick up the change. For Codex, also restart the Codex app, because it builds its model list at startup.

To go back, pick one of the agent’s own models, or run magpie claude default (replace claude with the agent name). magpie removes what it wrote and restores the values it replaced.

If you already connected an agent to Aiberm directly

You do not need to export ANTHROPIC_BASE_URL or OPENAI_BASE_URL for magpie; it writes the gateway address into each agent’s own config.

• Claude Code or Codex configured in its config file (as in the Claude Code guide and the Codex guide): nothing to do. magpie replaces only the values it needs, and magpie <agent> default puts yours back.
• Claude Code configured with export, setx, or Windows user environment variables: you can leave them. Claude Code gives the values in ~/.claude/settings.json precedence, so magpie’s settings win while you use it. After magpie claude default, Claude Code falls back to your variables and talks to Aiberm directly.

While you use it

• magpie has to be running. Closing the window leaves it in the menu bar or system tray. magpie tray starts the icon only, and magpie serve runs just the gateway. To start it at login without a window, run magpie daemon install on macOS or Linux, or magpie autostart on on Windows.

• Add the key only in magpie. magpie does not read API keys from your shell environment.

• A proxy app (Clash, Surge, mihomo, and similar tools, with system proxy, TUN, or enhanced mode on) can intercept traffic to 127.0.0.1:3425. If an agent returns 502 and the request never appears on magpie’s Routing tab, add rules that send local addresses direct, ahead of your other rules:

  IP-CIDR,127.0.0.0/8,DIRECT,no-resolve
  IP-CIDR6,::1/128,DIRECT,no-resolve

  In a Clash or mihomo config, put the same lines under rules:, each starting with - .

• The Usage tab counts only calls that go through the gateway. Calls an agent makes straight to Aiberm are not included. Unless you set your own prices or a price rate for the provider, magpie estimates cost at the model makers’ list prices, which can be well above what Aiberm charges. Your actual bill is on the Aiberm console.

Optional: several keys or a fallback

All API keys of one Aiberm account draw from the same balance. When the balance runs out, every key of that account fails at once, so more keys from the same account are not a fallback for running out of credit. Several keys help when they come from different Aiberm accounts, or when a key has its own quota limit set in the console and you want the next key to take over once it is used up.

To use several keys, paste them into the Aiberm provider’s API key field, separated by commas, spaces, or new lines. The first key is tried first. Then choose how requests are spread:

magpie moves to the next key on errors such as 401, 403, 429, and 5xx, as long as nothing has been sent to the agent yet. Least used first and Weekly pace are mainly for subscriptions; with keys they only compare recent token use. Every mode except Smart comes from magpie’s built-in rotation plugin; if only Smart is offered, turn that plugin on.

A more common setup is a fallback across providers: use a subscription first and Aiberm when it runs out. On the Routing tab, create a group with your subscription’s model first and the Aiberm model second, for example a Claude plan model followed by aiberm/claude-sonnet-5-5, and point the agent at group/<id>. When the first member is out of quota, rate limited, or down, magpie sends the turn to the next member before the error reaches the agent. magpie also creates group/auto-<model> on its own when two of your providers serve the same model.

Recover and troubleshoot

For other error codes, see Error Handling. magpie’s own documentation is at Get started and Add to magpie.