Guide
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.
Desktop, CLI & scripting →
What ships, how to sign in, and how to call the gateway from a script.
Configuration →
Data directory, environment variables, providers, remote hosts.
How Nib is put together
Nib is a desktop application plus a gateway. The desktop is the product: chat, projects, scheduled tasks, plugins, MCP, voice, and remote machines. The gateway is the OpenAI-, Anthropic- and Gemini-compatible endpoint behind it, so the same account and the same credits also work from an editor or a script.
- One sign-in. A device-code flow turns a browser approval into a credential kept in the OS keychain — no key to copy, no password to paste.
- One key. A key from the console works in Cline, Continue, Zed, or any OpenAI-compatible SDK, and bills the same credits.
- One bill. The composer status bar and the console 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 nib-host | 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 credit allowance with weekly and daily caps. Usage is recorded per request and shown in the app and the console. When the balance is exhausted the gateway rejects new requests with a 402 rather than letting the account run negative.