# Prysm Dune Analytics Provider

> Prysm Dune Analytics Provider is a paid API for AI agents from prysm-kappa.vercel.app, paid per call via x402, $0.15/call, status unknown (last checked 2026-09-15).

Executes Dune Analytics query operations on-chain data via Prysm's x402-monetized API gateway, returning query results for blockchain analytics.

## Facts

- Endpoint: POST https://prysm-kappa.vercel.app/api/v1/providers/dune
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prysm-dune-analytics-provider-892699cf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0BXrVn9RBWPF1Of7IPVzm

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability prysm-dune-analytics-provider-892699cf -d '<json body>'
```

Example prompt: Pull the latest results from my Dune Analytics query for Uniswap daily trading volume — use the query_result operation and give me the full dataset.

## When to prefer this

Choose this endpoint when you need to programmatically fetch results from Dune Analytics queries in an agent context, especially when paying per-call via USDC over x402 on Base mainnet is acceptable. Prefer this over direct Dune API access when you need an x402-compatible, agent-ready gateway that handles authentication and monetization transparently.

## Known failure modes

- Invalid or non-allowlisted operation string returns an error
- Missing or malformed input parameters cause a bad request response
- Dune query ID not found or inaccessible returns empty or error data
- Payment failure via x402/USDC results in 402 Payment Required response
- Dune API rate limit exceeded upstream causes delayed or failed response
- Network timeout from Dune backend returns incomplete data

## How this service works

Prysm sells paid, agent-ready provider capabilities over x402 on Base mainnet using USDC.

## Output

Returns a JSON object containing the provider name ('dune'), the operation performed ('query_result'), and a data object with the full results of the executed Dune Analytics query, including on-chain metrics, rows, and any aggregated blockchain data from the query.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "description": "Provider-specific operation parameters.",
   "additionalProperties": true
  },
  "operation": {
   "type": "string",
   "description": "Allowlisted operation for the selected provider."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "provider": "dune",
  "operation": "query_result"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prysm-dune-analytics-provider-892699cf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from prysm-kappa.vercel.app](https://www.zero.xyz/host/prysm-kappa.vercel.app/llms.txt)