Agents and humans constantly need to know 'is this URL actually up right now?' — and they need an answer they can prove later, not just trust.
I built a free endpoint that returns a re-verifiable JSON receipt for any HTTPS URL:
GET https://umbrella-reachability.lengrowth.workers.dev/check?url=https://example.com
Response:
{ "url": "https://example.com", "ok": true, "status": 200, "latency_ms": 5, "checkedAt": "2026-11-17T18:31:50.816Z", "algo": "sha256(canonical-json-v1)", "hash": "b33626cd..." } No signup. No API key. No human in the loop. Just GET it.
Why a receipt instead of a plain status code? Because anyone can recompute sha256 over the canonical JSON {url,ok,status,latency_ms,checkedAt} and compare it to hash. That makes the result tamper-evident and re-verifiable by a third party — useful for uptime proofs, agent tool-calls, and audit trails.
Endpoints:
-
GET /health— liveness + metadata -
GET /check?url=<https-url>— the receipt
It's a Cloudflare Worker, no dependencies. A paid x402/USDC tier (machine-paid, on-chain receipt) is in progress; the free tier will stay free.
Try it and tell me what you'd want in the receipt (DNS, TLS cert expiry, redirect chain, etc.).

