Whale Flow Data for Crypto Newsletters & Research Desks: Licensing & Formats

Crypto newsletters and research desks quote whale data constantly, often from screenshots of alert bots with no window, no scope and no distinction between an exchange withdrawal and a purchase. A publisher that wants figures readers can trust needs three things: a source with a documented method, a license that matches how the numbers are used, and wording that describes the flow accurately. This page covers all three for Deep Blue Alpha’s Ethereum whale data.

What you can use, and on which plan

Formats for editorial workflows

• Token pages (/tokens) — public 24h/7d/30d tracked-whale flow per token, citable by link.
• Daily reports (/reports) and the Whale Sentiment Index (/whale-index, embeddable badge).
• REST API — /api/v1/token/{symbol}/flow and /api/v1/top-tokens return chart-ready per-token windows with exchange and DEX fields split.
• MCP server (/mcp) — free, no key; lets a researcher ask Claude or ChatGPT for current whale flow.
• CSV — a free 7-day sample now; daily CSV + JSON files launching soon on Business.

Writing about exchange flow accurately

Most tracked whale flow is exchange transfers: in the Oct 16, 2026 sample, 78% of rows were exchange deposits or withdrawals and 22% DEX swaps. A withdrawal is not a purchase, and a deposit is not a sale. Wording that holds up:

Example: a weekly whale-flow item, written accurately

A typical newsletter item built from the public token pages or the API reads like this (placeholders in place of live figures):

Each element earns its place: the verb matches the label (pulled off exchanges, not bought), the window is stated (7 days), the scope is stated (tracked whale wallets), the swap share is mentioned, and the credit names the source. The item describes what happened; it does not say what the price will do or what readers should do.

What publishers ask before choosing a data source

• Is the method public? Deep Blue Alpha documents wallet selection, labels, pricing, history and known limits at /data/methodology.
• Can readers check a figure? Each move has a tx hash; token pages are public.
• Which chain? Ethereum mainnet only — say so if a piece covers other chains.
• How is a correction handled? Moves can arrive late or be revised; republish from the current page or API rather than an old screenshot.
• How is buying handled? Self-serve and by email; no calls or meetings.

Citing whale data step by step

1. Decide how the data appears. Occasional figures quoted in your own analysis, or charts and tables that show the data itself to readers.
2. Match the license. Occasional aggregated figures with the credit "Data: Deep Blue Alpha" are allowed under Business; paid newsletters, client reports, apps and terminals that display the data need Enterprise.
3. Use honest flow vocabulary. Write "pulled off exchanges" or "sent to exchanges" for transfers; reserve "bought" and "sold" for DEX swaps.
4. State the window and scope. Say which window (24h, 7d, 30d) and that figures describe tracked whale wallets, not all wallets.
5. Link the source. Link the token page or methodology so readers can check the figure.

Other sources publishers use

Whale Alert’s Alerts API ($29.95/mo) is labeled personal use only, with commercial use on its Enterprise plans ($699/mo; Enterprise Big from $2,000/mo). Glassnode and CryptoQuant publish metric charts widely cited in research; check each vendor’s terms for reproduction. Sources: developer.whale-alert.io; studio.glassnode.com/pricing, Glassnode API docs; CryptoQuant API credits, CryptoQuant docs; checked Oct 16, 2026.

Plans