Skip to main content
A provider/model offer has separate upstream and Phaseo statuses. This matters when a provider has released a model but Phaseo has not yet implemented or enabled the corresponding endpoint. You will see these fields on model pages, provider pricing cards, and related availability UI.

​
Provider availability

Provider availability describes the upstream offer. Provider availability never means that Phaseo can route the request.

​
Phaseo integration status

Phaseo status describes our implementation and rollout. Only Enabled integrations can have public routing enabled.

​
Internal access

Access scope is separate from Phaseo integration status: An internal route requires the high-entropy internal token and an explicit testing-mode request. A customer cannot enable it with the testing header alone. Ordinary requests do not perform an internal-route database lookup; they use the existing default context cache. Internal testing uses a separate cache segment and only considers explicitly internal routes whose upstream offer is usable and whose Phaseo status is Testing or Enabled.

​
Routing health

Routing health is a third, operational signal. It answers how an enabled route should be selected right now. Deranking does not change the provider’s availability or Phaseo’s integration lifecycle. Live health observations also do not rewrite either lifecycle field.

​
Examples

A newly released provider offer can be:
  • provider availability: Available
  • Phaseo status: Implementing
  • routing health: not applicable because routing is off
A mature but temporarily degraded route can be:
  • provider availability: Available
  • Phaseo status: Enabled
  • routing health: Deranked L2
A provider announcement can be:
  • provider availability: Coming Soon
  • Phaseo status: Planned
  • routing health: not applicable

​
Compatibility

Existing API fields such as availability_status, routing_status, is_active_gateway, and routable remain available during the additive rollout. New integrations should use the explicit provider and Phaseo fields.
Last modified on August 4, 2026