Incidents Json

Machine-readable incident history. Public, no auth, no credits.

Returns an ordered list of platform incidents (most recent first) with start / resolved timestamps, impact summary, root cause, resolution, affected endpoints. Customers ingest this for:

• Vendor reliability scoring matrix.
• SLA-compliance verification (the times we missed our targets).
• Status-page rollups (some customers render their own).
• AI agent answering "has ParlayAPI been reliable recently?"

Empty / short record is itself a meaningful signal — the absence of incidents over a long window indicates a stable platform.

Source-of-truth is src/api/static/incidents.json (human-edited, git-versioned). Each incident has a stable id so customers can dedupe across polls.

Stability promise: id, title, status, severity, started_at, resolved_at, impact keys will not be removed or renamed without bumping version.