Service Incidents
Return active service incidents in normalized form.
Forest exposes this capability as a deterministic machine-readable API for software agents. Discovery is free; execution uses the canonical paid endpoint below. The live x402 challenge is the source of truth for payment terms.
$0.002 / callPOST /service/incidentsx402 · Base
Typical agent tasks
This capability is intended for bounded machine decisions such as:
- is this service having incidents
- find active service outages
- check recent service incident history
What Forest guarantees
- bounded normalized public-source lookup
Boundaries
- provider-specific guarantees
- unpublished facts
Machine contract
The request and response schemas are published in the canonical OpenAPI document. This page shows a representative input from the same production manifest.
Input example
{
"status_url": "https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run"
}
Canonical paid endpoint
https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/service/incidents
Related capabilities
- Service Component-status — Resolve the live state of a named service component.
- Service Status — Check the current service status published by an explicit public Atlassian Statuspage: operational, maintenance, degraded, partial outage, major outage or unknown, plus components, active incidents and scheduled maintenance. It reads the provider-published status page only and does not infer hidden backend health.
- Service Changed — Cheap watchdog: material service state changed since prior canonical hash?