Fireworks AI
Route CortexDB's answer and extraction LLM calls through Fireworks AI's OpenAI-compatible API.
Fireworks 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. See
Self-hosting defaults.
Deployment configuration
# Extraction lane
CORTEX_LLM_URL=https://api.fireworks.ai/inference/v1
CORTEX_LLM_MODEL=accounts/fireworks/models/llama-v3p3-70b-instruct
CORTEX_ENTITY_API_KEY=$FIREWORKS_API_KEY
# Answer lane (OpenAI-compatible)
CORTEX_ANSWER_PROVIDER=openai
CORTEX_ANSWER_URL=https://api.fireworks.ai/inference/v1
CORTEX_ANSWER_MODEL=accounts/fireworks/models/llama-v3p3-70b-instruct
CORTEX_ANSWER_API_KEY=$FIREWORKS_API_KEYKeep CORTEX_EMBEDDING_* on OpenAI or a local Ollama unless you're using a Fireworks embedding model.
See Embeddings.
Choosing the model
The answer model is the one in CORTEX_ANSWER_MODEL. A per-request answer_model on /v1/answer is
only echoed in diagnostics.answer_model; the configured model answers. To serve a different
model, change CORTEX_ANSWER_MODEL or run a second deployment. See
LLM & Answer Generation.