Operational Status
Status and incident visibility for the Decision API.
Public snapshot of runtime readiness, metrics ingestion, and incident communication paths for Decide. This page is refreshed from live endpoints while restricted counters stay protected.
Availability metrics on this page are monitor-scoped telemetry for listed endpoints and are not contractual uptime terms.
Live sources: /api/runtime-config, /api/metrics, /api/uptime, /api/compliance-export?format=json.
Buyer readiness packet
Use this page as the operational packet for first review: live readiness, monitor coverage, exportable evidence, and the path for incident escalation.
Runtime readiness
Inspect runtime blockers, metrics mode, monitor suite status, and readiness export fields before connecting a production action boundary.
Evidence export
Download the readiness CSV or open JSON for procurement notes, launch review, or internal implementation signoff.
Escalation path
Use support@decide.fyi with runtime incident or security incident, plus any available request_id and decision_id.
| Review question | Where to inspect | Buyer expectation |
|---|---|---|
| Is the runtime ready for a production boundary? | Live service snapshot and readiness breakdown. | No active blockers before irreversible downstream actions depend on Decide. |
| Are public endpoints being monitored? | Public Monitor Suite and 24h uptime strip. | Monitor telemetry should be current and scoped to Decide endpoints. |
| Can review evidence be exported? | Readiness export CSV and JSON preview. | Export should be available for launch packet, security review, and procurement notes. |
| What happens when a dependency is unavailable? | Error reference and incident response process. | High-risk software actions should fail closed or route to review. |
| Where are security and data boundaries documented? | Security packet. | Data scope, verification, key handling, and incident paths should be explicit. |
Live service snapshot
Status checks are sourced from /api/runtime-config and /api/metrics. Some metrics remain token-gated by design.
Runtime config
Public readiness scaffold; live checks populate this card after refresh.
Metrics ingest
Public metrics are limited by design; authenticated review exposes full production counters.
Incident channel
For urgent issues, email support@decide.fyi with subject security incident or runtime incident.
Last checked: public snapshot initializes on page load.
Public Monitor Suite
External monitor coverage for public decide endpoints, sourced from UptimeRobot monitor status.
Interpretation rule: monitor status reflects configured probe behavior for each endpoint, not full-system guarantees beyond published runtime scope.
Primary runtime monitor (UptimeRobot)
Public monitor ratios initialize from the configured endpoint suite.
--
| Monitor | Status | Interval | 30d uptime | 90d uptime | Endpoint |
|---|---|---|---|---|---|
| Public monitor suite initializes from configured endpoint probes. | |||||
A healthy suite should show all key runtime and reference-application endpoints as Up. Uptime windows reflect trailing 30d and 90d ratios.
Readiness breakdown
| Signal | Current value | Interpretation |
|---|---|---|
| Commercial readiness | Public snapshot | Derived from configured intake, checkout, alerting, and confirmation channels. |
| Active blockers | Public snapshot | Non-empty blocker list indicates rollout follow-up is required. |
| Metrics endpoint mode | Public view | Public view may be limited while full counters remain token protected. |
| Metrics update timestamp | Token-gated if limited | Fresh timestamps indicate event ingestion is active. |
| Uptime ratios (30d / 90d / all-time) | Public monitor snapshot | Sourced from UptimeRobot monitor-specific API telemetry. |
| Estimated downtime (90d) | Public monitor snapshot | Derived from 90-day uptime ratio. |
Readiness export
Download the latest operational readiness CSV from /api/compliance-export and inspect JSON summary data from /api/compliance-export?format=json. The route name is historical; the public artifact is a readiness snapshot, not a certification report.
Endpoint health
Public readiness export initializes from the snapshot endpoint.
Snapshot details
- Generated atPublic snapshot
- Record countPublic snapshot
- SourcePublic snapshot
- WindowPublic snapshot
- request_idPublic snapshot
- Top-level fieldsPublic snapshot
JSON preview
Public readiness snapshot initializes from /api/compliance-export?format=json.
Incident response process
Customer-facing updates use support@decide.fyi. High-priority incidents are acknowledged with request_id-linked context for follow-up.
Delivery failures and readiness blockers trigger immediate operator review and retry/route fallback workflows.
This page reflects current operational mode and whether observed issues are blocking production API readiness.