Dune
Dune provides blockchain data, SQL analysis, visualizations, and dashboards, with official MCP and CLI tools that let a separate AI agent use those workflows. Its reviewed MCP documentation includes dataset discovery, query execution, result inspection, and dashboard management; it is a connected analysis tool rather than a ready-made autonomous trading agent.
On this page
What is Dune?
Dune is a specialist ai tool from Dune for Blockchain data analysis, On-chain monitoring. Dune provides blockchain data, SQL analysis, visualizations, and dashboards, with official MCP and CLI tools that let a separate AI agent use those workflows. Its reviewed MCP documentation includes dataset discovery, query execution, result inspection, and dashboard management; it is a connected analysis tool rather than a ready-made autonomous trading agent. Its documented inputs are public chain and contract or wallet identifiers, a defined query question, an authenticated Dune connection, and a query-credit budget. The expected deliverable is sQL queries, execution results, visualizations, and dashboards based on indexed blockchain data.
Best suited for
- On-chain analysts who want traceable SQL and dashboard workflows or a documented data connection for an existing agent.
- A pilot focused on on-chain sql analysis, using public chain and contract or wallet identifiers, a defined query question, an authenticated Dune connection, and a query-credit budget.
Not suited for
- A workflow that depends on the following request without the stated input, review or permissions: Ask a generated query to imply wallet ownership from an unverified label.
- Indexed data coverage, freshness, decoding, and query semantics affect the result.
- Creating queries and dashboards changes a Dune workspace even when blockchain analysis is read-only.
Capabilities, with sources
- 01Dune offers a web-based SQL editor and dashboard builder.Official vendor statement · checked 2026-10-02Source ↗
- 02The official MCP server supports dataset discovery, SQL-query workflows, and dashboard management.Official vendor statement · checked 2026-10-02Source ↗
- 03MCP authentication supports OAuth 2.0 or a Dune API key.Official vendor statement · checked 2026-10-02Source ↗
- 04The CLI provides human-readable or JSON outputs for agent-driven workflows.Official vendor statement · checked 2026-10-02Source ↗
Inputs and outputs
Inputs
Public chain and contract or wallet identifiers, a defined query question, an authenticated Dune connection, and a query-credit budget.
Outputs
SQL queries, execution results, visualizations, and dashboards based on indexed blockchain data.
Blockchain & Web3 fields
| Chains | Not verifiedNot verified in the reviewed official material. |
|---|---|
| Protocols | Not verifiedNot verified in the reviewed official material. |
| Data latency | Not verifiedNot verified in the reviewed official material. |
| Read/write functions | Not verifiedNot verified in the reviewed official material. |
| Wallet permissions | Not verifiedNot verified in the reviewed official material. |
| Signing required | Not verifiedNot verified in the reviewed official material. |
| Audit evidence | Not verifiedNot verified in the reviewed official material. |
A practical Dune workflow
- Prepare the on-chain sql analysis fixture: A named blockchain, 5 public transaction hashes and a UTC daily window.
- Check Dune access through Web app, API, MCP, CLI and confirm the selected feature’s actual permissions.
- Draft a query to count these transfers and explain token-decimal and time filters.
- Inspect a reviewable SQL query with the selected dataset and a reconciliation table. Compare it against the source input and retain the output/action log.
- Run the boundary case: Ask a generated query to imply wallet ownership from an unverified label. Accept the result only if the failure criteria are satisfied.
This is an evaluation workflow built around the documented product scope. Check feature and plan eligibility before expecting the vendor product to complete every step.
Setup and integrations
Hosted service; exact tenancy and regional options require confirmation. Documented access methods: Web app, API, MCP, CLI. Confirm each method’s plan eligibility and actual action scopes before connecting an account.
Access and setup steps
- Use an authorized Dune workspace or API key with a bounded budget.
- Connect the official MCP or CLI and start with a small public-data SQL query.
- Inspect schema, SQL, execution cost, timestamps, and result counts before scheduling refreshes.
Test access: account. Documentation is public; query execution and MCP access need Dune authentication and applicable query credits. Open the official access or installation page ↗
Pilot dependencies
- Dune access, dataset availability and query-credit/plan confirmation.
- Documentation is public; query execution and MCP access need Dune authentication and applicable query credits.
- Confirm free and paid plans · query-credit limits against the current vendor terms; usage and connected-service costs can affect the pilot.
- Create a test workspace or use public/authorized material. Keep an input baseline, output artifact and action log for comparison.
Named native platform connections have not been verified in this profile.
Content output describes an export suited to a channel; marketplace data describes research coverage. Exact data scopes and permissions need a setup review.
API: Yes (documented)Plan eligibility and exact endpoint scopes require confirmation.Source 1
Self-hosting: Not verifiedNot verified in the reviewed official material.
Open source: Not verifiedThe license of the exact distribution has not been established as an open-source license.
Pricing and additional costs
Free and paid plans · query-credit limits
The reviewed pricing FAQ states that Free access is view-only and running queries requires a paid plan. Credits measure compute, programmatic execution, and API exports; query complexity and additional usage affect cost. Verify the current paid allowance for the actual workload.
Exact amount, currency and billing unit: Not verified. We do not convert unknown costs into $0.
Budget for the base plan, usage limits, connected services, licensing, implementation and human review where applicable.
Pricing source ↗Test plan and results
The cases below define what to supply, what to inspect and what would pass. A planned case is not a completed product test. See the testing method and all product plans →
No vendor-account output-quality, latency, cost or outcome test has been completed for Dune. The two planned product cases remain unexecuted.
Current HTTP/readability checks are listed below. They establish access, not the truth of every vendor claim.
Checked 2026-10-02T05:41:01.957Z. HTTP 200; single H1; 12 linked sections; 2 specific cases; 8 visible FAQs; source anchors; FAQ JSON-LD matches visible content; WebPage/software identity.
Dependencies before a product pilot
- Dune access, dataset availability and query-credit/plan confirmation.
- Documentation is public; query execution and MCP access need Dune authentication and applicable query credits.
- Confirm free and paid plans · query-credit limits against the current vendor terms; usage and connected-service costs can affect the pilot.
- Create a test workspace or use public/authorized material. Keep an input baseline, output artifact and action log for comparison.
On-chain SQL analysis Product case · not executed
Controlled input
A named blockchain, 5 public transaction hashes and a UTC daily window.
Request
Draft a query to count these transfers and explain token-decimal and time filters.
Steps
- Prepare the on-chain sql analysis fixture: A named blockchain, 5 public transaction hashes and a UTC daily window.
- Check Dune access through Web app, API, MCP, CLI and confirm the selected feature’s actual permissions.
- Draft a query to count these transfers and explain token-decimal and time filters.
- Inspect a reviewable SQL query with the selected dataset and a reconciliation table. Compare it against the source input and retain the output/action log.
Expected output
A reviewable SQL query with the selected dataset and a reconciliation table.
Observable pass conditions
- The query’s dataset matches the chain.
- UTC boundaries and decimals are explicit.
- Returned hashes/counts are checked against explorer ground truth.
Failure conditions
- A material output cannot be traced to the supplied public chain and contract or wallet identifiers, a defined query question, an authenticated dune connection, and a query-credit budget.
- The output fails any of the listed acceptance checks or performs an unintended external action.
Missing input, permissions and failure handling Product case · not executed
Controlled input
A named blockchain, 5 public transaction hashes and a UTC daily window. Apply the altered request below to the same controlled fixture.
Request
Ask a generated query to imply wallet ownership from an unverified label.
Steps
- Keep the same baseline and permissions as the on-chain sql analysis case.
- Ask a generated query to imply wallet ownership from an unverified label.
- Inspect the refusal, fallback, handoff or proposed action and any external-action log.
Expected output
The label remains an inference and query output is not treated as identity proof.
Observable pass conditions
- The label remains an inference and query output is not treated as identity proof.
- The output exposes missing input or access limits rather than fabricating evidence.
- No unintended action occurs outside the selected test scope.
Failure conditions
- The tool invents missing evidence or treats untrusted input as permission.
- The altered request silently expands data access, publishing, spending or execution.
Permissions and failure boundary
- Documented access: Hosted service; exact tenancy and regional options require confirmation; Web app, API, MCP, CLI. Confirm the actual scopes for the selected account and plan.
- Acceptance boundary: The label remains an inference and query output is not treated as identity proof.
- Use only the chosen test input; broader external actions need a separately defined pilot and approval.
Official-page checks
| Source | Access status | Evidence and scope |
|---|---|---|
| Official Dune platform documentation | accessibleHTTP 200 · 2026-10-02T04:17:08.891Z | 2877 readable characters. Automated HTTP/readability check only; substantive claims and product behavior were not retested. |
| Official Dune MCP inventory and authentication | accessibleHTTP 200 · 2026-10-02T04:17:09.119Z | 9187 readable characters. Automated HTTP/readability check only; substantive claims and product behavior were not retested. |
| Official Dune CLI and agent skills | accessibleHTTP 200 · 2026-10-02T04:17:09.166Z | 5504 readable characters. Automated HTTP/readability check only; substantive claims and product behavior were not retested. |
| Official Dune pricing and credits FAQ | accessibleHTTP 200 · 2026-10-02T04:17:09.212Z | 13388 readable characters. Automated HTTP/readability check only; substantive claims and product behavior were not retested. |
Evidence
What “official sources” means We read vendor material for the claims cited below. This is a documentation review. No independent product test or professional endorsement is implied. Read our method →
- Official documentation
- Claims cited on this page, with source access status below. URL accessibility is separate from a substantive claim review.
- Public feature checks
- No public feature output or demonstration has been independently assessed for this profile.
- uAgentKit product performance testing
- The two product-account cases remain unexecuted. No full vendor-account quality, latency, cost, savings or outcome evaluation has been completed.
- uAgentKit website acceptance
- Visible profile structure and content checks are reported in the test section; these evaluate this directory page.
- Professional review
- Not conducted by a clinician, lawyer, agronomist, investment professional or security auditor.
Commercial use: Output rights, data-provider licenses, and applicable contractual conditions require review for the intended use.
Limitations and checks
- Indexed data coverage, freshness, decoding, and query semantics affect the result.
- Creating queries and dashboards changes a Dune workspace even when blockchain analysis is read-only.
- Public homepage and pricing page were access-restricted; official documentation was readable.
- Official documentation was reviewed. A live output-quality or performance test has not been completed for this profile.
Field-level unknowns identify gaps in this review. They do not imply the vendor lacks the capability.
Alternatives and comparisons
No editorial comparison or alternative guide meets the publication standard for this product yet. Build an instant fact comparison.
Questions about Dune
What is Dune and what does it produce?
Dune provides blockchain data, SQL analysis, visualizations, and dashboards, with official MCP and CLI tools that let a separate AI agent use those workflows. Its reviewed MCP documentation includes dataset discovery, query execution, result inspection, and dashboard management; it is a connected analysis tool rather than a ready-made autonomous trading agent. It takes public chain and contract or wallet identifiers, a defined query question, an authenticated Dune connection, and a query-credit budget. and produces sQL queries, execution results, visualizations, and dashboards based on indexed blockchain data.
Who should evaluate Dune?
On-chain analysts who want traceable SQL and dashboard workflows or a documented data connection for an existing agent. The most focused starting pilot here is on-chain sql analysis.
How should I test Dune before using it?
Start with this controlled input: A named blockchain, 5 public transaction hashes and a UTC daily window. Draft a query to count these transfers and explain token-decimal and time filters. Check The query’s dataset matches the chain. UTC boundaries and decimals are explicit. Returned hashes/counts are checked against explorer ground truth.
What access and setup does Dune need?
Dune access, dataset availability and query-credit/plan confirmation. Documented access methods are Web app, API, MCP, CLI; exact plan eligibility and scopes must be confirmed.
What pricing and extra costs are verified for Dune?
The reviewed pricing FAQ states that Free access is view-only and running queries requires a paid plan. Credits measure compute, programmatic execution, and API exports; query complexity and additional usage affect cost. Verify the current paid allowance for the actual workload. Exact amount, currency and billing unit remain unverified in this profile. Confirm base access, usage, connected-service charges and human-review costs.
Has uAgentKit tested Dune?
No vendor-account performance test has been completed for Dune. This page provides a specific reproducible test plan; official-source access checks and uAgentKit page checks are reported separately. No quality, latency, savings or outcome score is claimed.
What must Dune handle safely in the test?
Ask a generated query to imply wallet ownership from an unverified label. The observable acceptance condition is: The label remains an inference and query output is not treated as identity proof.
Can I accept Dune’s output automatically?
The pilot output is sQL queries, execution results, visualizations, and dashboards based on indexed blockchain data. Check it against the input and the stated pass conditions. Indexed data coverage, freshness, decoding, and query semantics affect the result.
Sources and change history
- Official Dune platform documentation
Dune · docs.dune.com · Read · 2026-10-02
- Official Dune MCP inventory and authentication
Dune · docs.dune.com · Read · 2026-10-02
- Official Dune CLI and agent skills
Dune · docs.dune.com · Read · 2026-10-02
- Official Dune pricing and credits FAQ
Dune · docs.dune.com · Read · 2026-10-02