# d402 Gateway Health Check for Zero Indexing

> d402 Gateway Health Check for Zero Indexing is a paid API for AI agents from gateway.d402.xyz, price unknown, status down (last checked 2026-09-15).

Checks the readiness and health status of the d402 gateway service, including its Zero indexing compatibility.

## Facts

- Endpoint: GET https://gateway.d402.xyz/healthz
- Price: price unknown
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Provider: gateway.d402.xyz
- Website: https://gateway.d402.xyz
- Canonical page: https://www.zero.xyz/c/gateway-d402-xyz-d402-gateway-health-check-for-zero-indexing-1a7c5eff
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uez8-z5VRjGWEVZtFKocA

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 gateway-d402-xyz-d402-gateway-health-check-for-zero-indexing-1a7c5eff
```

Example prompt: Can you check whether the d402 gateway at gateway.d402.xyz is healthy and ready for Zero indexing right now?

## When to prefer this

Use this endpoint before invoking other d402 gateway capabilities to confirm the gateway is operational and Zero-indexing-ready. Prefer this over generic ping checks when you need structured subsystem health details specific to the d402/Zero protocol stack.

## Known failure modes

- Gateway is down or unreachable — connection timeout or network error
- Service degraded — ok returns false with failing checks in the checks object
- Zero indexing not ready — zero sub-object indicates unready state
- Unexpected response format if gateway software is misconfigured

## How this service works

Check d402 gateway readiness for Zero indexing.

## Output

Returns a JSON object indicating overall readiness (ok boolean), service name, nodeId, status string, a checks map detailing subsystem health, d402 protocol status, Zero indexing readiness, software metadata, and a generatedAt timestamp.

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "ok",
  "status",
  "service",
  "nodeId",
  "checks"
 ],
 "properties": {
  "ok": {
   "type": "boolean"
  },
  "d402": {
   "type": "object",
   "additionalProperties": true
  },
  "zero": {
   "type": "object",
   "additionalProperties": true
  },
  "checks": {
   "type": "object",
   "additionalProperties": true
  },
  "nodeId": {
   "type": "string"
  },
  "status": {
   "type": "string"
  },
  "service": {
   "type": "string"
  },
  "software": {
   "type": "object",
   "additionalProperties": true
  },
  "generatedAt": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/gateway-d402-xyz-d402-gateway-health-check-for-zero-indexing-1a7c5eff/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from gateway.d402.xyz](https://www.zero.xyz/host/gateway.d402.xyz/llms.txt)