# LupaRiel Catalog URL Liveness Check

> LupaRiel Catalog URL Liveness Check is a paid API for AI agents from lupariel.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-02).

Probes one or more LupaRiel catalog URLs to check whether they are live, returning HTTP status, 402 flags, and liveness results per entry.

## Facts

- Endpoint: POST https://lupariel.com/api/liveness?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lupariel-catalog-url-liveness-check-d4b6966b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eEdp-9r8KHFOirBKeCegb

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 lupariel-catalog-url-liveness-check-d4b6966b -d '<json body>'
```

Example prompt: Can you check whether the LupaRiel catalog entry 'lupapago-consent-hop' is still live — specifically if it responds and whether it's flagging as an HTTP 402 endpoint?

## When to prefer this

Use this endpoint when you need to confirm that a specific LupaRiel catalog ficha URL is currently live and responding as expected, particularly to verify 402-gated endpoints before invoking them or to audit catalog entries for staleness. Prefer this over generic uptime monitors when the target is specifically a LupaRiel riel entry and you need structured liveness metadata including 402 flags.

## Known failure modes

- URL slug not found in catalog — empty or error result
- Network timeout reaching the target ficha URL — liveness returns false
- Malformed request body — server returns 4xx validation error
- Payment not provided or insufficient — endpoint returns 402 itself before probe executes
- Catalog out of sync — URL exists in catalog but target has moved

## How this service works

Directorio público de x402, AP2, ACP y MPP. Fuente + fecha. No inventamos precios ni estados.

## Output

A JSON object containing a 'kind' field set to 'liveness', a count of probed entries, the product name ('LupaRiel'), an array of results each with id, live boolean, notes string, is_402 boolean, and http_status code, plus the applied ruleset identifier and a disclaimer string.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "kind": "liveness",
  "count": 1,
  "product": "LupaRiel",
  "results": [
   {
    "id": "lupapago-consent-hop",
    "live": true,
    "notes": "HTTP 402 Payment Required",
    "is_402": true,
    "http_status": 402
   }
  ],
  "ruleset": "riel-liveness-v1",
  "disclaimer": "Checks LupaRiel catalog URLs; no es asesoramiento."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lupariel-catalog-url-liveness-check-d4b6966b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from lupariel.com](https://www.zero.xyz/host/lupariel.com/llms.txt)