CLI reference

The tenzro CLI is one binary for everyone on the network. Developers use it to create an account, chat with models and call any JSON-RPC method. Operators use it to set up a node, bond for a role, serve models and decide who may use the node. Every command talks to a node over JSON-RPC, and every command has --help with its full option list.

The complete reference, every command and flag, is generated from the binary: CLI.md. The node binary's own flags are in NODE.md.

For a read-only view of a node in the terminal, see the terminal console.

Install

Each release archive on the downloads page holds both tenzro and tenzro-node. To build from source:

cargo install --git https://github.com/tenzro/tenzro-network --bin tenzro

Check the install:

tenzro version
tenzro info

Endpoints and credentials

There are no API keys. Where a node's access policy asks callers to sign in, tenzro access sign-in signs with this machine's hardware key (TPM 2.0 or Secure Enclave) and stores a DPoP-bound access token that later commands present. TENZRO_DATA_DIR sets the node data directory for both the CLI and tenzro-node.

Join the network

# Guided setup: consume, provide or validate on Tenzro Network,
# bootstrap a local network, or join a private one
tenzro setup

# The same, non-interactive
tenzro setup --path network --mode provide --roles ai,storage --yes
tenzro setup --path local --network-name lab --yes
tenzro setup --path private --genesis ./genesis.toml --bootstrap did:tenzro:machine:<id>@<relay-url>

# One-step participation as a user, or as an inference provider
tenzro join --name "Ada"
tenzro join --provider

tenzro setup flags include --path network|local|private, --mode consume|provide|validate, --roles, --operator self|autonomous, --access on-demand,subscription,rental, --visibility, --machine-name, --validator-stake, --provision-tpm, --apply and --yes. Every path needs a TPM 2.0 or a Secure Enclave on the machine: node and account keys live in hardware. Setup checks the hardware root first and prints each unmet item with its fix; --provision-tpm creates the machine's TPM keys without asking, and --apply installs the node as a service, starts it and follows it until it has synced. Follow a running node with tenzro status --watch.

An operator who needs stake for a role can check and apply for sponsorship from the same terminal:

tenzro sponsor check
tenzro sponsor apply
tenzro sponsor status

See Sponsorship and grants.

A new account enrols its ML-DSA-65 key with tenzro pq-hybrid enroll before, or as, its first transaction; the CLI also does this automatically. See Cryptography.

tenzro join --provider detects your hardware, posts the compute bond, registers you as a provider, sets default pricing and serves the largest catalog model that fits your machine.

Who may use your node

tenzro access show                    # the policy in force, as access.toml
tenzro access set ./access.toml       # replace it
tenzro access preview ...             # what the policy decides for a caller
tenzro access tokens                  # live access tokens the node issued
tenzro access revoke ...              # withdraw one token, or every token of a DID

On the node itself, tenzro-node access is the same policy as a wizard (--preset open|closed|signed_in|agents_with_terms, --admin <did>). See RPC access.

Call any method

tenzro rpc methods --contains agent --rpc https://rpc.tenzro.com
tenzro rpc methods --namespaces
tenzro rpc call tenzro_getSupplyMetrics --rpc https://rpc.tenzro.com
tenzro rpc call tenzro_getBlock --params '{"height":"latest"}'

tenzro rpc methods prints each method with its access class (open, owner or admin). The methods themselves are documented in the JSON-RPC reference.

Command groups

Run tenzro <command> --help for the subcommands and flags of each group.