Integrations
Together AI
Route CortexDB's answer and extraction LLM calls through Together AI's OpenAI-compatible API.
Together AI exposes an OpenAI-compatible API, so CortexDB's LLM routers point straight at it.
Set both the extraction and answer lanes
CORTEX_LLM_* is the entity-extraction lane; /v1/answer uses the separate CORTEX_ANSWER_*
lane (default anthropic/claude-opus-4-6). Set both — CORTEX_LLM_* alone leaves /v1/answer on
the disabled default. See Self-hosting defaults.
Deployment configuration
# Extraction lane
CORTEX_LLM_URL=https://api.together.xyz/v1
CORTEX_LLM_MODEL=meta-llama/Llama-3.3-70B-Instruct-Turbo
CORTEX_LLM_API_KEY=$TOGETHER_API_KEY
# Answer lane (OpenAI-compatible)
CORTEX_ANSWER_PROVIDER=openai
CORTEX_ANSWER_URL=https://api.together.xyz/v1
CORTEX_ANSWER_MODEL=meta-llama/Llama-3.3-70B-Instruct-Turbo
CORTEX_ANSWER_API_KEY=$TOGETHER_API_KEYTogether also serves embeddings (e.g. togethercomputer/m2-bert-80M-8k-retrieval) if you'd rather keep
those local to the same provider — otherwise keep CORTEX_EMBEDDING_* on OpenAI or Ollama. See
Embeddings.
Per-request override
client.answer(scope="org:acme/user:alice", question="…",
answer_model="openai/meta-llama/Llama-3.3-70B-Instruct-Turbo")