Documentation
Everything needed to install Nib, connect a tool, and understand what you are charged.
Start here
Quickstart →
Install, sign in, run your first task. Two minutes.
External tools →
Use one key in Cline, Continue, Zed, or any SDK.
API reference →
Protocols, base URLs, headers, error shapes.
CLI commands →
Every command, flag, and exit code.
How Nib is put together
Nib ships as three pieces that share one account: the desktop app, the command line, and the gateway your requests are routed through. The desktop app is the main product; the CLI and the API exist so the same plan works from a terminal, an editor, or a script.
- One sign-in. A device-code flow turns a browser approval into a local credential — no key to copy, no password to paste.
- One key. The
Defaultkey created with your account is what the desktop app uses. The same key works in Cline, Continue, Zed, and any OpenAI-compatible SDK. - One bill.
nib status, the desktop status bar, and the console all read the same entitlement: credits included, credits used, and when the window resets. - Every model. Plans differ by allowance and concurrency, never by which model families you may call.
What lives where
| Piece | Where | Licence |
|---|---|---|
| Desktop app and CLI | github.com/secretkeyllc/nib | LGPL-3.0 |
| Gateway, billing, model routing | Operated by Secret Key LLC | Proprietary |
| This site and the console | Operated by Secret Key LLC | Proprietary |
Credits in one paragraph
Ten credits equal one dollar of model usage. Every plan includes a monthly credit allowance. Every response reports the credits it charged and the credits remaining. If a request's cost would exceed your remaining balance, it is rejected before it runs, with a 402 error that names the shortfall.