All posts

DuneIsNowAgent-Native:CLIandSkillsarenowlive

Dune is now fully agent-native. This week we shipped the Dune CLI and Skills — giving AI agents direct terminal access to onchain data across 130+ chains. Here's what's new, why it matters, and how to get started.

NewsMarch 13, 20262 min read
Dune CLI
agent-native
MCP
Skills.md
Onchain data
@Alsie L.
Alsie L.Content Marketing Manager at Dune
Dune Is Now Agent-Native: CLI and Skills are now live

AI agents are becoming the primary interface for onchain data. They don't click through dashboards. They query, execute, and return results. Programmatically, autonomously, and fast.

Last week we shipped Dune MCP. This week we shipped three more things that make Dune fully agent-native.

Dune CLI & Skills

The Dune CLI (github.com/duneanalytics/cli) gives AI agents direct access to Dune from the terminal. It's built on a Go SDK and covers the full workflow: discover datasets, write and execute DuneSQL, manage queries, search docs, and track usage. Every command outputs JSON for machine consumption.

It also ships with a Skills.md file. This follows the same Agent Skills standard adopted by Anthropic, Microsoft, and others. Your agent reads the file and immediately knows what Dune can do, what commands to run, and how to handle errors. No integration work. No custom tooling.

Why does this matter? Terminal-based AI tools like Claude Code, OpenCode, and Cursor, along with autonomous agents like OpenClaw, NanoClaw, and IronClaw, operate in environments where every token counts. CLI + Skills is more context-efficient than MCP for these workflows. It's the same pattern GitHub CLI pioneered, now for onchain data across 130+ chains.

Under the hood, both the CLI and MCP are powered by two new API endpoints that we're also making public this week. /v1/datasets/search lets agents search Dune's entire catalog (decoded contracts, spells, community tables) using natural language with filters for blockchain, category, and schema. /v1/datasets/search-by-contract takes any contract address and returns every decoded event and function table associated with it.

What this means in practice: your agent doesn't need to know what tables exist. It discovers them, writes the query, executes it, and returns results. No human in the loop.

CLI & Skills setup guide

When to use MCP or CLI?

Last week we shipped Dune MCP. This week, CLI & Skills. Both access the same data across 130+ chains. Choose based on how your agent works:

MCP → Best for GUI-based AI apps like Claude.ai, ChatGPT, and Gemini. Persistent connection, structured tool calls.

CLI + Skills → Best for terminal agents and autonomous workflows. Stateless, command-based, lower token overhead.

Get Started with Dune CLI

Install the CLI, authenticate, and start querying:

dune auth --api-key <your-key>
dune query run-sql "SELECT * FROM dex.trades LIMIT 10" -o json

CLI & Skills guide · MCP guide · API docs

Related

VIEW ALL

Make real impact with onchain data

JOIN US

Looking to use Dune for your company?