# qn — Quicknode CLI
`qn` is a command-line interface for Quicknode, built around noun-verb commands that read naturally for both humans and agents. Manage endpoints, streams, webhooks, the KV store, teams, usage, and billing, with output in multiple formats for easy reading or scripting.
```
$ qn endpoint list
ID LABEL STATUS CHAIN/NETWORK TYPE MULTI
ep-1 production active ethereum/mainnet shared yes
ep-2 — paused solana/mainnet dedicated no
showing 1–2 of 2
$ qn endpoint list --wide
ID LABEL STATUS CHAIN/NETWORK TYPE MULTI HTTP WSS
ep-1 production active ethereum/mainnet shared yes https://ep-1.example —
ep-2 — paused solana/mainnet dedicated no https://ep-2.example —
showing 1–2 of 2
# Piped / non-TTY output defaults to JSON
"data": [
{
"id": "ep-1",
"name": "ep-1",
"label": "production",
"status": "active",
"chain": "ethereum",
"network": "mainnet",
"is_dedicated": false,
"is_flat_rate": false,
"http_url": "https://ep-1.example",
"wss_url": null,
"tags": ["prod", "eu"],
"is_multichain": false
},
{
"id": "ep-2",
"name": "ep-2",
"label": null,
"status": "paused",
"chain": "solana",
"network": "mainnet",
"is_dedicated": true,
"is_flat_rate": false,
"http_url": "https://ep-2.example",
"wss_url": null,
"tags": [],
"is_multichain": false
}
],
"pagination": { "total": 2, "limit": 20, "offset": 0 },
"error": null
}
```
## Installation
Pick the recommended path for your platform. Other channels are listed under [Alternatives](#alternatives).
### Homebrew (macOS)
```sh
brew install quicknode/tap/qn
```
Homebrew installs shell completions automatically — open a new shell after
install and `qn <TAB>` works. zsh users may have one extra requirement: zsh only
autoloads a completion when its directory is on `$fpath` before `compinit` runs
at shell startup. If `qn <TAB>` lists files instead of subcommands, the Homebrew
completions directory is missing from `$fpath` — see the
[zsh completion-system manual](https://zsh.sourceforge.io/Doc/Release/Completion-System.html).
### Scoop (Windows)
```powershell
scoop bucket add quicknode https://github.com/quicknode/scoop-bucket
scoop install quicknode/qn
```
### `.deb` (Debian, Ubuntu)
Each GitHub release attaches a `.deb` per architecture. These canonical URLs always point at the latest release — check your architecture with `dpkg --print-architecture` and pick the matching one:
```sh
# amd64 (Intel/AMD)
curl -LO https://github.com/quicknode/cli/releases/latest/download/qn_amd64.deb
sudo apt install ./qn_amd64.deb
# arm64
curl -LO https://github.com/quicknode/cli/releases/latest/download/qn_arm64.deb
sudo apt install ./qn_arm64.deb
```
Versioned files (`qn_<VERSION>_amd64.deb`) are also attached to each release for pinning.
### Arch Linux (AUR)
```sh
yay -S qn-bin # or any other AUR helper
```
### Fedora, EPEL (COPR)
```sh
sudo dnf copr enable quicknode/qn
sudo dnf install qn
```
### Docker (GHCR)
```sh
docker pull ghcr.io/quicknode/qn:latest
docker run --rm ghcr.io/quicknode/qn:latest --help
```
### Alternatives
<details>
<summary>crates.io, from source, prebuilt binaries</summary>
**crates.io:**
```sh
cargo install quicknode-cli
```
The crate name is `quicknode-cli` but the installed binary is `qn`.
**From source:**
```sh
git clone git@github.com:quicknode/cli.git && cd cli
cargo install --path .
```
**Prebuilt binaries:** every GitHub release attaches per-platform archives — see the [latest release page](https://github.com/quicknode/cli/releases/latest).
</details>
## Authentication
You will need a Quicknode API key to get started. Once you have that, you can run `qn auth login`
`qn` resolves your API key from the first source that matches:
1. `--api-key <KEY>` flag
2. The config file: the `--config-file <PATH>` flag if given, otherwise
`~/.config/qn/config.toml` — or `$XDG_CONFIG_HOME/qn/config.toml` if that
env var is set. The same layout applies on Windows:
`%USERPROFILE%\.config\qn\config.toml`. Managed by `qn auth login`.
If no source matches, `qn` exits with code 4 and tells you to run
`qn auth login`.
```sh
qn auth login # prompts for the key, writes it to ~/.config/qn/config.toml
qn auth whoami # confirms the key works against the live API
qn auth logout # removes the saved key
```
## Output
Pick a format with `--format <FMT>` (alias `-o <FMT>`):
| `table` | Humans on a TTY. Pretty UTF-8 tables with optional color. Default when stdout is a terminal. |
| `json` | Scripts and pipelines (`jq`, `gron`, …). Default when stdout is **not** a terminal (piped / agent invocations). |
| `yaml` | Same shape as JSON, easier to skim by eye. |
| `md` | GitHub-flavored markdown — paste into PRs, issues, docs. |
| `toon` | [Token-Oriented Object Notation](https://github.com/toon-format/toon-rust) — compact serialization optimized for LLM prompts. |
Other output flags:
- **`-w` / `--wide`:** add extra columns to `table` and `md` output (e.g. HTTP/WSS URLs in `endpoint list`). Mirrors `kubectl get -o wide`. Doesn't affect `json`/`yaml`/`toon`, which always include everything.
- **`--no-color`:** plain ASCII (also honored: `NO_COLOR` env var, `TERM=dumb`, non-TTY stdout, any non-`table` format).
- **`--quiet`:** suppress state-change notes on stderr.
- **`--verbose`:** include API error bodies and other detail.
You can also set defaults in `~/.config/qn/config.toml`:
```toml
[output]
format = "yaml" # default --format value
wide = true # always show extra columns in table/md output
```
CLI flags win over config values. Built-in defaults: `format = "table"` when stdout is a TTY, `"json"` otherwise; `wide = false`.
`qn` follows the [Command Line Interface Guidelines](https://clig.dev/): data on stdout, diagnostics on stderr, meaningful exit codes (0 success, 2 API error, 3 network error, 4 auth/config, 5 needs confirmation), and a documented `-h`/`--help` at every subcommand level.
## Example usage
### Endpoints
```sh
qn endpoint show ep-1234
qn endpoint pause ep-1234
qn endpoint logs ep-1234 --from 1h --to now --limit 50
qn endpoint metrics ep-1234 --metric method_calls_over_time --period day
qn endpoint security set-options ep-1234 --tokens enabled --jwts disabled
qn endpoint rate-limit set ep-1234 --rps 100 --rpm 5000
qn endpoint archive ep-1234 --yes
```
### Streams
```sh
qn stream list --limit 20
qn stream create \
--name my-stream \
--network ethereum-mainnet \
--dataset block \
--start 24691804 --end=-1 \
--region usa-east \
--webhook https://webhook.site/abc \
--batch-size 1
qn stream activate s-1234
qn stream test-filter \
--network ethereum-mainnet \
--dataset block \
--block 17811625 \
--filter-file filter.js
qn stream delete s-1234 --yes
```
### Webhooks
```sh
qn webhook list
qn webhook create \
--name "wallet alerts" \
--network ethereum-mainnet \
--url https://webhook.site/abc \
--template evm-wallet \
--wallet 0xa0b8...
qn webhook create \
--name "uniswap events" \
--network ethereum-mainnet \
--url https://webhook.site/xyz \
--template evm-contract-events \
--contract 0x88e6...
qn webhook activate wh-1 --start-from latest
qn webhook pause wh-1
```
### KV store
```sh
qn kv set put my-key my-value
qn kv set ls
qn kv list create allowlist 0xabc 0xdef
qn kv list append allowlist 0x123
qn kv list contains allowlist 0xabc
qn kv list get allowlist
```
### SQL
```sh
# Run a query inline, from a file, or from stdin (--file -)
qn sql query "SELECT action_type, user FROM hyperliquid_system_actions ORDER BY block_time DESC LIMIT 3" --cluster-id hyperliquid-core-mainnet
qn sql query --file query.sql --cluster-id hyperliquid-core-mainnet
# Pipe rows into jq (stats print to stderr, so stdout stays clean)
# Inspect a cluster's tables, columns, and types
qn sql schema hyperliquid-core-mainnet
```
Queries are read-only (SELECT) and capped at 1000 rows per request; page through
larger result sets with `LIMIT`/`OFFSET` in the SQL.
### Other
```sh
qn usage summary --from 7d
qn usage by-endpoint --from 30d -o yaml
qn metrics account --period day --metric credits_over_time
qn chain list
qn chain credits ethereum
qn billing invoices
qn endpoint bulk pause ep-1 ep-2 ep-3
qn endpoint tag list
qn team list
```
## Shell completions
When installing qn through a package manager, it's possible that no additional
shell configuration is necessary — Homebrew (see above) and distro packages
place the script for you. To set up completions manually, follow the
instructions below (`qn completions --help` prints the same). Exact config file
locations may vary by system; restart your shell before testing.
### bash
Install `bash-completion` with your package manager, then add to `~/.bashrc`:
```sh
eval "$(qn completions bash)"
```
### zsh
Homebrew already creates this `_qn` file for you on `brew install`. To set it up
manually, generate the script into a directory on your `$fpath` (Apple Silicon
shown; Intel brew uses `/usr/local/share/zsh/site-functions`):
```sh
qn completions zsh > /opt/homebrew/share/zsh/site-functions/_qn
```
Ensure that the following is present in your `~/.zshrc`:
```sh
autoload -U compinit
compinit
```
See the [zsh completion-system manual](https://zsh.sourceforge.io/Doc/Release/Completion-System.html) for details.
### fish
```sh
qn completions fish > ~/.config/fish/completions/qn.fish
```
### PowerShell
Add this line to your profile script (`$PROFILE`):
```powershell
Or append the generated script so it loads each session:
```powershell
qn completions powershell >> $PROFILE
```
## Configuration via environment
The conventional variables are honored: `NO_COLOR` and `TERM=dumb` disable color,
and `XDG_CONFIG_HOME`/`HOME` (`USERPROFILE` on Windows) locate the default
config file. The CLI hands the key to the Quicknode SDK explicitly; it does
not read the SDK's `QN_SDK__*` environment namespace.
The hidden `--base-url <URL>` flag overrides the API host for all four
sub-clients at once (used for integration tests and on-prem mirrors).
## Confirmations
Destructive commands (`delete`, `archive`, `bulk pause`, token revocation,
removing a rate-limit override, …) prompt before acting, and the prompt states
what will happen ("Pause 3 endpoint(s)? They will stop serving requests").
Pass `--yes`/`-y` to skip the prompt. In scripts and CI (no TTY), a gated
command without `--yes` exits with code 5 **before** any request is sent.
The CLI deliberately has no account-wide wipe commands (no `delete-all`);
operations with that blast radius belong behind the API, not a one-liner.
## Retries
Read-only commands (`list`, `show`, `logs`, `metrics`, `usage`, …) retry
transient failures — HTTP 429, 500, 502, 503, 504, timeouts, and connection
errors — with exponential backoff and full jitter. The default is 3 retries;
tune it with the global `--retries <N>` flag (`--retries 0` disables).
`stream test-filter` retries too: it sends a POST, but only evaluates a
filter against historical data and changes nothing.
Commands that modify resources (`create`, `update`, `delete`, `pause`, …)
**never** retry automatically: a retried create could provision twice. If a
mutation fails with a transient error, check whether it took effect before
re-running it.
## Exit codes
| 0 | Success |
| 1 | CLI error (usage/bad argument, IO, decode) |
| 2 | API error (server returned 4xx/5xx) |
| 3 | Network failure (timeout, connect, transport) |
| 4 | Missing or invalid API key / config |
| 5 | Operation needs confirmation (pass `--yes`) |
| 130 | Interrupted (SIGINT) |
## License
MIT