Token Analytics
Token-level views over the same synced transfer data: search over the token registry, a screener and holder breakdowns, and buyer/seller flows in a chosen window, on Ethereum, BNB Chain, Base and HyperEVM.
Coverage: Screener, holders, transfer flows — Ethereum, BNB Chain, Base, HyperEVM · search — the token registry. Free — API key — delivered via MCP · API.
Data summary
| Category | On-Chain |
|---|---|
| Coverage | Screener, holders, transfer flows — Ethereum, BNB Chain, Base, HyperEVM · search — the token registry |
| Delivery | APIArchiveStreamMCP |
| Access | Free — API key |
| MCP tools | token_search token_screener token_holders token_transfers |
| REST | /v1/onchain/tokens/search/v1/onchain/tokens/screener/v1/onchain/tokens/{token_address}/holders/v1/onchain/tokens/{token_address}/transfers |
Getting started
curl -H "X-API-KEY: vk_..." \
"https://data.vike.io/v1/onchain/tokens/search?q=PEPE"
import requests
r = requests.get("https://data.vike.io/v1/onchain/tokens/screener",
params={"chain": "ethereum", "window": "24h", "limit": 10},
headers={"X-API-KEY": "vk_..."}, timeout=30)
r.raise_for_status()
for row in r.json(): # a JSON array of tokens
print(row)
{"jsonrpc": "2.0", "id": 1, "method": "tools/call",
"params": {"name": "token_transfers",
"arguments": {"token_address": "0x6982508145454ce325ddbe47a25d4ec3d2311933",
"period": "24h", "tab": "bought"}}}
Or in plain language — Ask Claude: who were the biggest PEPE buyers in the last 24 hours, and are any of them labeled entities?
Example applications
- Buyer/seller pressure analysis
If price action needs an on-chain explanation, token_transfers splits a window's flow into buys and sells with the wallets behind them — pressure with provenance.
- Holder-concentration risk checks
If you are sizing a position in a long-tail token, token_holders shows how much supply the top wallets control before concentration risk becomes your problem.
- New-token triage
If dozens of tokens cross your feed daily, token_search resolves them to contracts and chains, and the screener ranks them by actual on-chain activity, not by who is loudest.
Access
Free — get an API key at vike.io/account (up to 3 keys per account) and send it as X-API-KEY on every request.
Archive files are licensed CC BY 4.0 — use them for anything, credit Vike. API responses carry the same attribution ask. Keys, rate limits and errors: the API page.