Skip to main content

Documentation Index

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

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

Environment & Configuration

All Svantic deployment configuration is managed through environment variables. No code changes are required to switch between topologies.

Core Variables

VariablePurposeDefault
SAVANT_PORTPort the Svantic server listens on3000
SAVANT_BASE_URLBase URL for this Svantic instancehttp://localhost:3000
SAVANT_CENTRAL_URLCentral hub URL (sidecar → central topology only)
LLM_API_KEYAPI key for the language model provider
LLM_MODELModel to use for planning and executiongemini-2.5-flash

Agent Variables

VariablePurposeDefault
SVANTIC_CLIENT_IDAPI client ID for agent authentication
SVANTIC_CLIENT_SECRETAPI client secret for agent authentication
SVANTIC_INSTANCE_IDStable instance ID (for containers/k8s)hostname-port
SAVANT_AGENTS_URLURL your agent uses to reach Svantic

Knowledge Store

VariablePurposeDefault
CORTEX_URLURL of the Cortex knowledge servicehttp://localhost:3002
CORTEX_MONGO_URIMongoDB connection string for knowledge card storage
EMBEDDING_MODELModel used for vector embeddings

Database

VariablePurposeDefault
DATABASE_URLPostgreSQL connection string for the gateway
REDIS_URLRedis connection string for session state and caching

Topology-Specific Configuration

Standalone

Minimal configuration — just the LLM key:
LLM_API_KEY=your-key npm run api

Sidecar

Same as standalone, but your application connects via SAVANT_AGENTS_URL:
SAVANT_AGENTS_URL=http://savant:3000 node my-app.js

Central + Sidecar

Add SAVANT_CENTRAL_URL on each sidecar to register with the hub:
SAVANT_CENTRAL_URL=http://central-savant:3000 npm run api
The central instance does not need SAVANT_CENTRAL_URL — it is the hub.