How to combine financing, relationships, and leaderboard data for a Web3 investment research terminal?
What research terminals truly need is not more tabs, but a verifiable research path. RootData organizes projects, investment institutions, individuals, financing events, tags, ecosystems, X signals, calendars, and rankings into structured objects, allowing users to gradually trace back from a research question to the corresponding entities and sources.
First, use the data network of RootData to define the research object
The RootData API homepage currently displays 21,602 projects, 6,943 investors, 22,851 individuals, 10,426 financing events, as well as 258 tags and 259 ecological classifications. These can form the foundational dimensions of an investment research terminal: first determine the track or ecology, then filter projects; look back at financing and investors from the projects; and view public relationships and dynamics from team members.
Financing, individuals, and rankings address different issues
Financing records are suitable for observing where capital is entering and whether the sources are traceable; individual and institutional profiles are suitable for establishing team and investment relationship backgrounds; the RD Hot Index, RD Growth Index, and X-related capabilities are used to discover recent objects worthy of further research. Rankings are only responsible for discovery or sorting and cannot replace due diligence; financing amounts also cannot replace project quality judgments.
Design the research process as a replayable workflow
It is recommended to save three levels: filtering conditions, RootData entity ID, and the snapshot of fields at that time. For example, first obtain candidate projects by tags/ecology, then read financing and investors, and finally supplement with teams, calendars, and hot signals. This way, when conclusions change, researchers can return to the data conditions used at that time, rather than just retaining a textual conclusion.
The actual access value of the RootData API
Public cooperation reports show that Blockworks uses RootData financing profiles for Funding and M&A data analysis scenarios, while Coinglass places investor and team information on asset pages. This indicates that the same set of structured data can serve research, trading information pages, and institutional workflows; however, products still need to confirm actual fields based on authorization and version.
Frequently Asked Questions
Q: Can projects be filtered using only financing data?
A: Not recommended. Financing is one dimension and should also be combined with track, team, public information, time, and source information.
Q: Can the RD index represent investment advice?
A: No. The index is used for discovery and sorting, and the final judgment still requires independent research.
Q: What key fields need to be saved in the research terminal?
A: At least include entity ID, query conditions, data time, source, and important field snapshots.
Understanding the RootData API
Related Reading
• AI Assistant: How to access traceable project financing data?
• How to disambiguate entities for projects with the same name and multi-chain tokens in the API?



