Dependency health
Read live from the API on page load. Each row is the instantaneous state of a dependency the service actually needs, not a summary written by hand.
| Component | Status | Detail |
|---|---|---|
| No live snapshot loaded. The public JSON endpoint reports storage, RPC and payment-rail health. | ||
Availability history
Availability is computed only from recorded samples. No current history has been loaded.
Observed success is the share of eligible checks that passed. Temporal coverage shows how much of each window those checks represent; a 100% observed success rate with incomplete coverage does not mean 100% availability for the full window.
Core service & gateway
Persistent storage, Base RPC reachability, and public HTTP gateway health. Legacy core series exposed as uptimeClaim.
Customer-path observations
Each customer-path series keeps its own evidence category. Observed success is a ratio of eligible genuine samples; it is not an uptime or SLA claim.
Public gateway
Synthetic 402 challenge
Synthetic HTTP probes verify 402 Payment Required challenge and Base-USDC terms advertisement on payable routes. They do not execute signed verification or payment settlement.
RapidAPI marketplace
Signed verify/settle evidence
Evidence from genuine signed payment verification and facilitator settlement transactions. Strictly separated from synthetic 402 challenge probes; scheduled health probes do not execute transactions.
Signed settlement evidence is verified on live production transactions only. No unmeasured synthetic settlement uptime is inferred.
Any figure shown here is computed from health samples recorded by the scheduled worker. If no figure is shown, none has been measured — we do not publish an availability number we cannot evidence. Growth and Pro catalogue figures are operational targets, not financially backed guarantees unless a separate signed agreement says otherwise; see the Terms of Service.
Raw response
Exactly what GET /v1/status returned.
…