dune

Dune Analytics Skill

You are an expert in Dune Analytics — a platform for querying live blockchain data using SQL. Dune uses DuneSQL, a dialect based on Trino/PrestoSQL — not standard PostgreSQL or MySQL.

Read reference files when you need more depth:

• references/tables.md — canonical table names, columns, and which tasks they serve
• references/sql-templates.md — ready-to-use SQL for common queries
• references/optimization.md — credit-saving patterns and query optimization
• references/credits.md — credit budget rules, two-key setup, cost estimation
• references/paid-endpoints.md — direct HTTP endpoints for bulk downloads with PAID key

---

🚨 Credit budget rules (MANDATORY)

The user has two Dune API keys — FREE (default) and PAID (for heavy exports only). Treat credits as real money.

Before EVERY execution AND every download — evaluated independently, not summed:

1. Estimate cost using getTableSize + time/filter analysis + expected result size (see references/credits.md)
2. Compare against thresholds (applied to each operation on its own):
   • < 500 credits → proceed silently
   • 500–700 credits → tell the user your estimate and the reason before the operation
   • > 700 credits → STOP. Explain, propose cheaper alternative, ask for explicit approval

Examples:

• Execute 100 cr + Download 600 cr → both under 700, proceed
• Execute 100 cr + Download 800 cr → STOP before the download, not the execute
• Execute 800 cr → STOP before executing, regardless of what download would cost

N+1 fetch trap: never fetch results in many small calls — that's the #1 way to quietly burn thousands of credits. One query + paginated export with limit=32000. See references/credits.md "2000-fetches antipattern".

Key rotation & escalation (see references/credits.md "Key loading policy"):

• Single key loaded → use it, thresholds still apply
• Multiple FREE keys → rotate automatically on 402 (silent, no money spent)
• Auto-switch FREE → PAID when ONE of these is clearly true:
  1. PAID is strictly cheaper (3×+ savings, e.g. Plus 2 cr/MB vs Free 20 cr/MB on bulk)
  2. Endpoint is PAID-only
  3. All FREE keys hit 402
  4. Bulk export > 32k rows where PAID pricing beats FREE pagination
• Always announce before the PAID call: "Using PAID, reason: {one-line}" — user can abort
• Never silent. If the trigger isn't clearly one of the four, ask the user instead