# Service Failover Selector

> Service Failover Selector is a paid API for AI agents from phion.systems, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-20).

Selects the highest-priority healthy and compatible provider for failover without silent fallback, surfacing the decision transparently

## Facts

- Endpoint: POST https://phion.systems/v1/paid/trust/service-failover-selector?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/service-failover-selector-df8f374b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FYcgCW5Jq_TcAOVG7IL3S

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability service-failover-selector-df8f374b -d '<json body>'
```

Example prompt: My primary API provider just went down — can you pick the highest-priority healthy provider from my list that's compatible with my current service requirements, and tell me explicitly which one you chose and why rather than just silently switching?

## When to prefer this

Choose this endpoint when you need explicit, auditable failover decisions rather than silent substitution — especially in agentic workflows where transparency about which provider was selected and why is critical for debugging, compliance, or trust. Prefer this over generic load-balancers or silent retry logic when the selection rationale must be surfaced to the user or logged for audit.

## Known failure modes

- No healthy providers available — all candidates failing health checks
- No compatible providers match the stated requirements
- Insufficient provider metadata to assess compatibility
- Input schema missing required service context fields
- Ambiguous or conflicting priority definitions preventing clear ranking

## How this service works

Select the highest-priority healthy compatible provider without silent fallback

## Output

Returns the explicitly selected highest-priority provider that is both healthy and compatible with the stated requirements, along with the rationale for the selection, priority ranking context, and health status — ensuring no silent fallback occurs.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input",
  "output"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "additionalProperties": true
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "example"
   ],
   "properties": {
    "example": {
     "type": "object",
     "additionalProperties": true
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/service-failover-selector-df8f374b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from phion.systems](https://www.zero.xyz/host/phion.systems/llms.txt)