Skip to main content
GET
Liveness check (public, no API key).

Response

200

Service is up: { "status": "ok", "upstreamRateLimitHits": n, "defiDegradedFallbackCount": n, "octoposConfigured": bool }. The first counter is how many upstream account-state requests the provider refused with 429 since this process started - a rising value is the signal to point PATH_ROUTING_API_* at a provider with more headroom. The second is how many DeFi-position reads fell back to a direct on-chain sweep because OctoPos was unavailable, unrecognizable, or not tracking the address. octoposConfigured is a plain deploy-time fact - false means OCTOPOS_API_URL_MAINNET was never set on this revision, so every mainnet DeFi read is degrading by design, not because OctoPos is having an outage. All three are weeks-early operational signals, not something discovered from a user's screenshot.