# CLI Reference

> **This page has moved.** The canonical CLI documentation is now at [CLI & Chain Binary](/for-developers/cli.md).

The CLI surface is flat verb-first — every command lives at `bb <verb>`. The previous `bb cli <subcmd>` infix is deprecated and prints a stderr banner during the migration window; the release after the window removes it. See the [overview](/for-developers/cli.md#deprecation-runway--the-old-bb-cli-and-standalone-names-still-work) for the full mapping. Start here:

* [**Installation**](/for-developers/cli/installation.md) — install the chain binary + Node CLI in one shot
* [**Build Commands**](/for-developers/cli/build-commands.md) — flag-based generators (`build vault`, `build subscription`, `build bounty`, …)
* [**Analysis Commands**](/for-developers/cli/analysis-commands.md) — `check` (validate / review / verify folded), `explain`, `simulate`, `preview`
* [**Deploy Commands**](/for-developers/cli/deploy-commands.md) — `deploy --burner` for the keyless faucet path
* [**Tool Commands**](/for-developers/cli/tool-commands.md) — fine-grained MCP `tool` / `tools` registry, persisted `session`, static `resources`
* [**Utility Commands**](/for-developers/cli/utility-commands.md) — `docs`, `skills`, `address`, `alias`, `lookup`, `gen-list-id`, `doctor`
* [**API Commands**](/for-developers/cli/api-commands.md) — 104+ indexer routes
* [**Auth Commands**](/for-developers/cli/auth-commands.md) — wallet-agnostic SIWBB sessions
* [**Chain Commands**](/for-developers/cli/chain-commands.md) — `bitbadgeschaind` keys, transactions, queries
* [**CLI for AI Agents**](/for-developers/cli/for-ai-agents.md) — agent workflows and automation patterns


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bitbadges.io/for-developers/bitbadges-sdk/cli.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.