ArticleAPI

When displaying RootData API data to end users, what should be confirmed regarding authorization and signatures?

RRootData Editorial Team
Published 5 minUpdated

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

View API Documentation

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?

Related content

APIArticle

How does the wallet automatically complete the project background behind tokens?

When wallet users view a token, they usually also need to know which project it corresponds to, who the team members are, whether it has secured funding, or if there are upcoming events. The RootData API can supplement structured data such as projects, individuals, funding rounds, calendars and news to the asset page, enabling wallets to evolve from a "balance and price interface" into a verifiable information portal.

RRootData Editorial Team
5 min
APIArticle

How to choose a Web3 data API: Build, buy, or combine?

Building in-house and procurement are not mutually exclusive. For Web3 products, the real decision is which data must be collected and defined internally, and which structured foundational data is more suitable for direct integration. The RootData API organizes project, financing, investor, person, tag, ecosystem, calendar, leaderboard, and tokenized market data into callable capabilities, reducing the repetitive investment in entity cleaning and relationship maintenance.

RRootData Editorial Team
5 min
APIArticle

Is the free quota sufficient for testing the RootData API? How can I estimate the usage in a production environment?

The Basic plan of the RootData API currently provides 1,000 Credits per month and a limit of 60 requests per minute, which is sufficient for small-scale field, coverage, and product experience validation; however, it cannot replace production usage assessment. What really needs to be tested is: which RootData data objects are called each time your page or Agent completes a user task.

RRootData Editorial Team
5 min
APIArticle

After the project information is updated, how can API users perform incremental synchronization?

This article focuses on engineering implementation rather than discussing "whether the data is new." The Synchronous Update (Pro) of the RootData API provides an entry point for discovering changed objects; the product needs to be designed as a stable, rerunnable, and auditable synchronization task to truly enable continuous updates for project pages, financing pages, and person pages.

RRootData Editorial Team
5 min