# RagRadar On-Chain Heatmap

> RagRadar On-Chain Heatmap is a paid API for AI agents from ragdar.vercel.app, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Returns on-chain activity heatmap data for a specified blockchain network (Base, Arbitrum, or Solana)

## Facts

- Endpoint: GET https://ragdar.vercel.app/api/heatmap/%7Bchain%7D
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ragradar-on-chain-heatmap-31cf23a8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0nQpJEXXPnzARNN1RqCJy

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 ragradar-on-chain-heatmap-31cf23a8
```

Example prompt: Pull the on-chain activity heatmap for Base from RagRadar so I can see which time periods have the highest transaction density.

## When to prefer this

Choose this endpoint when you need a time-based or spatial distribution view of on-chain activity for Base, Arbitrum, or Solana — particularly useful for identifying peak activity windows, congestion periods, or behavioral patterns. Prefer over raw transaction APIs when you need pre-aggregated heatmap-style analytics rather than individual transaction data.

## Known failure modes

- Unsupported chain name returns error or empty response
- Invalid chain path parameter returns 404 or malformed response
- Micropayment via x402 fails due to insufficient USDC balance
- Upstream blockchain data provider unavailable causing 503
- Rate limiting if too many requests sent in rapid succession

## How this service works

On-chain intelligence for AI agents. 70+ endpoints across Base, Arbitrum, Solana. x402 micropayments.

## Output

A JSON object containing heatmap data representing on-chain activity distribution across the specified blockchain, including transaction counts or activity intensity broken down by time periods or address clusters. Status field confirms successful retrieval.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "ok"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ragradar-on-chain-heatmap-31cf23a8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ragdar.vercel.app](https://www.zero.xyz/host/ragdar.vercel.app/llms.txt)