Search returns the wrong entity
Add an entity type, chain, ticker, handle, or related project. Reused names and symbols are common in crypto, so a narrower query helps entity resolution.A profile is missing data
Missing data can mean the source does not publish it, the record has not been resolved, or the available evidence did not pass validation. Check related entities and source links before assuming a zero value.A market number looks stale
Check the observation time and refresh the page. Market, TVL, news, and social datasets update on different schedules. Report a persistent stale value with the page URL, field name, displayed timestamp, and a current source.A cited page does not match the claim
Confirm that the citation points to the same entity, date, and unit. Report the answer URL, exact claim, citation, and a better source when available.Credits were charged unexpectedly
Check whether the action was a direct lookup, an AI answer, or a deeper comparison. Developer API responses include credit-use metadata. Contact support with the request or chat identifier; never send an API-key secret.An API key fails
Confirm the key is active, has the required scope, and is sent as a bearer token. Disabled and revoked keys fail before credit or rate-limit checks. Rotate a key if its secret may have been exposed.The API returns a rate-limit error
Wait until the response reset time, reduce request concurrency, and use bounded queries. Retrying immediately in a tight loop can extend the problem and consume unnecessary work.The MCP client cannot connect
Confirm the client supports Streamable HTTP, sends the requiredAccept values,
and includes the API key as a bearer token. Browser clients also need an allowed
origin. MCP access remains limited during beta.