Dappradar's Trader API plan paired data access with a monthly call allowance

How many calls did the Trader plan include?

The Trader tier introduced in May 2023 included 2,500 API calls per month. Its $9.99 monthly price covered subscription access, while the allowance described the included request capacity. An integration needed to account for data requests across the allocation period. The number of charts or observations shown on screen did not, by itself, measure that demand.

Data retrieval and request parameters

The 2023 introductory interface used GET requests to retrieve data, with an API key providing access. An endpoint selected the kind of information the application requested.

Request selection

Request parameters gave each query a target and a measurement context. Changing a reporting window could change the returned observations without changing the subscription.

The application or collection

The documented identifiers included dappID for applications and collectionID for NFT collections. Each endpoint expected identifiers appropriate to its subject. A collection identifier and an application identifier described different objects, even when one project had both.

The chain and time range

Parameters such as chain and range refined the blockchain and observation period. The API also supported requests for top dapps by chain, category and time window. That made rankings available for research without requiring a manual copy of each displayed entry.

Credential handling

The API key belonged in private request configuration. Public code samples or shared notebooks could expose it to other people. Anyone possessing usable credentials could attempt requests under that access. Sharing the resulting analytics did not require publishing the access key alongside them.

Was the monthly allowance a request-speed limit?

The monthly allowance did not establish a request-speed limit. It described total included usage over the allocation period. A separate throttling rule would govern burst traffic or short intervals. Dividing the allowance across days could support budgeting without creating a documented daily cap. Staying below a monthly total therefore did not establish whether a burst of requests would be accepted.

Reusing responses changed the freshness trade-off

Where response rules permitted storage and reuse, an application could display retrieved analytics without a new upstream request. Request savings came from skipping retrieval, not merely redrawing the interface. Revalidating a stored response could still generate another upstream request. Identical charts could therefore have different request demand because their applications used different retrieval patterns. An integration's tolerance for older observations helped determine when reuse remained appropriate.

Open full-size image

A response's retrieval time and its observation window also had different meanings. Retrieving data later did not make historical observations current. Likewise, redrawing a chart did not extend the period its underlying response covered. A snapshot remained useful for questions about that recorded window. Analysis sensitive to new activity needed fresh observations and access to a suitable feed.

Explorer and On-demand addressed different budgets

The May 2023 offer gave Explorer 100 free calls and reserved parts of the data offering for paid tiers. Explorer therefore involved constraints on data access alongside its call count. Trader provided paid API access under its monthly allocation.

Open full-size image

On-demand used a different cost structure: $0.005 per call in the May 2023 pricing change. Metered access connected cost to usage, while Trader specified a monthly subscription and included allowance. The historical product range also included Startup, Advanced and Enterprise tiers. Data outside Explorer's access required a paid package even when an integration used few calls.

More calls did not expand the measured activity

The API's dapp statistics described tracked application activity, including Unique Active Wallets, transaction count and volume. Repeated queries retained the measurement scope of their underlying data. More frequent retrieval did not automatically extend tracked contract coverage or reveal every app session outside the blockchain. A refresh budget controlled opportunities to retrieve observations, while the underlying measurement defined the questions those observations could answer.

Contract coverage could change over time, so period comparisons needed matching measurement context. An integration could retain query parameters beside a response to preserve its scope. Those parameters identified the requested application, blockchain and reporting window. They did not, alone, establish complete coverage of every contract belonging to the application.

Open full-size image

What did the closure change for API users?

The original team announced a wind-down in November 2025, including plans to stop blockchain and dapp tracking. Unused call capacity could not establish continued data delivery after that change. A May 2026 DAO update announced new ownership for the Dappradar brand and platform assets. The old pricing described the original team's service without establishing the terms of any later offering.

A saved response could remain a record of earlier activity with its original time window and coverage. A live integration needed an available endpoint and observations appropriate to its intended period. Any renewed API offer would have its own access terms and call allocation. The 2023 Trader figures would apply only if a later offer explicitly retained them.