# Status State API - Vendor Monitor Snapshot

> Status State API - Vendor Monitor Snapshot is a paid API for AI agents from status-state-api.replit.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-09).

Returns a full per-vendor status snapshot including component statuses, overall health, active incidents, and recent check timestamps for a specific developer infrastructure vendor by slug.

## Facts

- Endpoint: GET https://status-state-api.replit.app/api/monitors/%7Bslug%7D
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-09
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/status-state-api-vendor-monitor-snapshot-20f65122
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5HkE9Q3qCjotIbYRGhVjH

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 status-state-api-vendor-monitor-snapshot-20f65122
```

Example prompt: Can you check the current status of OpenAI right now — are all their API components operational or is there an active incident?

## When to prefer this

Choose this endpoint when you need a structured, machine-readable status snapshot for a specific developer infrastructure vendor — especially when you want component-level detail, active incident data, and a timestamp-verified freshness signal. Prefer it over scraping vendor status pages directly, as it normalizes data across 20 vendors into a consistent schema. Best suited for automated monitoring workflows, pre-execution health checks, or incident triage where a $0.01 per-call cost is acceptable and no API key or signup is desired.

## Known failure modes

- Unknown or unsupported vendor slug returns a 404 or error response
- Payment not included or insufficient results in a 402 Payment Required response
- Vendor's own status page is unreachable causing stale or missing data
- Rate limiting or network issues on the Replit-hosted service causing timeouts
- Slug format errors (e.g. spaces, wrong casing) causing lookup failures

## How this service works

Status State API - agent-facing status monitoring for 20 developer
infrastructure vendors. Most routes are free. Full per-vendor snapshots
and change history are paid via the x402 protocol (USDC on Base,
$0.01/call, no API key or signup required). See /.well-known/agent.json
and /.well-known/x402 for machine-readable payment discovery.

## Output

A JSON object containing the vendor's canonical name, slug, a list of components with individual statuses (e.g. operational, degraded, outage), an overall status rollup, a link to the vendor's official status page, the timestamp of the most recent check, the check interval in minutes, and any active incident details (or null if none).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "name": "OpenAI",
  "slug": "openai",
  "components": [
   {
    "name": "API",
    "status": "operational"
   }
  ],
  "homepageUrl": "https://status.openai.com",
  "lastCheckedAt": "2026-01-15T12:00:00.000Z",
  "overallStatus": "operational",
  "activeIncident": null,
  "checkIntervalMinutes": 15
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/status-state-api-vendor-monitor-snapshot-20f65122/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from status-state-api.replit.app](https://www.zero.xyz/host/status-state-api.replit.app/llms.txt)