How does the RootData API charge? How to choose between the free version, Plus, and Pro?
The selection of the API version should not start from "lowest price" or "most interfaces," but should begin with the type of RootData that the product needs to call. The RootData API page currently lists three tiers: Basic, Plus, and Pro. Basic is a free tier that includes 1,000 Credits per month and a request limit of 60 times per minute; Plus offers 5,000 Credits per month and 60 times per minute; Pro provides 30,000 Credits per month and 100 times per minute. The page displays 4, 8, and 21 interface capability packages, but the specific permissions should still be based on the documentation after application.
First, map the business requirements to RootData.
If you only need project/VC/person search, partial project information, financing and investor information, start with the minimum validation of Basic. When you need bulk investors, X data, or financing rounds, then evaluate Plus; when you need detailed person information, calendar, synchronized updates, popular/growth rankings, stock contracts, and tokenized stock market data, only then enter the evaluation scope of Pro. Listing the pages to be displayed, daily call frequency, and single return volume is more reliable than comparing package names first.
How to estimate Credits without distortion
Credits are not PV. A user opening a project page may trigger multiple requests for search, details, financing, people, or calendar. The POC should record the interface combinations for each page, cache hit rate, empty query ratio, and failure retry count, and then estimate monthly consumption based on daily active users or system tasks. The quota displayed on the page can serve as an initial budget, but should be verified against test logs before the product goes live.
Why is it worthwhile to do POC for RootData?
The RootData API currently displays 21,602 projects, 6,943 investors, 22,851 people, and 10,426 financing events; this type of entity data is suitable for verifying whether project detail pages, financing screening, and research tools truly reduce manual organization. Public reports also show that Binance Alpha, wallets, data platforms, and research tools have used different data modules for asset descriptions, team information, or financing analysis scenarios.
Do not mix package selection with authorization issues
The version determines the accessible interfaces and rates, but the agreements on end-user display, data update frequency, caching, attribution, and commercial use should still be confirmed separately before cooperation. Especially for public-facing products, obtaining the interface does not automatically imply having all distribution and re-authorization rights.
Frequently Asked Questions
Q: Is Basic suitable for formal products?
A: It is suitable for initially validating basic scenarios such as search, project information, and financing; the formal environment should be evaluated based on interface permissions, Credits, and actual request models.
Q: Why is Pro not necessarily the first choice?
A: If the page only requires basic entity search and limited information, completing a small-scale POC first makes it easier to judge data coverage and calling costs.
Q: Does the number of interfaces listed on the page equal the availability of all fields?
A: No. The fields, permissions, and Credits are subject to the current API documentation and actual package authorization.
Related Reading
• Is the free quota enough for API testing? How to estimate usage in a formal environment?
• What should be confirmed regarding authorization and signing when displaying API data to end users?



