# Forest Gas Station – Statuspage Health Normalizer

> Forest Gas Station – Statuspage Health Normalizer is a paid API for AI agents from http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-02).

Fetches and normalizes a public Atlassian Statuspage into a structured health envelope with operational state, active incidents, scheduled maintenance, and component statuses.

## Facts

- Endpoint: POST https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/service/status?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/forest-gas-station-statuspage-health-normalizer-2f1a1aa0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rLa5fi1i0CCxtwQzVQ7dS

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 forest-gas-station-statuspage-health-normalizer-2f1a1aa0 -d '<json body>'
```

Example prompt: Can you check the Stripe status page at https://status.stripe.com and tell me if there are any active incidents or degraded components right now?

## When to prefer this

Use this endpoint when you need to programmatically check the real-time health of any service that publishes an Atlassian Statuspage (e.g. Stripe, GitHub, Twilio, OpenAI, AWS, etc.) and want a normalized, machine-readable result rather than scraping raw HTML. It is best suited for incident triage, pre-deploy dependency checks, and automated monitoring workflows where structured output (state enum + components + incidents) is required. Prefer this over generic web scrapers when the target is known to be an Atlassian Statuspage.

## Known failure modes

- URL does not point to an Atlassian Statuspage-compatible /api/v2/summary.json endpoint — returns unknown state or error
- Status page is private or requires authentication — request fails
- Target statuspage is itself unreachable or returns non-200 — returns unknown state
- Malformed or non-https URL rejected by input validation
- Statuspage uses a non-standard format not compatible with Atlassian Statuspage v2 API — may return partial or unknown data

## How this service works

Normalize a public Atlassian Statuspage into operational, maintenance, degraded, partial_outage, major_outage or unknown state, with components, active incidents and scheduled maintenance. V1 accepts an explicit status-page URL; it does not discover arbitrary providers or infer hidden service health. Base mainnet USDC

## Output

A structured JSON object containing a normalized operational state (one of: operational, maintenance, degraded, partial_outage, major_outage, unknown), a list of components with their individual statuses, any currently active incidents with descriptions and impact levels, and any upcoming or ongoing scheduled maintenance windows.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "status_url": {
   "type": "string",
   "pattern": "^https?://",
   "maxLength": 2048,
   "minLength": 1,
   "description": "Public status-page URL. V1 expects an Atlassian Statuspage-compatible /api/v2/summary.json endpoint."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/forest-gas-station-statuspage-health-normalizer-2f1a1aa0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run](https://www.zero.xyz/host/http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/llms.txt)