Runtime Configuration

The runtime.toml file is the central configuration for an Akshi node.

Typical configuration

# Runtime identity
[identity]
name = "my-node"
data_dir = "./akshi-data"
# did = "did:web:node.example.com"   # auto-generated if omitted

# Agent definitions
[[agents]]
name = "log-monitor"
wasm_path = "agents/log_monitor.wasm"
tick_interval_secs = 60
fuel_limit = 1_000_000

[agents.capabilities]
inference = true
journal = true
filesystem = true

[agents.endpoints]
allowed = []

# Inference routing
[router]
default_route = "local"

[[router.routes]]
name = "local"
provider = "ollama"
model = "llama3.2"
base_url = "http://127.0.0.1:11434"

# Dashboard and HTTP API
[dashboard]
port = 3210
token = "my-secret-token"
cors_origins = ["http://127.0.0.1:3210"]
rate_limit = 300
rate_limit_burst = 50

Section reference

Section	Purpose
`[identity]`	Node name, data directory, DID identity
`[[agents]]`	Agent entries (one per agent)
`[router]`	Inference routing configuration
`[dashboard]`	HTTP API and dashboard settings
`[mesh]`	Multi-node mesh networking (optional)
`[broker]`	Secrets broker settings (optional)
`[economics]`	Spend policy and budgets (optional)

Data directory

The data_dir path stores journals, databases, keys, and audit logs. It is created automatically on first run. Use an absolute path in production.

Environment variable substitution

Values can reference environment variables:

[dashboard]
token = "${AKSHI_TOKEN}"

[[router.routes]]
api_key = "${ANTHROPIC_API_KEY}"

See Environment Variables for the full list of recognized variables.

Validation

Check your configuration before running:

akshi config-check

This validates syntax, required fields, capability consistency, and endpoint reachability.