# api-status-oracle

> "Does this vendor's public status page say they are up right now?" You give a provider id; you get one JSON object with an overall state, a short description, up to 40 components and up to 10 incidents.

- Status: MCP package (hosted access coming soon)

## What question it answers

"Does this vendor's public status page say they are up right now?" You give a provider id; you get one JSON object with an `overall` state, a short description, up to 40 components and up to 10 incidents.

## When to use it

- An agent wants a cheap check before retrying a failing call to one of those vendors.
- You want one shape across vendors instead of parsing each status page.

## When not to

- It reports what the vendor's own status page says. It does not probe the vendor's API, so it can lag a real outage.
- Not for providers outside the list (unknown ids return an error).
- Be careful with `stripe`: the Stripe-specific parser is currently unreachable (known issue) and the endpoint used for Stripe has not been verified.

## Data source and licence

Each vendor's public status-page JSON (Atlassian Statuspage format for most; Slack's own API). The data belongs to those vendors; check their terms. This tool adds no data of its own.

## Freshness and limits

- Cached 2 minutes per provider.
- Components capped at 40, incidents at 10, batch at 12 providers.
- 20 s timeout, 5 MB response cap.
- Heuristic: the `overall` mapping is a fixed table, not a judgment.