Dwellir CLI Docs | API Keys, Endpoints, and Usage

Install and use the Dwellir CLI to manage API keys, discover endpoints, and monitor usage from your terminal or CI pipeline.

The Dwellir CLI (dwellir) gives you full access to the Dwellir platform from the command line. Authenticate, manage API keys, discover 150+ blockchain endpoints, monitor usage, and inspect error logs -- all without leaving your terminal.

It is built for three audiences:

Developers who prefer terminal workflows over a web dashboard
CI/CD pipelines that need to provision and rotate API keys automatically
AI agents that consume structured TOON/JSON output

Quick start

Bash

# Install
curl -fsSL https://raw.githubusercontent.com/dwellir-public/cli/main/scripts/install.sh | sh

# Authenticate
dwellir auth login

# List your API keys
dwellir keys list

# Discover Ethereum endpoints
dwellir endpoints search ethereum

Also available via Homebrew, AUR, go install, or from source.

Output modes

Every command supports multiple output modes:

--human -- formatted tables and key-value displays (default in interactive terminals)
--json -- JSON wrapped in a standard {ok, data, meta} envelope for scripting and automation
--toon -- TOON format (structured text)

In auto-detected non-interactive/agent environments (for example non-TTY runs, Codex, and Claude agent runs), the CLI defaults to TOON when no explicit output config exists. Use --json for strict machine pipelines (especially jq-first scripts), or set dwellir config set output json to make JSON your default.

Bash

dwellir keys list --json

JSON responses use a consistent envelope:

JSON

{
  "ok": true,
  "data": { ... },
  "meta": {
    "command": "keys.list",
    "timestamp": "2026-02-26T12:00:00Z"
  }
}

Errors return ok: false with an error code, message, and optional help text, plus a non-zero exit code.

Benchmark note (JSON vs TOON for agents)

A local benchmark run (Codex + Claude, 8 total runs) showed:

Equal correctness (4/4 pass in both JSON and TOON variants)
Lower interaction overhead with TOON (~24% fewer tool calls)
Lower output-token footprint with TOON (~36.5% fewer output tokens)

Details: 2026-03-03 JSON vs TOON benchmark

TOON is not always the right choice. See:

Command overview

Command	Description
`dwellir auth`	Login, logout, check status, print tokens
`dwellir keys`	Create, list, update, enable, disable, and delete API keys
`dwellir endpoints`	Browse and search 150+ blockchain endpoints
`dwellir usage`	View billing-cycle summary, usage by endpoint/method, costs, and RPS
`dwellir logs`	Inspect error logs, stats, and facet aggregations
`dwellir account`	View organization info and subscription details
`dwellir docs`	List, search, and fetch Dwellir documentation as markdown
`dwellir config`	Get and set CLI configuration values
`dwellir completion`	Generate or install shell completions (bash, zsh, fish, powershell)
`dwellir update`	Self-update to the latest release
`dwellir version`	Print build and version metadata

Global flags

These flags work on every command:

Flag	Description
`--json`	Output as JSON
`--human`	Output as human-readable tables (default in interactive terminals)
`--toon`	Output as TOON format (auto-selected in non-interactive/agent mode)
`--profile <name>`	Use a specific auth profile
`-q`, `--quiet`	Suppress non-essential output
`--anon-telemetry`	Anonymize telemetry data

Run dwellir --help or dwellir <command> --help for full usage details.

Next steps

Installation -- five ways to install the CLI
Authentication -- browser login, CI tokens, and profiles
API Keys -- create and manage keys
Endpoints -- discover blockchain networks
Usage & Logs -- monitor requests and debug errors
Configuration -- profiles, environment variables, and per-project settings
Agent Tooling -- migration prompt, agent skills, and documentation endpoints for AI agents