Work directly with Glassnode engineers to solve integration and data challenges.
Request a quote from Glassnode Expert Services
Ctrlk
WebsiteStudioInsightsTwitter
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Data Credits

Retrieving data from the platform consumes Data Credits. Regardless of the export method used, such as an API call, JSON/CSV file download, the Excel add-in, or other integrations, credits are deducted based on the specific assets included in your request.

Note: General usage and viewing data within the Studio interface does not consume Data Credits. Credits are only deducted when you actively download or export data from the Studio.

Credit Consumption Rates

  • BTC: 1 credit per request

  • All other assets: 2 credits per request

Example: If you use the Excel add-in to pull the ETH price, it consumes 2 credits. Pulling the BTC price through an API call consumes only 1 credit.

Track Current Month Credit Usage

You can monitor your data credit usage in two ways:

  • Studio dashboard: Visit studio.glassnode.com/settings/api to see your current month's credit usage and a history of recent API calls with their individual credit consumption.

  • API endpoint: https://api.glassnode.com/v1/user/api_usage — returns a JSON object that includes a creditsUsed field (for example, { ..., "creditsUsed": 6, ... }).

Bulk Endpoints and Data Credits

Bulk endpoints allow to retrieve data for multiple parameter combinations in a single request. While this is efficient in terms of reducing the number of API calls, it's essential to understand how data credits are consumed:

  • Credit Calculation: Each request to a bulk endpoint consumes credits based on the number of assets requested (1 credit for BTC, 2 credits for any other asset). Other parameters like exchanges or networks do not affect credit consumption. For example:

    • Calling the /market/mvrv/bulk endpoint with BTC and 4 other assets will consume 1 + (4 × 2) = 9 data credits, regardless of how many exchanges are included.

  • Parameter Whitelists: When the asset parameter is not specified, the bulk endpoint returns data for all available assets, which can lead to significant credit consumption. To manage and predict credit usage effectively, it's advisable to always specify the assets (a) parameter explicitly.

For more detailed information on bulk endpoints and their usage, refer to the Bulk Metrics documentation.

PreviousAPI SetupNextRate Limits

Last updated