Uptime Check

Check whether a URL is up: status code, latency, redirects, TLS and server headers.

Pay by wallet (x402) uptime-check

Example

Example answer
{
  "tls": true,
  "url": "https://example.com",
  "error": "fetch failed",
  "status": "down",
  "checked_at": "2026-03-09T20:03:13.819Z",
  "latency_ms": 22,
  "status_code": null
}

Inputs

FieldTypeRequiredWhat it is
urlstringYes—
methodstringNo—
timeout_msintegerNo—

Output fields

How reliably each field appears in a successful answer.

FieldTypeAppears
statusstringAlways (present in every successful answer)
latency_msintegerAlways (present in every successful answer)
redirectedbooleanAlways (present in every successful answer)
status_codeintegerAlways (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "uptime-check",
    "inputs": {
      "url": "https://strale.dev"
    },
    "max_price_cents": 2
  }'

Limitations

  • One check does not measure historical or regional uptime

    Single point-in-time check from one server location — does not represent historical uptime or multi-region availability

    What to do instead: Schedule periodic checks and compute uptime percentage over time rather than relying on a single probe

  • HTTP 200 can mask missing pages

    Only the HTTP status code is inspected. A removed listing or soft-404 page served with HTTP 200 (or even a literal 404 response) is reported as status "up" — this capability answers "does the server respond?", not "does this page still exist?".

    What to do instead: Use page-exists to check whether a specific page still resolves to real content.

Related tools