Skip to main content
Pricing for API is charged along several dimensions. All details can be found at dune.com/pricing.
Failed executions are not always charged. Queries that run until Dune’s execution timeout, executions stopped by a user-defined resource/cost cap, and user-cancelled executions after compute has been used may consume credits for resources already used.Dune does not charge for SQL syntax/semantic errors, internal query-engine failures, or query-engine capacity-limit failures such as memory or stage limits. For a specific execution, check execution_cost_credits on the status endpoint.

Executions

Credits are consumed based on actual compute resources used for each query execution. The performance tier you select affects credit consumption. If you execute a query but never pull the results, you are only charged for the execution.

Data Export

Credits are consumed when exporting query results via API or CSV.
PlanCredits per MB Exported
Free20
Analyst10
Plus2
EnterpriseCustom

Data Writes

Credits are consumed when writing data (table creation, data insertion, uploads).
PlanCredits per GB Written
Free3
Analyst3
Plus3
EnterpriseCustom
Minimum charge is 1 credit per write operation.

Storage

Storage limits are per-plan caps, not charged per-credit.
PlanStorage Limit
Free100 MB
Analyst1 GB
Plus15 GB
EnterpriseUnlimited

Webhooks (Alerts)

PlanWebhooks
Free1
Analyst5
Plus5
EnterpriseCustom

Queries Endpoint

Available on Plus and Enterprise plans.

Data Transformations Billing

Data Transformations is an Enterprise-only feature with usage-based credit consumption.

Credit Consumption

Compute Credits

  • Same as Fluid Engine credits for query execution
  • Charged based on actual compute resources used
  • Depends on query complexity and execution time

Write Operations

  • Minimum 1 credit per write operation
  • Scales with data volume (GB written)
  • Applied to INSERT, MERGE, CREATE TABLE AS SELECT, etc.

Maintenance Operations

  • OPTIMIZE, VACUUM, and ANALYZE operations consume credits
  • Based on compute resources and data written during maintenance
  • Can be automated with dbt post-hooks
See dbt Connector documentation for more details.