When displaying RootData API data to end users, what should be confirmed regarding authorization and signatures?
Displaying API data on web pages, wallets, exchanges, or AI responses is just the first step in technical connectivity. The product also needs to confirm the display range of fields, update and caching rules, source identification, redistribution permissions, and the visible boundaries of user responsibilities, to avoid misunderstanding "can be called" as "can be used freely."
What kind of attribution reference does the public case provide?
Binance Alpha page marks "Data from RootData"; HashKey Exchange asset page displays "sourced from RootData"; Coinglass, Blockworks, and CertiK's public pages also show RootData as the source. These cases illustrate that visible sourcing is not only a brand display but also helps users understand which structured data layer the information comes from. They do not automatically define the scope of authorization for other partners.
Confirm four types of issues before going live
First, which interface fields can be publicly displayed; second, whether caching, secondary processing, or redistribution to end users is allowed; third, attribution text, links, and placement; fourth, how to handle data updates, error corrections, and page management when terminating services. Writing these matters into product requirements and business confirmations is more prudent than remedying them after going live.
Source identification should appear alongside data explanations
The update rhythms for projects, financing, personnel, and market data differ, so the page should ideally display the RootData source, the last update time, and necessary original source links simultaneously. For financing, a source_url and status can be attached; for tokenized market data, collected_at and data_status should be included. Attribution should not be used to imply that RootData endorses the project, exchange, or conclusions.
AI and content products must be particularly cautious
If API data has been summarized, scored, or edited by a model, it should distinguish between "data returned by RootData" and "the product's own analysis." Conclusions generated by models cannot masquerade as the original words of the data source, nor can they omit key uncertainties and time conditions.
Frequently Asked Questions
Q: Does marking the RootData source equal obtaining display authorization?
A: No. Source attribution and the scope of authorization should be confirmed separately.
Q: Do all pages need to display the source?
A: It should follow the cooperation agreement; for key data modules aimed at users, clear sourcing usually helps with understanding and tracing.
Q: Can RootData data be used for automatic scoring?
A: Authorization must be confirmed first, and it should be clear to distinguish between original data and scores formed by proprietary models/rules.
Understanding the RootData API
Related Reading
• How does RootData API charge? How to choose between Free, Plus, and Pro?
• How to choose Web3 data API: self-built, purchased, or a combination?



