What this page is and is not
- Status updates describe customer-visible discovery and contract posture.
- Source status lives separately at /source-status.
- This page is not an uptime SLA, internal incident timeline, or legal opinion.
Public contract reliability
This page explains how SmartAPIs communicates customer-facing incidents, how the public discovery surface is monitored, and how versioning and deprecation are handled for public contracts. It is intentionally customer-readable, not an internal operations console.
At a glance
The summary below is published from a machine-readable status feed so customers and agents can inspect public contract reliability without authentication.
Machine-readable feed: GET /status.json
Canary-covered discovery surfaces
These discovery surfaces are expected to stay publicly reachable and machine-readable. Regressions here should block or at least halt release confidence.
Versioning and incidents
Versioning and deprecation policy is intentionally conservative. Incidents should be communicated in plain language with clear customer impact and next-step guidance.