# Report an issue or get help > How to report wrong Robinhood Chain data or a docs issue to Crius, what to include so it can be checked, account and billing help, and the status page. Source: https://docs.crius.sh/support/ · Updated 2026-10-28 Write to **[support@crius.sh](mailto:support@crius.sh)** for anything: data that looks wrong, a docs page that is unclear, account, key and billing questions, or a launchpad you’d like attributed. It is the only support address. Before you write about an outage, check **[status.crius.sh](https://status.crius.sh)**. ## Is it down, or is it me? 1. **Check [status.crius.sh](https://status.crius.sh)** for ongoing incidents and uptime history. 2. **Call `GET /v1/status`.** It is public and needs no key. `status: "live"` with a small `lag_ms` means the index is following the chain; `catching_up` or `stalled` means data is behind for now. See [Service status](https://docs.crius.sh/reference/chain/service-status/). 3. **Read the error code.** A `4xx` with `error.code` usually says exactly what to change (a key, a plan, a parameter). The [errors page](https://docs.crius.sh/errors/) lists every code and what to do about it. ## Report wrong data If a price, holder count, tax, PnL or label looks wrong, tell us. Data reports are the most useful messages we get, and a precise one can be checked the same way you checked it. **[Email a data report](mailto:support@crius.sh?subject=Wrong%20data%3A%20%3Ctoken%20address%3E&body=Endpoint%20and%20full%20request%3A%0A%0Ameta.block%20of%20the%20response%3A%0A%0AWhat%20the%20API%20returned%3A%0A%0AWhat%20you%20expected%2C%20and%20where%20you%20saw%20it%20%28explorer%20link%2C%20tx%20hash%29%3A%0A)**, and include: - **The address**: the full token, pool, wallet or hook address (`0x` and 40 hex characters, or the 32-byte id of a v4 pool). - **The request**: the endpoint and the full path with its query, for example `GET /v1/robinhood/token/0x7b8892cea949bc60d494681d1bc3ea96071ab0b8/holders?limit=5`. Leave out your API key. - **The block**: `meta.block` from the response, so we can look at the chain exactly as the API saw it. If you compared with a specific transaction, add its hash. - **What you expected and why**: the value you think is right and where it comes from: an explorer page ([Etherscan](https://robin.etherscan.io) or [Hoodscan](https://hoodscan.co)), a transaction, the token’s own contract. - **When**: the time you made the request, if `meta.block` isn’t at hand. Every example on this site has a **Data looks wrong? Report it** link that opens an email with the example and its request already filled in. ```text Subject: Wrong data: Request: GET /v1/robinhood/token/
/security meta.block: Returned: Expected: Source: ``` Some values are not wrong, only measured differently from other sites: `liquidity_usd` is 2 × the quote side of a pool, `market_cap_usd` leaves out burned tokens, concentration stats leave out pools and lockers, and candles leave out outlier trades. The [conventions](https://docs.crius.sh/conventions/), [token prices](https://docs.crius.sh/concepts/token-prices/) and [holder classes](https://docs.crius.sh/concepts/holder-classes/) pages explain each. If a number still looks off after reading them, send it anyway. ## Report a docs issue Every page ends with **Report an issue with this page**, which opens an email with the page address filled in. Tell us what was wrong, missing or hard to follow, or **[email a docs issue](mailto:support@crius.sh?subject=Docs%20issue%3A%20%3Cpage%3E&body=Page%20URL%3A%0A%0AWhat%20is%20wrong%20or%20missing%3A%0A)** directly. A broken example, a field that doesn’t match the response or a guide that skips a step are all worth a message. ## Account, keys and billing Most account tasks are self-serve on the [dashboard](https://dashboard.crius.sh): creating, rotating and revoking keys, usage, and plans on the [Billing page](https://dashboard.crius.sh/billing). For anything else, **[email account or billing help](mailto:support@crius.sh?subject=Account%20or%20billing%3A%20%3Cyour%20account%20email%3E)** with: - the email address of your Crius account; - for a key problem, the key’s public **prefix** (the `AbCd1234` part of `crs_live_AbCd1234_…`) and the error code you got; - for a payment, the wallet address you paid from and the transaction hash of the payment on Robinhood Chain. Never send a key’s secret, a seed phrase or a private key: nobody at Crius needs them or will ask for them. A lost key can’t be recovered (only a hash of it is stored), so [rotate it](https://docs.crius.sh/authentication/) instead. Payments are on-chain and final; refunds follow the [refund policy](https://crius.sh/refunds/). For more than the Business plan, or an Enterprise agreement, write to the same address. ## Launchpads and contracts If your launchpad’s tokens show `creation.attribution` other than `known_launchpad`, or a contract of yours has no label, **[email an attribution request](mailto:support@crius.sh?subject=Attribution%20request%3A%20%3Cproject%20name%3E)** with the project’s name and website and every contract address (factory, curve, hook, locker, router). ## What to expect We read every message. We try to reply within a few business days. Data issues sometimes need a fix to the indexer and a re-check of history, so a correction can take longer than the first reply. There is no guaranteed response time. Changes to the API are listed in the [changelog](https://docs.crius.sh/changelog/). If you’ve found a security problem in the API or the dashboard, email it with **Security** in the subject and don’t share it publicly until we’ve answered. ## Frequently asked questions **How do I contact Crius support?** Email [support@crius.sh](mailto:support@crius.sh). It is the only support address, for data issues, docs, accounts, billing and partnerships alike. **How quickly does Crius answer?** We read every message and try to reply within a few business days. A data issue that needs investigation can take longer to fix than to acknowledge. There is no guaranteed response time, so for outages check status.crius.sh first. **Should I send my API key when I report a problem?** No. Never send the secret part of a key, a seed phrase or a private key, and nobody from Crius will ask for them. The key's public prefix (the `AbCd1234` part of `crs_live_AbCd1234_…`) is enough for us to find it. **The API looks down. Where can I check?** status.crius.sh shows uptime and incidents. `GET /v1/status` (public, no key) shows the index's own state: `live`, `catching_up`, `stalled` or `starting`, with the indexed block and the lag behind the chain. ## Related [Docs **Errors** Crius API error format, HTTP status codes and every error code with its meaning and what to do about it. Read](https://docs.crius.sh/errors/) [Docs **FAQ** Answers to common questions about the Crius Robinhood Chain API - pricing, free plan, data freshness, coverage, history, rate limits, payments and support. Read](https://docs.crius.sh/faq/) [Docs **Plans, limits & credits** Crius API plans (Free, Starter, Pro, Business, Enterprise), monthly credits, requests per second, WebSocket limits, credit cost per endpoint and the rate-limit response headers. Read](https://docs.crius.sh/plans-and-limits/) [Docs **Authentication & API keys** How to authenticate Crius API requests with the x-api-key header, key scopes, IP allow-lists, browser origins, expiry, rotation with a grace period, and dashboard sessions. Read](https://docs.crius.sh/authentication/) [API reference **Service status API** Per-chain index health: status (live, catching\_up, stalled, starting), indexed block, lag behind the chain head, safe and finalized blocks, and how many tokens, pools and addresses are indexed. Read](https://docs.crius.sh/reference/chain/service-status/) [Docs **Changelog** Every change to the Crius Robinhood Chain API, the dashboard and the documentation, newest first, with new endpoints, fields and behaviour changes. Read](https://docs.crius.sh/changelog/)