Report an issue or get help

Write to 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.

Is it down, or is it me?

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, 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 or Hoodscan), 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.

Subject: Wrong data: <full token address>

Request:    GET /v1/robinhood/token/<address>/security
meta.block: <block from the response>
Returned:   <the field and its value, e.g. tax.sell_pct>
Expected:   <the value you think is right>
Source:     <explorer link or transaction hash, and how you worked it out>

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, token prices and 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 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: creating, rotating and revoking keys, usage, and plans on the Billing page. For anything else, email account or billing help 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 instead. Payments are on-chain and final; refunds follow the refund policy. 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 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.

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

Related