Skip to content
oneapi.finance API Reference

Status

Live service status, current incidents, and historical uptime are published at:

status.oneapi.finance Open in a new tab. Updated continuously by the gateway and worker fleet.

What’s on the status page

  • Per-component state for the gateway, the worker fleet, the cache layer, the Postgres primary, and each upstream source we depend on.
  • Active incidents with rolling updates as we investigate and recover.
  • Historical uptime for the last 90 days per component.
  • Scheduled maintenance announcements at least 7 days in advance for anything that may degrade the gateway.
  • Post-mortems for incidents that exceeded 30 minutes of customer-visible impact.

Subscribing

The status page supports email and webhook subscriptions. We recommend subscribing your team’s incident channel (PagerDuty, Slack webhook, generic HTTP endpoint).

Programmatic check

A minimal “is the API up” probe:

Terminal window
curl -fsS -H "Authorization: Bearer oa_live_..." \
  -o /dev/null -w "%{http_code}\n" \
  https://api.oneapi.finance/v1/usage

200 is healthy. 5xx over multiple consecutive checks is a real outage. Use this as a synthetic monitor; we do not currently expose a dedicated /health endpoint on the public host.

Reporting an issue

If you observe a discrepancy between what the status page says and what your client is seeing, file a report at support@oneapi.finance with:

  • Time of the issue (UTC).
  • Source IP region (US, EU, APAC).
  • A few example request paths that returned the wrong status.
  • The value of meta.source you saw, if any.

We page on incidents but not on individual customer reports, so an early report from you can shorten our mean-time-to-detect.

See also