Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Configuration

The Zora CLI stores configuration in ~/.config/zora/:

FileContentsPermissions
config.jsonAPI key, anonymous analytics ID, DM-check timestamp0600
wallet.jsonPrivate key (plain text), smart wallet & agent metadata0600
budget.jsonGlobal spending budget cap + ledger0600
session.jsonCached Privy session used by agent and DM commands0600

The private key in wallet.json is stored in plain text — it is protected by file permissions (0600, owner read/write only), not encryption. The files are versioned (version: 1) so the CLI can validate and migrate them. budget.json is created the first time you run zora agent budget set.

On Windows, the config directory is %APPDATA%\zora\ or ~\AppData\Roaming\zora\.

API Key

An API key is optional. Without one, read-only commands work but may be rate-limited.

Configure via CLI

npx @zoralabs/cli auth configure
# Prompts for your API key and saves to config.json

Configure via Environment Variable

export ZORA_API_KEY=your-key-here

The environment variable takes precedence over the config file.

Get an API Key

Generate one at zora.co/settings/developer.

Wallet

Trading commands (buy, sell, send, balance) require a wallet.

Create via CLI

npx @zoralabs/cli setup --create

Import via CLI

npx @zoralabs/cli setup
# Interactive prompt to paste a private key

Configure via Environment Variable

export ZORA_PRIVATE_KEY=0x...

The environment variable takes precedence over the wallet file. This is recommended for CI/CD, containers, and agent runtimes.

All Environment Variables

VariableDescription
ZORA_API_KEYAPI key (overrides config file)
ZORA_PRIVATE_KEYWallet private key (overrides wallet file)
ZORA_API_TARGETOverride API base URL (for dev/staging)
ZORA_PROFILE_APIOverride the profile/messaging API base URL (for dev/staging)
ZORA_SMART_WALLET_ADDRESSSmart wallet address to use for trading/posting when not recorded in the wallet file
ZORA_DM_NOTIFYSet to always to bypass the throttle on the new-DM notification shown after commands
ZORA_NO_ANALYTICSSet to 1 to disable analytics
DO_NOT_TRACKSet to 1 to disable analytics
NO_COLORSet to disable colored terminal output

Analytics

The CLI collects anonymous usage analytics via PostHog. No personal data is collected — only command names, success/failure status, and CLI version.

Opt out by setting either:

export ZORA_NO_ANALYTICS=1
# or
export DO_NOT_TRACK=1

Agent Configuration

For AI agents and automated environments, configure everything via environment variables to avoid interactive prompts:

export ZORA_PRIVATE_KEY=0x...
export ZORA_API_KEY=your-key-here
export ZORA_NO_ANALYTICS=1

Then use --json and --yes flags on all commands:

npx @zoralabs/cli balance --json
npx @zoralabs/cli buy 0x... --eth 0.01 --yes --json