# x402 Facilitator Health & Capability Probe

> x402 Facilitator Health & Capability Probe is a paid API for AI agents from x402.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-18).

Queries all known x402 facilitators live to report their supported chains, assets, and payment schemes, plus current response latency — without any historical series data.

## Facts

- Endpoint: POST https://x402.halowerk.com/facilitator/health?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-facilitator-health-capability-probe-06d6af3e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ShgZ-Uo3rJOYZLvy5pKbk

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-health-capability-probe-06d6af3e -d '<json body>'
```

Example prompt: Can you check all the live x402 facilitators right now and tell me which chains and assets each one supports, and how fast they're responding?

## When to prefer this

Use this endpoint when you need a live, real-time snapshot of which x402 facilitators are online and what they support right now — especially before routing a payment or debugging a failed flow. Prefer this over static registry lookups when freshness matters. Do not use this if you need historical reliability metrics, uptime percentages, or latency percentiles — those require a time-series monitoring system this endpoint explicitly does not provide.

## Known failure modes

- Facilitator unreachable — individual facilitator may be offline or timing out, returned as a reachability failure for that entry
- No facilitators known — if the facilitator registry is empty or unavailable, the result set will be empty
- Partial results — some facilitators may respond and others may not within a single call window
- Latency data absent — historical percentile metrics (p95, uptime, error rate) are structurally unavailable and will not be returned even on success

## How this service works

Asks every known facilitator what it supports and measures how long that answer takes. Reachability, supported chains, supported assets, supported schemes and the current response time are measured live on every call. Limits, and they are the important part: error rate over 24 hours, uptime over 7 days and latency percentiles CANNOT be delivered. They require a series of own measurements every few minutes, and this service keeps no such series - a single call cannot produce a p95. Those fields s

## Output

A live snapshot for each known x402 facilitator: whether it is reachable, which blockchain networks it supports, which ERC-20 or native assets it accepts, which x402 payment schemes it advertises, and the wall-clock response time of that single call. Note: error rates, uptime percentages, and latency percentiles (e.g. p95) are explicitly not available as they require time-series measurements this service does not store.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "type": "string",
   "description": "Optional: report whether this chain is supported, as a CAIP-2 identifier such as eip155:8453."
  },
  "facilitators": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "maxItems": 6,
   "description": "Which facilitators to check by key: cdp, xpay, x402org. Default: all known."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-facilitator-health-capability-probe-06d6af3e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.halowerk.com](https://www.zero.xyz/host/x402.halowerk.com/llms.txt)