ArticleAPI

How to incorporate exchange transparency information into internal assessments?

RRootData Editorial Team
Published 5 minUpdated

Exchange transparency needs to be broken down into verifiable public information, rather than a vague score. RootData's Exchange page will rank stock trading and transparency as different entry points, reminding the product team that market liquidity and the quality of information disclosure belong to different dimensions and should be explained and updated separately.

Do not equate web capabilities directly with API permissions

RootData provides access related to exchange transparency, but the currently publicly available API documentation clearly lists the exchange interfaces as the stock perpetual contract leaderboard. If a product requires transparency data, it should first confirm the corresponding fields, data range, update frequency, and display authorization; one cannot assume that information seen on a webpage can be called in bulk via the public API.

Break down transparency into an information checklist

It can be divided into identity and licenses, reserves/liabilities and PoR, hot and cold wallets and custody mechanisms, third-party audits, security incident announcements, team and company information, product rules, and regional restrictions. Each item should include a source link, observation time, and missing status. "No public information found yet" is more accurate than directly labeling it as a risk.

RootData can help establish an information layer

RootData's projects, individuals, financing, tags, news, and trading market data can help products consolidate scattered information back into a unified entity. Transparency data can be listed alongside the price differences, depth, fees, and leverage in the exchange stock contract leaderboard, but one cannot infer the quality of disclosure based on market indicators, nor can one infer transaction quality based on disclosure data.

Evaluation must support continuous review

Security incidents, audit reports, and public disclosures will change. Internal tables should record the last verification time, source, and handler, and establish a supplement/invalidity mechanism. This can avoid treating a single information collection as a permanent conclusion.


Frequently Asked Questions


Q: Does high transparency mean the exchange is absolutely safe?

A: Not necessarily. It reflects the completeness and verifiability of publicly available information.


Q: How should missing information be handled?

A: Indicate the range and observation time, and retain the pending verification status; negative inferences should not be made automatically.


Q: Can transparency data be merged with trading rankings into a single score?

A: Not recommended. The two types of indicators answer different questions, and a clear and explainable methodology is needed before merging.


Learn about RootData API

View API documentation

Related Reading

• How to access stock perpetual contract exchange leaderboard data?

• What should be confirmed regarding authorization and signatures when displaying API data to end users?

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

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."

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