Live status on this deployment
What each provider contributes
How freshness works
Every API response carries the time it was generated, and the interface shows Updated N seconds ago next to the data it describes. Server-side caches are short and use stale-while-revalidate so a burst of visitors never becomes a burst of upstream calls; the browser refetches on an interval matched to each feed. Provider failures are reported per provider (“DexScreener is currently unavailable”) and the rest of the page still renders from the sources that did respond.
Explorers
Secret keys never reach the browser. All provider calls run in server routes under
/api/*; the client only ever receives normalised data and boolean “configured” flags.