9Router ×ばつ B.AI Auto Setup

9Router's web dashboard normally requires a browser login, and wiring a custom OpenAI-compatible provider by hand means clicking through the UI. This script does it via 9Router's internal CLI API — no browser login, no SQLite surgery, no process restart. The provider appears on the dashboard and is immediately routable.

It is idempotent: run it once, run it ten times — it detects what already exists and skips it.

1. Derives the CLI token from ~/.9router/machine-id + ~/.9router/auth/cli-secret (the same mechanism the 9router CLI uses).
2. Creates a provider node (openai-compatible type) pointing at https://api.b.ai/v1 — or reuses it if one with the same prefix already exists.
3. Creates a provider connection with your B.AI API key — or skips it if already connected.
4. Tests the connection against the first model in the list.
5. Registers models (deepseek-v4-flash, deepseek-v4-pro by default) into the dashboard's Available Models.
6. Verifies that models appear on the router's /v1/models under your prefix.

• Linux with bash 5+, curl, sha256sum, python3
• A running 9Router instance (http://127.0.0.1:20128 by default)
• Read access to the 9Router data directory (~/.9router, root or the user that runs 9Router)

git clone https://github.com/<you>/9router-bai-setup.git
cd 9router-bai-setup
./setup.sh --api-key sk-your-bai-key

--api-key is your B.AI API key — created at the B.AI dashboard (https://api.b.ai), format sk-.... It is the upstream key for the provider being registered.

It is not:

• the 9Router API key / "Default Key" — that's the key apps use to talk to 9Router's /v1; the script never needs it
• any Hermes / OpenAI / other key

The script additionally needs read access to ~/.9router/machine-id and ~/.9router/auth/cli-secret to derive 9Router's internal CLI token — run it as root or as the same user that runs 9Router.

./setup.sh --api-key sk-xxx \
 --models deepseek-v4-flash,deepseek-v4-pro,glm-5.2 \
 --name "B.AI" --prefix bai

• Never restarts 9Router — all changes go through the HTTP API of the already-running process.
• Dry-run first: ./setup.sh --api-key sk-xxx --dry-run shows exactly what will happen.
• No secrets are logged — the API key is only sent over the local HTTP call.

MIT

This project is not affiliated with B.AI or 9Router. Use at your own risk — always dry-run in a test environment first.