# x402 Facilitator Failover

> x402 Facilitator Failover is a paid API for AI agents from x402-agent-suite-production.up.railway.app, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-14).

Provides a failover facilitator endpoint for x402 payment-gated HTTP requests, validating and routing GET/HEAD/DELETE requests after x402 payment settlement.

## Facts

- Endpoint: POST https://x402-agent-suite-production.up.railway.app/api/facilitator/failover
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-facilitator-failover-fd0829a6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bQotHbgni4xjyzGArkEIm

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 x402-facilitator-failover-fd0829a6 -d '<json body>'
```

Example prompt: My primary x402 facilitator is down — can you route this GET request through the x402 Agent Suite failover facilitator to check if payment has settled and the resource access is allowed?

## When to prefer this

Use this endpoint specifically when your primary x402 facilitator is unavailable or experiencing downtime and you need a resilient backup to validate payment settlement for read-only or idempotent HTTP operations (GET, HEAD, DELETE). Prefer this over building your own failover logic when operating AI agent fleets that depend on continuous x402-gated API access.

## Known failure modes

- Primary facilitator also unavailable — cascading outage returns error
- Payment not yet settled — allowed returns false with explanatory summary
- Invalid HTTP method supplied (only GET, HEAD, DELETE accepted) — schema validation error
- Malformed input object — 422 or 400 validation error
- x402 payment signature invalid or expired — request rejected with not-allowed response

## How this service works

24 paid x402 infrastructure APIs for AI agent fleets: buy advisor, audition coach, guard, proxy, MPP, attestations, and pipeline orchestration.

## Output

Returns a JSON object with 'ok' (boolean indicating request success), 'allowed' (boolean indicating whether the payment-gated resource access is permitted), and 'summary' (a human-readable string describing the outcome after x402 payment settlement).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "required": [
      "ok",
      "allowed",
      "summary"
     ],
     "properties": {
      "ok": {
       "type": "boolean"
      },
      "allowed": {
       "type": "boolean"
      },
      "summary": {
       "type": "string"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "allowed": true,
  "summary": "Paid response after x402 settlement"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-facilitator-failover-fd0829a6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-agent-suite-production.up.railway.app](https://www.zero.xyz/host/x402-agent-suite-production.up.railway.app/llms.txt)