Skip to main content

Provider Configuration

aCMF supports separate OpenAI-compatible providers for:
  • Adjudicator
  • Context Enhancer
  • Cortex
  • Embeddings

Provider kinds

  • openai_compatible
  • stub
stub is useful for tests and local development. openai_compatible expects a standard OpenAI-style API with base_url, API key, and model name. For a complete field-by-field environment reference, including which variables are required and when, see Environment Reference. Recommended starting point:
  • use openai/gpt-5.4 for adjudicator, context enhancer, and cortex if you want one consistent default
  • use inception/mercury-2 only for the Context Enhancer if you want faster token speed on read-time synthesis
  • use openai/text-embedding-3-large when retrieval quality matters most, or openai/text-embedding-3-small when cost and vector size matter more

Resolution rules

  • Each role first reads its own PROVIDER, BASE_URL, API_KEY, MODEL, and TIMEOUT_SECONDS.
  • If a role does not define BASE_URL, API_KEY, or TIMEOUT_SECONDS, aCMF falls back to the global OpenAI-compatible defaults.
  • If a role is set to stub, network credentials are not required for that role.

Global defaults

These settings are shared when a role does not define its own override:

Adjudicator

Context Enhancer

Cortex

Embeddings

Example mixed setup

Recommendation

Keep providers independent, but start by using the same endpoint for all roles unless you have a clear routing reason not to. The important boundary is that each role can choose its own model and credentials when needed.