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.
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.
Typical agent tasks
This capability is intended for bounded machine decisions such as:
- check the current service status published on this Atlassian Statuspage
- read whether a service is operational degraded under maintenance or in an outage
- inspect active incidents components and scheduled maintenance on a public status page
- get the provider-published current status for this service
What Forest guarantees
- bounded public Statuspage summary lookup
- normalized component and incident states
Boundaries
- provider-independent discovery
- hidden backend health
- SLA interpretation
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
Canonical paid endpoint
Related capabilities
- Service Component-status — Resolve the live state of a named service component.
- Service Incidents — Return active service incidents in normalized form.
- Service Changed — Cheap watchdog: material service state changed since prior canonical hash?
- Automation Preflight — Preflight one public Apify Actor before a paid automation run using only public Store and default-build OpenAPI metadata. Forest checks agentic-payment eligibility, pricing/budget signals and top-level input compatibility without starting an Actor, buying credit, authenticating or making an external payment.
- Chain Gas-snapshot — Return one bounded current EVM fee-history snapshot for a fixed supported chain using SolidRPC public JSON-RPC. Forest reports recent base-fee and latest sampled-block priority-fee percentile evidence only; it does not estimate a caller transaction gas limit, simulate, sign or broadcast a transaction, access a wallet, choose a transaction fee for the caller or guarantee an optimal fee.
- Commerce Purchase-preflight — Combine public product resolution, one fresh isolated anonymous cart, optional delivery lookup and checkout handoff evidence into one bounded purchase preflight. Shopify Ajax and WooCommerce Store API are supported; Forest never logs in, touches a customer session, creates an order or attempts payment.