# verify-service x402 Endpoint Health & Catalog Checker

> verify-service x402 Endpoint Health & Catalog Checker is a paid API for AI agents from verify-service.node01.org, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-31).

Probes an x402 paid endpoint three times without payment and checks it against the PayAI discovery catalog, returning a verdict, success rate, latency percentiles, payTo address, and catalog status.

## Facts

- Endpoint: GET https://verify-service.node01.org/api/verify-service?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/verify-service-x402-endpoint-health-catalog-checker-db900f22
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_F26zwn9WcPCkuejqMCbti

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 verify-service-x402-endpoint-health-catalog-checker-db900f22
```

Example prompt: Can you check if the x402 endpoint at https://example.com/api/service is alive, how fast it responds, and whether it's already listed in the PayAI discovery catalog?

## When to prefer this

Use this endpoint when you need to confirm an x402 endpoint's liveness, latency profile, payTo address, and catalog status in a single call before integrating or paying for it. Prefer it over generic HTTP health checkers because it is x402-protocol-aware, tests without triggering payment, and cross-references the PayAI discovery catalog simultaneously.

## Known failure modes

- Target URL is unreachable — endpoint returns BROKEN verdict
- Target URL does not return a 402 response — verdict is NOT-402
- Endpoint responds but exceeds latency thresholds — verdict is SLOW
- Endpoint is live but not found in the PayAI catalog — NOT-INDEXED returned
- Invalid or malformed URL input — request rejected with validation error
- Verify-service itself is temporarily unavailable — upstream error returned

## How this service works

Send the URL of an x402 endpoint. It is probed three times without payment, then matched against the PayAI discovery catalog. You get a verdict (ALIVE / SLOW / BROKEN / NOT-402 / INDEXED / NOT-INDEXED), success rate, latency p50/p95, payTo and last catalog update.

## Output

A JSON object with a status verdict (e.g. ALIVE, SLOW, BROKEN, NOT-402, INDEXED, NOT-INDEXED), the target URL, catalog metadata (found boolean and count), latency statistics (p50 and p95 in seconds, sample count), the payTo wallet address, and a verified_at timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "URL of the x402 endpoint to verify (liveness, latency, catalog)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "ALIVE_PAYABLE_NOT_INDEXED",
  "target": "https://example.com/api/service",
  "catalog": {
   "count": 0,
   "found": false
  },
  "latency": {
   "p50_s": 0.45,
   "p95_s": 1.2,
   "samples": 3
  },
  "verified_at": "2026-10-08T08:00:00Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/verify-service-x402-endpoint-health-catalog-checker-db900f22/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from verify-service.node01.org](https://www.zero.xyz/host/verify-service.node01.org/llms.txt)