.env.example

# Instance auth: /services/* is always gated on the api_key callers send, looked
# up in lightning_clients via APOLLO_CLIENTS_DB_URL (falls back to POSTGRES_URL).
# A known client swaps in its stored Anthropic key; an unknown sk-ant- key is
# forwarded. See platform/src/auth/README.md.

# Database holding the lightning_clients credentials table. Leave unset locally to
# share POSTGRES_URL (one DB for everything). In production point this at a separate
# credentials DB so client secrets don't co-locate with the docs data. The TS auth
# code, `bun run migrate`, and the `client` CLI all resolve this var; the Python docs
# services always use POSTGRES_URL.
# APOLLO_CLIENTS_DB_URL=postgresql://localhost:5432/apollo_clients

# Optional at-rest encryption for stored client Anthropic keys. Base64 of 32 bytes
# (openssl rand -base64 32). See platform/src/auth/README.md.
# APOLLO_ENC_KEY=

# Shared secret for internal Apollo-to-Apollo apollo() calls. In production set
# this to the SAME value across all processes — it is what lets self-calls through
# the gate, and the global ANTHROPIC_API_KEY is a dev-only fallback. If unset,
# each process mints its own token, which only works single-process-per-host.
# APOLLO_INTERNAL_TOKEN=

ANTHROPIC_API_KEY=sk-YOUR-API-KEY-HERE

OPENAI_API_KEY=sk-YOUR-API-KEY-HERE
PINECONE_KEY=YOUR-API-KEY-HERE
POSTGRES_URL=postgresql://localhost:5432/apollo_dev
SENTRY_DSN=YOUR-API-KEY-HERE
GITHUB_TOKEN=KEY

# Langfuse observability
LANGFUSE_SECRET_KEY=sk-lf-...
LANGFUSE_PUBLIC_KEY=pk-lf-...
LANGFUSE_BASE_URL=https://cloud.langfuse.com

# HF_ACCESS_TOKEN=hf_YOUR-API-KEY-HERE # llama2 base
# ZILLIZ_URI =  https://in01-XXXXXXXXXXXXX.aws-us-west-2.vectordb.zillizcloud.com:XXXXX
# ZILLIZ_TOKEN =db_admin:password (or ApiKey)