Billing
Pricing for API is charged along two dimensions. All details can be found at dune.com/pricing
If your execution fails, then no credits are charged. If you execute a query but never pull the results, you are only charged for the execution.
Dimension | Charge |
---|---|
Executions | 10 credits per medium query engine executions 20 credits per large query engine executions |
Datapoints (Results) | 1 credit per 1,000 datapoints on Free 1 credit per 5,000 datapoints on Plus 1 credit per 25,000 datapoints on Premium |
Storage | 1MB on Free 15GB on Plus 50GB on Premium |
Queries Endpoint | Available on Plus and Premium |
Webhooks (Alerts) | 1 on Free 5 on Plus 50 on Premium |
A datapoint applies to query results after the query is run, and can in most cases be thought of rows * columns
with an additional limit of 100 avg bytes per cell in a set of results. This can be expressed as:
Byte-Based Calculation Details
When calculating datapoints based on total bytes, cells that exceed 100 bytes will “spill over” into additional cells. Here’s how this works:
Example Table:
Spillover Calculation: If one cell contains 175 bytes, that cell effectively counts as 2 cells in the datapoint calculation:
- First 100 bytes = 1 cell
- Remaining 75 bytes = 1 additional cell
Example breakdown:
- 8 cells of 100 bytes each = 8 cells
- 1 cell of 175 bytes = 2 cells (100 + 75)
- Total: 10 cells
API Usage Billing
Any API usage billing will be based on what account the API key is associated with. If you use your team API key to call a public query belonging to yourself, the billing will be associated to the team (and vice versa).