The console at noket.dev is where you turn what the connector exposes into something your applications can call: models, API keys, sharing, budgets, usage, and logs.
| Page | What it is for |
|---|---|
| Models | Create a model backed by an external API or by an upstream on one of your nodes. |
| API keys | Issue keys for your applications and SDKs. |
| Usage | Cost, requests, tokens, latency, and per-model totals. |
| Logs | Individual requests, with status, model, and timings. |
| Tunnel → Nodes | The machines running noketd, and whether they are connected. |
| Tunnel → Upstreams | What each node is serving. |
| Account | Your email, verification, and active sessions. |
Models and sources
A model is the thing you call with an API key. It has a source:
- External API — Noket forwards to an API you configure in the console.
- Tunnel node — Noket forwards through the tunnel to an upstream on one of your machines.
Tunnel models are the ones this documentation mostly covers, because they depend on the CLI and the connector. External API models need no software on your side.
How the pieces fit together
noketdconnects this machine to Noket and exposes the model ids from its upstreams.- The console sees the node and the models it can serve.
- You create a model in the console that points at one of those upstream models.
- You issue an API key and call the model with it.
The CLI manages steps 1 and 2. The console manages steps 3 and 4.