Caching & Freshness
Every REST endpoint is fronted by an in-process LRU cache, so repeat reads return in microseconds instead of a database round-trip. Each cache has a TTL tuned to how fast its data changes — a response can be up to that many seconds stale.
| Endpoint group | Cache TTL |
|---|---|
| OHLCV candles | 5s |
| Bundles | 15s |
| Wash trades | 15s |
| Buyer quality | 30s |
| Wallet performance | 30s |
| Coordination | 30s |
| Wallet labels | 60s |
| Wallet profile | 60s |
| Leaderboard | 60s |
| Provenance | 300s |
| Token info | 300s |
REST is for backfill and point lookups. For zero-latency, uncached data, subscribe to the matching WebSocket stream — events are pushed the moment a transaction lands, with no cache in the path.
Compression
All responses support gzip. Send Accept-Encoding: gzip to cut transfer size on large payloads (holder lists, trade history, bundle rosters).