Acceptable Use Policy
1. Purpose
This policy sets out what you may and may not do with the API. It exists to keep the service available and accurate for everyone, and to make clear where responsibility sits when the output is used to make automated decisions.
2. You must not
- Circumvent authentication, rate limits, credit caps or payment enforcement, or attempt to.
- Share, resell or sublicense a key, or create multiple wallets to obtain additional free allowances.
- Resell bulk API access as a competing data or risk-scoring service.
- Send credentials in a URL query string. The API rejects these; deliberately retrying is abuse.
- Scrape, mirror or redistribute the API output as a standalone dataset.
- Use the service to plan, promote or execute fraud, market manipulation, rug pulls, phishing or theft.
- Use the service to attack, probe or stress-test infrastructure you do not own — including the RPC endpoints and third-party data sources we relay from.
3. Rate limits and concurrency
Stay within the tier limits set out in the documentation. Do not hammer endpoints when rate-limited.
The service sends standard rate-limit headers (including Retry-After on 429 responses); honour them.
Sustained flooding will trigger IP-level or subnet-level blocking.
4. Automated trading and execution
If you use API output to drive automated transactions, you are solely responsible for the transactions your systems submit. The API is a factual observation layer, not an investment advisor, auditor or execution guarantee. You must build your own fallbacks, slippage controls and circuit breakers.
5. Security research
Good-faith research is welcome. Report findings to [email protected] and give us reasonable time to fix an issue before disclosing it. Do not access other users' data, degrade the service for others, or run high-volume automated attacks. We will not pursue legal action against research that follows this section.
6. Enforcement
We may throttle, suspend or permanently revoke a key for a breach of this policy. Serious breaches — payment enforcement bypass, attacks on infrastructure, or use of the service to facilitate fraud — result in immediate termination without refund, and may be reported to the relevant authorities.
Where a breach is likely inadvertent, we will normally contact you first. If you believe an enforcement action was mistaken, appeal to [email protected].
7. Reporting abuse
Report misuse of the service to [email protected] with the relevant timestamps and, where possible, the transaction hashes or key digest prefix concerned.