ArticleAPI

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

RRootData Editorial Team
Published 5 minUpdated

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.

Start with a real scenario POC

For example, when creating a project detail page: first search for the project, confirm the RootData entity ID, and then read the basic project information, financing/investor or personnel information. When creating a tokenized asset dashboard, you need to test target filtering, market segmentation, pricing, liquidity, and data status. Don't just call one interface to confirm "data can be returned," but run through the complete path of a user completing a research or browsing session.

Estimate Credits using call combinations instead of user counts

A single user may generate multiple requests such as search, details, financing, calendar, and refresh; the backend will also have synchronization, cache warming, and failure retries. During testing, record the number of requests for each page, the Credits for each type of interface, cache hit rates, and peak concurrency, and then extrapolate to daily active users and backend tasks to determine whether 1,000 Credits is sufficient.

Selection logic for Basic, Plus, and Pro

The API page currently lists Basic with 4 ports, Plus with 8 ports, and Pro with 21 ports; Pro also provides 30,000 monthly Credits with a limit of 100 requests per minute. If the POC has verified the value of the basic data, then choose to upgrade based on whether batch data, personnel/calendar, synchronization, leaderboard, or tokenized stock capabilities are needed, and do not skip verification just because of the number of interfaces.

What should be重点核验 in RootData POC

Verify whether the project/personnel/financing coverage meets the target users, whether the fields are interpretable, whether the source and update time can be displayed, whether the entity ID is convenient for database storage, and whether the cooperation authorization covers terminal display. Only if all these conditions are met is it worth entering formal integration.

Frequently Asked Questions

Q: What scenarios is Basic suitable for testing?

A: It is suitable for the minimum closed loop of search, basic project information, financing/investors, etc.; specific permissions are subject to the current package.


Q: How to reduce the consumption of testing Credits?

A: Use small samples, cache responses, limit repeated queries, and record each call.


Q: When should I upgrade to Pro?

A: When the product clearly requires the capabilities listed in Pro such as synchronization, leaderboards, personnel, calendars, or tokenized markets, and the POC has verified the value.


Understanding RootData API

View API documentation

Related Reading

• How is RootData API charged? How to choose between free, Plus, and Pro?

• How to choose Web3 data API: self-built, purchased, or combined?

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

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