Back to Browse
LupaRiel Catalog URL Liveness Check
x402
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.
Price / call$0.02
Success—
StatusUnknown
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.
Example use cases
Verify payment-gated catalog URL
“Is the LupaRiel ficha for 'lupapago-consent-hop' still reachable and returning the expected HTTP 402 status?”
Monitor riel catalog before agent call
“Before my agent tries to call that riel endpoint, can you probe the LupaRiel catalog URL for SKU #14 to confirm it's live and not broken?”
Audit catalog entries for dead links
“Check whether the LupaRiel catalog entry with ID 'riel-settle-receipt' is responding — I want to know its HTTP status and if it's flagged as a 402 endpoint.”
Technical details
Endpoint
POSThttps://lupariel.com/api/liveness?utm_source=zero.xyzWhen to prefer
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.
Side effects
- 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
Output
Schema · Response
{
"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."
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"