Dune MPP: Pay-per-Request API Access for AI Agents
Let AI agents query Dune’s API and pay per request with the Machine Payment Protocol (MPP), with no Dune account or API key.
MPP (Machine Payment Protocol) is an open standard for machine-to-machine HTTP micropayments built on the HTTP 402 challenge-response flow. Dune’s MPP integration lets agents pay per-request through a payment channel - no API keys, no user account, and no credit card required.
How It Works
Your client sends a request to a Dune API endpoint.
Dune responds with HTTP 402 and a WWW-Authenticate: Payment challenge describing the cost.
The mppx client library automatically opens a Tempo payment channel on the first 402, depositing funds into an on-chain escrow.
Subsequent requests are authenticated with signed channel vouchers deducted from the deposit.
When you are done, you close the session and any unspent deposit is returned to your wallet.
Available Endpoints
Endpoint
Description
POST /v1/sql/execute
Execute a SQL query
GET /v1/execution/:execution_id/results
Fetch JSON results for an execution
GET /v1/execution/:execution_id/csv
Download CSV results for an execution
Option 1: Agentic Integration
The fastest way to get started. Ask your AI coding agent to set up Tempo and run a query on Dune - no manual code required. This works with any agent that supports skills or tool use, including Claude Code, Cursor, OpenAI Codex, OpenCode, and others.
Getting Started
Simply give your agent the following prompt:
Read https://tempo.xyz/SKILL.md and set up tempo.After that, use MPP to run the following query on Dune:SELECT * FROM ethereum.transactions LIMIT 10
Your agent will:
Read the Tempo skill instructions and configure itself
Open a payment channel funded from your crypto wallet
Execute the query against Dune’s API via MPP
Return the results directly in your conversation
No Dune account, no API key, and no credit card needed - you pay per-request with crypto.
Closing Your Session
Always ask your agent to close the session when you are done. Closing the session settles the payment channel on-chain and refunds any reserved funds back to your wallet - you are only charged for what you actually used.
When you are finished querying, tell your agent:
Close the tempo session.
This ensures your unspent deposit is returned promptly. If you forget to close, funds remain in escrow until the channel expires.
Option 2: Manual Integration
For full control, you can integrate MPP directly into your application using the mppx client library and viem for EVM account management. The mppx session API wraps the standard fetch and handles the 402 negotiation, channel management, spend tracking, and payment signing transparently.
Step 1 - Install dependencies
npm install mppx viem
Step 2 - Set up your wallet and initialize a session
Create an account from a private key and initialize a Tempo session. The maxDeposit parameter sets the maximum amount (in USD) to escrow when a payment channel is opened.
import { tempo } from "mppx/client";import { privateKeyToAccount } from "viem/accounts";const account = privateKeyToAccount( process.env.PRIVATE_KEY as `0x${string}`);const session = tempo.session({ account, maxDeposit: "10" });
Step 3 - Execute a query
Use session.fetch exactly like the standard Fetch API. On the first call, the session intercepts the 402 response, opens a Tempo payment channel, and retries the request with a valid payment credential - all transparently.
Dune executes queries asynchronously. Poll the status endpoint until the state is QUERY_STATE_COMPLETED.
let state = "";do { const r = await session.fetch( `https://api.dune.com/api/v1/execution/${execution_id}/status` ); state = ((await r.json()) as { state: string }).state; if (state === "QUERY_STATE_FAILED") throw new Error("Query failed"); if (state !== "QUERY_STATE_COMPLETED") await new Promise((r) => setTimeout(r, 2_000));} while (state !== "QUERY_STATE_COMPLETED");
Step 5 - Fetch results
Once the query completes, retrieve the results. Each request is automatically paid through the open channel.