Skip to main content

Configuration

Config is stored at ~/.dria/config.json and created automatically by dria init. All values can be overridden with environment variables.

Config fields

Config fieldEnvironment variableDefault
privateKeyDKN_PRIVATE_KEY
apiKeyDKN_API_KEY
apiBaseDKN_API_BASEhttps://inference.dria.co
networkDKN_NETWORKbase

Example config

{
  "privateKey": "0x...",
  "address": "0x...",
  "apiKey": "dkn_live_...",
  "apiBase": "https://inference.dria.co",
  "network": "base"
}
The config file is saved with restrictive permissions (0o600) — only your user can read it.

Environment variable overrides

Environment variables take precedence over config file values:
DKN_API_KEY=dkn_live_abc123 dria generate -m qwen3.5:9b "hello"

Output conventions

The CLI follows Unix conventions for piping:
  • Spinners and progress go to stderr
  • Data (generated text, JSON) goes to stdout
  • Spinners are suppressed when stdout is not a TTY (i.e., piped)
  • --json flag outputs raw JSON and suppresses all spinners
This means you can safely pipe output:
dria generate -m qwen3.5:9b "list 5 colors" | tee output.txt
dria batch prompts.jsonl | jq .