Errors and limits
HTTP behavior
| Status | Meaning |
|---|---|
402 | Payment required |
404 | The requested token is not present in indexed data |
422 | Invalid chain, address, query, body, or insufficient launch-history coverage |
429 | Route concurrency is exhausted; retry with backoff |
503 | A dependency or idempotency store is unavailable |
504 | The bounded route deadline was exceeded |
Response quality
cache_status is hit, miss, error, or unknown. It describes the data
response cache, not paid-request idempotency.
Freshness fields are measured from the evidence that supports a value. Missing,
stale, or incoherent market values can be omitted. Old tokens discovered after
launch may return a structured DATA_UNAVAILABLE_OLD_TOKEN error instead of a
precise-looking partial analysis.
Fixed limits
- Batch analysis accepts 1–20 items.
- Recent alerts cover the preceding ten minutes.
- Token wallet cohorts are bounded to five rows per group.
- Unexpected query parameters are rejected on strict endpoints.