GitHub: veniceai/venice-cli
Published as
veniceai-cli on npm. MIT licensed.Privacy-first
Optional E2EE and TEE attestation. No telemetry, no browser tracking.
Every modality
Chat, search, image, upscale, TTS, transcription, video, and embeddings
Scriptable
JSON and raw output, stdin piping, and shell completions for bash, zsh, fish
Quick start
1
Install the CLI
Install globally with npm:Or run it without installing:
2
Get a Venice API key
Generate one from venice.ai/settings/api. See the API key guide for step-by-step instructions.
3
Configure your key
Run the interactive setup and paste your key when prompted, so it never appears in your shell history or process list:Or use an environment variable instead:
4
Start chatting
Requires Node.js 18.0.0 or higher.
VENICE_API_KEY overrides any value stored in the config file.Commands
Chat
Web search
Image generation & upscaling
Text-to-speech & transcription
Video generation
Video generation is asynchronous (queue-based).Models & embeddings
Configuration
Privacy: E2EE & TEE
Venice CLI is built for privacy. It ships no telemetry, stores your API key locally with restricted permissions, and supports Venice’s confidential compute models.- End-to-End Encryption (E2EE): Messages are encrypted client-side and decrypted only inside the TEE, so Venice cannot read your data. The CLI auto-enables E2EE when a model advertises the capability, generating an ephemeral key pair per session (ECDH + AES-GCM).
- TEE Attestation: Cryptographically verify that a model runs in a secure enclave before sending data.
E2EE mode disables tools and web search to preserve end-to-end encryption.
Output formats
The CLI auto-detects when output is piped and switches to
raw.
Resources
GitHub
Source code, issues, and releases
npm
veniceai-cliVenice MCP Server
Expose the same Venice tools to any MCP host
Venice API Reference
Full endpoint and parameter docs