# Tanod utilpeek – Status Page Reader

> Tanod utilpeek – Status Page Reader is a paid API for AI agents from tanod.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-14).

Reads a public status page (Atlassian Statuspage, incident.io, Instatus, Better Stack) and returns the overall health state, degraded components, and open incidents for any API or SaaS.

## Facts

- Endpoint: POST https://tanod.dev/v1/web/status-page?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tanod-utilpeek-status-page-reader-1b3e8c69
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Rb01qZ7ogym4ZB9P2TFqI

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 tanod-utilpeek-status-page-reader-1b3e8c69 -d '<json body>'
```

Example prompt: Can you check if Stripe is currently up or experiencing any incidents — look at their status page and tell me the overall state and any degraded components?

## When to prefer this

Use this endpoint when an agent needs to programmatically check whether a third-party API or SaaS is operational before making calls, diagnosing integration failures, or building automated uptime monitoring. It handles the hard work of discovering the status page URL, parsing proprietary formats across four major status page platforms, and returning structured incident and component data — eliminating the need to scrape raw HTML.

## Known failure modes

- No status page found at the provided URL or common subdomains (status.domain, etc.)
- Unsupported status page platform (only Atlassian Statuspage, incident.io, Instatus, Better Stack are supported)
- URL is malformed or exceeds length limits
- Status page is behind authentication or bot protection
- Network timeout reaching the status page

## How this service works

utilpeek (Tanod) status page reader: is a service up, degraded components and open incidents from its public status page. Use when an agent must know whether an API or SaaS is up: its status page's overall state, degraded parts, incidents.

## Output

Returns the overall operational status of the service (e.g. operational, degraded, outage), a list of any degraded or disrupted components, and details of any currently open incidents including titles and descriptions, all extracted from the target status page.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "maxLength": 2048,
   "minLength": 3,
   "description": "A status page URL (https://status.example.com), a company site URL or a bare domain (example.com). The page is looked for at that host and at status.<domain> and a few other common hosts. Atlassian Statuspage, incident.io, Instatus and Better Stack pages are read."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tanod-utilpeek-status-page-reader-1b3e8c69/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from tanod.dev](https://www.zero.xyz/host/tanod.dev/llms.txt)