MC-1 DOCS
API ReferenceCookbook
Docs/MC-1 Core/Routing objectives and constraints
PublishedGALAST REVIEWED · 30 AUG 2026

Routing objectives and constraints

Select automatic objectives and hard boundaries without coupling to one vendor.

Supported objectives

The objective guides ranking after hard eligibility constraints are applied.

  • auto
  • balanced
  • best_quality
  • lowest_cost
  • lowest_latency
  • private
  • sovereign
  • agent_safe
  • high_reliability
  • local_only

MC-1 request options

{
  "model": "colomboai/mc-1",
  "messages": [
    {
      "role": "user",
      "content": "Classify this incident."
    }
  ],
  "mc1": {
    "objective": "high_reliability",
    "max_cost_usd": 0.05,
    "max_latency_ms": 8000,
    "minimum_quality": 0.85,
    "privacy": "private",
    "data_classification": "confidential",
    "allowed_regions": [
      "us"
    ],
    "allow_escalation": true,
    "max_attempts": 2,
    "expose_route": true,
    "evaluation": "required",
    "risk_mode": "high"
  }
}

Provider preferences

Use provider.only to enforce an allowlist, provider.order to express preference, and allow_fallbacks to control whether other eligible providers may be attempted. A preference never bypasses policy.

{
  "provider": {
    "only": [
      "approved-provider"
    ],
    "order": [
      "approved-provider"
    ],
    "allow_fallbacks": false
  }
}
End of guide
Was this page helpful?