Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.valiqor.com/llms.txt

Use this file to discover all available pages before exploring further.

​
config

Project configuration — interactive setup, view, or update settings. Running valiqor config with no subcommand launches the interactive wizard, which creates a .valiqorrc file in the current directory. 
valiqor config
The wizard prompts for:
SettingDescription
project_nameName for your Valiqor project
trace_dirDirectory for trace output files
scan_dirDirectory for scan output files
environmentEnvironment label (e.g. development, production)
After saving, the CLI creates the output directories and shows next steps based on your auth status and installed modules. Use a subcommand to view or update settings non-interactively. 
valiqor config <show|set>

​
config show

Display current authentication info and local project settings. 
valiqor config show [flags]
FlagTypeDefaultDescription
--jsonflagfalseOutput as JSON
# Human-readable output
valiqor config show

# Machine-readable output
valiqor config show --json
Shows API key source (global/local), email, all .valiqorrc settings, and the config file path.

​
config set

Update one or more settings non-interactively. 
valiqor config set <key=value> [key=value ...]
Allowed keys: project_name, api_key, trace_dir, scan_dir, environment, valiqor_intelligence, debug, openai_api_key 
# Set multiple values at once
valiqor config set project_name=my-app environment=production

# Enable debug mode
valiqor config set debug=true
Boolean keys (valiqor_intelligence, debug) accept true, 1, yes as truthy values. If trace_dir or scan_dir change, the CLI creates the new directories automatically.

​
status

Show a comprehensive status overview. 
valiqor status
Displays:
  • Authentication — credential source (global vs local), email
  • Local config — project name, environment, directories
  • Cloud connection — API reachability
  • Files — trace and scan file counts in configured directories
  • Modules — availability of Trace, Scanner, Eval, Security, Failure Analysis
  • Version — installed SDK version

​
test

Validate that your project is correctly configured and can reach the Valiqor backend. 
valiqor test
Checks:
  1. Trace and scan directories exist and are writable
  2. API key is valid (local or global)
  3. Backend API is reachable
  4. Required modules are installed
  5. Provider packages detected (openai, anthropic, langchain, ollama, agno)
Reports errors and warnings with actionable messages.

​
upload

Upload trace and scan files to the Valiqor backend. 
valiqor upload [path] [flags]
FlagTypeDefaultDescription
pathpositionalconfigured dirsPath to a file or directory to upload
-t / --typetrace | scan | allallType of files to upload
--endpointstring—Custom backend API endpoint URL
--api-keystring—API key override
--delete-afterflagfalseDelete local files after successful upload
--dry-runflagfalseShow what would be uploaded without uploading

​
Examples

# Upload everything from configured directories
valiqor upload

# Upload a specific trace file
valiqor upload ./traces/run_001.json --type trace

# Preview what would be uploaded
valiqor upload --dry-run

# Upload and clean up local files
valiqor upload --delete-after
Without an explicit path, the CLI uploads from the directories configured in .valiqorrc (trace_dir and scan_dir).