Aiberm Auth
magpie / OpenCode provider plugin for Aiberm: one API key, each model on its native API (Anthropic Messages, OpenAI Responses, Gemini, Chat Completions)
0
0
20.0
Multi-signal model
22 hours ago
2026-10-20
Install and configure
opencode.jsonWrites to this project's opencode.json — applies to this repository only.
opencode.json
{
"$schema": "https://opencode.ai/config.json",
"plugin": ["aiberm-auth@0.1.1"]
}Writes to ~/.config/opencode/opencode.json — applies to every project.
~/.config/opencode/opencode.json
{
"$schema": "https://opencode.ai/config.json",
"plugin": ["aiberm-auth@0.1.1"]
}If you want to modify the plugin locally, install it into the project and reference the local path.
shell
pnpm add -D aiberm-authOpenCode loads npm dependencies through its embedded runtime on startup and caches them locally — no manual global install needed.
A magpie / OpenCode provider plugin for Aiberm. You sign in with one Aiberm API key, and each model is sent on its native API, so magpie converts a request only when the agent speaks a different API.
| Models | API | Endpoint |
|---|---|---|
| Claude | Anthropic Messages | https://aiberm.com/v1/messages |
| Gemini | Gemini | https://aiberm.com/v1beta/models/<id>:streamGenerateContent |
| GPT | OpenAI Responses | https://aiberm.com/v1/responses |
| Others (DeepSeek, Grok, Qwen, Kimi…) | Chat Completions | https://aiberm.com/v1/chat/completions |
The API for each model is picked from the supported_endpoint_types field in Aiberm's /v1/models. Grok and DeepSeek stay on Chat Completions, because Aiberm doesn't serve Responses for them.
Install
In magpie's window: Plugins → search aiberm → Install, then sign in with your Aiberm API key.
Or from the command line:
magpie plugin add aiberm-auth # from npm
magpie plugin login aiberm # asks for your own Aiberm API key
magpie provider test aiberm claude-opus-5-5
Each person signs in with their own key. The plugin holds no key; magpie keeps it on your machine.
Models are named aiberm/<model>, for example aiberm/claude-opus-5-5.
What it does
- Sign-in: one API key, stored by magpie in
~/.config/magpie/plugin-auth.json(mode 600). - Models: read from the key's
/v1/models. Embedding, image, speech and OCR models are left out. Context and output limits come from the vendors' published numbers, and Aiberm may cap below them. - Reasoning levels: Claude
low…max, GPTnone…xhigh, Geminilow/medium/high, otherslow/medium/high. - Usage:
magpie quotashows what the key has spent (New API's/api/usage/token/).
Tests
bun test
Similar plugins
Magpie Tokener
@tokener-ai/magpie-plugin-tokener
Tokener.ai provider plugin for OpenCode and magpie: API key sign-in, model discovery, Chat and Messages
Opendesign Auth
opencode-opendesign-auth
OpenCode provider plugin: Open Design Cloud (Design Plan, Vela/AMR)
Magpie
@d-ai/magpie
D.AI (dai.itbug.shop) models in magpie and OpenCode: one ddsk_ API key, chat models from the public catalog, per-key usage