Crypto Analytics Dashboards
Analyst-verified crypto research for individual investors — without the institutional price tag.
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Live 402 challenge
Captured by the enrichment pass, not read just now. Prices can change — always read the 402 the endpoint answers with.
{
"error": "Payment required. Pay the PAYMENT-REQUIRED header with an x402 client and retry.",
"price": "$0.25",
"catalog": "https://www.blockchainiq.co/api/x402/v1"
}Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
Pay 0.25 USDC on Base to 0x617d…B7C9e. The signed payment is good for 5 minutes.
- Paid to
- 0x617d…B7C9e
- USD Coin contract
- 0x8335…02913
- Payment window
- 5 minutes
- As published
- 250000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x617dA9383fbA67e86137BC4924b8b7E400fB7C9e",
"amount": "250000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"type": "http",
"method": "GET",
"pathParams": {
"slug": "bitcoin-network"
},
"queryParams": {}
},
"output": {
"type": "json",
"example": {
"data": {
"panels": [
{
"data": {
"unit": "count",
"series": [
{
"name": "Daily active addresses",
"points": [
{
"t": "2026-10-10T00:00:00.000Z",
"v": 630842.57
}
]
}
]
},
"kind": "time_series",
"title": "Active addresses",
"subtitle": "Distinct addresses appearing in any input or output, daily average for each week",
"panelSlug": "active-addresses",
"sourceView": "btc_aws_daily",
"refreshedAt": "2026-10-11T10:18:41.106Z",
"analyst_read": "Distinct addresses appearing in any input or output, averaged per day for each week. It counts addresses, not people: wallets rotate addresses, so one holder can appear as many, while exchanges and services put many users behind a few. The shape to read is a drift lower from the late-2024 peak into a narrow band for most of 2026, where one-week spikes fade within a week or two, so judge the slope of the band rather than any single week."
}
],
"dashboard": {
"live": true,
"slug": "bitcoin-network",
"tier": "analyst",
"blurb": "Activity on the Bitcoin blockchain itself — the Bitcoin price, transactions, active addresses, blocks, how full they are, fees paid to miners, coins moved, and mining difficulty. Drawn from the chain data, about a day behind.",
"title": "Bitcoin Network"
}
},
"terms": "https://www.blockchainiq.co/terms",
"source": "Blockchain IQ",
"disclaimer": "Market data and analysis, not investment advice.",
"panelCount": 1
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method"
],
"properties": {
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"GET"
],
"type": "string"
},
"pathParams": {
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"enum": [
"aptos-network",
"arbitrum-network",
"avalanche-network",
"base-network",
"bitcoin-network",
"bnb-network",
"ethereum-network",
"near-network",
"polygon-network",
"provenance-network",
"solana-network",
"stellar-network",
"tezos-network",
"ton-network",
"xrp-ledger"
],
"type": "string",
"description": "Dashboard slug, e.g. bitcoin-network"
}
}
},
"queryParams": {
"type": "object",
"properties": {}
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object"
}
}
}
}
},
"routeTemplate": "/api/x402/v1/dashboards/:slug"
}
}Provenance
- Seen in the source catalog
- 2026-10-26 09:30Z
- Last indexed by Roundhouse
- 2026-10-26 17:20Z
- Last enriched (probe, favicon, geo)
- 2026-09-29 13:15Z
- x402 version
- 2
- Max timeout
- 300s
- Liveness probe
- HTTP 402
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 32 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service Crypto Analytics Dashboards and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=Crypto%20Analytics%20Dashboards' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://www.blockchainiq.co/api/x402/v1/dashboards/:slug, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.