ArticleAPI

To create a Web3 project detail page, how should the team, funding, and official links be integrated?

RRootData Editorial Team
Published 5 minUpdated

A usable Web3 project detail page should not only display the project name and token price. The advantage of the RootData API lies in organizing project entities along with information about teams, funding, investors, tags, ecosystems, calendars, and more into the same data network, allowing users to continue verifying the project background from the asset entry point.

What data layers should the project page inherit?

The first layer is basic project information: introduction, tags, ecosystem, official website, and social media; the second layer is team and personnel: roles, backgrounds, and public accounts; the third layer is financing: rounds, announcement time, amount, valuation, investors, and source status; the fourth layer is calendar and dynamics. RootData API currently covers 21,602 projects, 6,943 investors, 22,851 individuals, and 10,426 financing events, making it suitable as a structured data foundation for detail pages.

First, use search and ID to solidify the page body

When the page is first created, determine the RootData entity ID through Project/VC/People Search, and then call the project, person, financing, or calendar capabilities by ID. Do not treat the token code as the only identifier for the project: projects with the same name, migrations, or multi-chain assets may cause mismatches. The Full Data ID of RootData and the update notification capability can also be used for subsequent maintenance.

What do collaboration scenarios explain?

Gate has integrated project introduction, team, and financing information on the trading pair page; HashKey's asset information page displays project data, tags, official links, total financing, and market value, and marks the source as RootData. These public pages reflect not just "adding more fields," but connecting the trading entry with the project's fundamentals, helping users complete the minimum information verification before taking action.

Detail pages should display sources and empty values

When financing is not publicly available, team information is missing, or sources are unverified, it should be displayed as empty or marked with a status, rather than automatically filled in with inferences. Important fields should retain the RootData data update time and source link; project information can assist understanding but should not be written as security, compliance, or profit commitments.

Frequently Asked Questions

Q: Does the project detail page have to display all fields?

A: No, it is not necessary. Priority should be given to displaying information that users can verify and that is relevant to the page's task, and then gradually expand.

Q: How can financing information avoid misinterpretation?

A: It should display rounds, announcement time, investors, sources, and data status simultaneously, avoiding conclusions based solely on a single financing amount.

Q: Can I only use the token symbol to query projects?

A: It can serve as a search entry, but long-term associations on the page should be based on the returned entity ID.

Understanding RootData API

View API Documentation

Related Reading

• How does the wallet automatically complete the project background behind the token?

• How to build a searchable Web3 project directory product?

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