Models & pricing

The catalog

Conduix curates a catalog of production-grade models across eight providers. Browse the full live catalog at /dashboard/models — each row shows the model id, provider, context window, and the exact per-1M-token rate you pay.

How pricing works

Transparent per-token pricing. The rate at /dashboard/models is what you pay — all-in. Credits behave like dollars (1 credit ≈ $1). No per-seat fees, no surprise overages.

Calling a model

Use the model id in the standard OpenAI request body. Conduix routes to the correct provider based on the id.

client.chat.completions.create(
    model="claude-haiku-4-5-20251001",  # → routed to Anthropic
    messages=[{"role": "user", "content": "Summarize…"}],
)

Automatic fallback chains

Each model has a curated fallback list. If the primary fails (provider down, circuit breaker tripped, rate-limited upstream), Conduix retries against the next entry — invisibly. Your customer never sees the failure.

Requested:  gpt-4o-mini
Fallback chain:
  1. gpt-4o-mini      (openai)
  2. claude-haiku-4-5 (anthropic)
  3. gemini-2.5-flash (google)

When a fallback served the request, the response includes x-conduix-fallback: true and x-conduix-model-served shows the actual model used. See Observability.

Restricting which models a key can call

Per-key allowlists keep developers in their lane (e.g. internal tools can't accidentally call frontier-tier models). Configure in the dashboard or via the keys API:

{
  "name": "Internal tools",
  "allowed_models": ["gpt-4o-mini", "claude-haiku-4-5-20251001"],
  "rate_limit": 60
}

Using a non-catalog model

Need a model Conduix doesn't curate? Or your own self-hosted model? Use BYO endpoints: register your own OpenAI-compatible URL and call model: "byo:<slug>/<your-model>".

Tiers

Models are grouped into tiers for governance. You can build allowlists at the tier level rather than naming each model: