Global Options
These flags work on every command. Place them before the command name.
| Flag | Short | Description |
|---|---|---|
--profile NAME | -p | Use a named profile (default: default) |
--output FORMAT | -o | Output format: table, json, csv. JSON is auto-selected when output is piped (e.g. by an LLM agent) |
--quiet | -q | Minimal output — IDs only. Useful for agents chaining commands |
--verbose | -v | Debug logging (request IDs, timing) |
--yes | -y | Skip confirmation prompts |
--dry-run | Show what a mutation would do without executing. Recommended for agent-initiated writes before human approval | |
--no-color | Disable terminal colors | |
--version | Show CLI version |
Environment Variables
| Variable | Description | Default |
|---|---|---|
LEV_API_KEY | API key for authentication | — |
LEV_API_URL | API base URL | https://api.levcapital.com |
LEV_PROFILE | Active profile name | default |
LEV_OUTPUT | Default output format | auto-detect |
LEV_API_TIMEOUT | Request timeout in seconds | 30 |
LEV_CA_BUNDLE | Custom CA cert path for corporate proxies | — |
LEV_DEBUG_LOG | File path for structured debug log output | — |
Configuration
Settings resolve in priority order:
View the resolved configuration for the current context:
lev config showProfiles
Named profiles let you switch between environments or accounts without re-authenticating.
# Create a profile
lev auth login --profile staging
# Use a profile for a single command
lev -p staging deals list
# Switch the default profile
lev auth switch stagingEach profile stores its own API URL and keychain credential. Profile names are arbitrary strings.
Exit Codes
| Code | Meaning |
|---|---|
| 0 | Success |
| 1 | General error |
| 2 | Usage error (bad args, missing --yes when piped) |
| 3 | Authentication failed |
| 4 | Insufficient permissions (scope) |
| 5 | Resource not found |
| 6 | Validation error (bad input) |
| 7 | Rate limited |
| 8 | Server error |
| 9 | Network error (connection failed, timeout) |
| 130 | Interrupted (Ctrl+C) |
See CLI Workflows for patterns that branch on these codes.
Troubleshooting
CLI docs complete
Explore the REST API reference for full field definitions and response schemas, or see the Workflows section for MCP and agent patterns.