Uptime Ping API

GET /api/ping $0.001 per call USDC on Base · x402

Cheapest liveness ping: ONE request to any public URL — is anything answering, and how fast? Returns up/down, HTTP status, and latency in ms. Any HTTP response below 500 counts as up; redirects are reported, not followed. High-frequency monitoring loops belong here; step up to /api/uptime for redirect following and headers, /api/uptime/report for the full timing/TLS/CDN report.

Parameters

Name	In		Description
`url`	query	required	Public http(s) URL to ping, e.g. https://example.com

Example request

curl "https://api.webbersites.com/api/ping?url=https%3A%2F%2Fexample.com"
# first call returns 402 + payment requirements; an x402 client pays and retries automatically

Example response

{
    "url": "https://example.com",
    "up": true,
    "status": 200,
    "latency_ms": 87,
    "checked_at": "2026-07-09T00:00:00.000Z"
}

MCP tool: get_ping — via npx -y webbersites-x402-mcp (local, key stays on your machine) or the remote endpoint https://api.webbersites.com/mcp.

How payment works

There is no signup and no API key. Call the endpoint; it replies 402 Payment Required with machine-readable payment requirements. Your client signs a USDC transfer authorization (EIP-3009, gasless) and retries with the X-PAYMENT header — @x402/fetch does this automatically. See the overview for a working snippet.