On-Chain Analytics and Token Signals
Wallet clustering, top-holder snapshots, fresh-address detection, balance time-series, and a curated signal feed — the same on-chain analytics surface that powers our own consumer analytics product.
Who this is for
| Persona | Typical inbound |
|---|---|
| Trading interface | ”We need wallet clustering and top-holder data on our token-detail pages.” |
| Research platform | ”We want insider, sniper, and developer labels for the holders of a given token.” |
| Alpha-signal tool | ”Real-time signal feed plus market-scan counts to surface unusual activity.” |
| Quant or on-chain analyst | ”Per-wallet balance time-series across a token universe for backtests and dashboards.” |
Not a fit if you need primary coverage of a chain we have not indexed (Solana is the most complete coverage today, with selective EVM coverage), custom data products beyond the published capabilities (analytics-as-a-service is a separate scoping conversation), or a fully anonymous public API tier with no commercial agreement.
What you can ship today
| Capability | What it includes |
|---|---|
| Wallet clustering and connections | Cluster analysis for a single wallet (insider-cluster suspicion scoring), and a relationship graph between multiple wallets. |
| Top-holder snapshots | Current top-holder snapshot for a token, plus historical top-holder evolution over time. |
| Fresh-address and accumulation detection | First-time wallets accumulating a given token, and aggregate balance-increase detection across the holder set. |
| Wallet and token labels | Sniper, developer, and insider tags by wallet, including tags scoped to a wallet’s behaviour around a specific token. |
| Balance time-series | Per-wallet token balance time-series, plus a multi-wallet historical info endpoint covering current and historical token, native, and Solana balances. |
| Curated signal feed | A signal-dashboard endpoint with rolling rate limits, plus an aggregate market-scan counter. |
| DCA and limit-order activity | DCA and limit-order activity for a given token. |
| Token search and overview | Token search by keyword, token detail (price, supply, holder count, social links), and a wallet-assets endpoint that returns all token holdings for a single wallet. |
How it works
The analytics surface is a set of REST endpoints over a shared backend that ingests on-chain data, classifies wallets, and exposes derived signals. Most endpoints accept a chain identifier and an address or token, and return a structured response shaped for analytics dashboards.
1. Your client (browser, server-side service, or batch worker) calls
the relevant analytics endpoint with the chain identifier and the
subject address or token.
2. The backend looks up the precomputed cluster, label, holder, or
balance state for that subject and returns the structured response.
3. For real-time use cases, your frontend can subscribe to the signal
feed and refresh on a fixed interval; for historical analysis, the
balance-history and historical-top-holders endpoints return the
time-series in a single call.Authentication and rate-limit policies are confirmed per partnership during scoping. Volume tiers, refresh cadence, and the exact set of endpoints exposed are tailored to the integration shape — for example, a research platform doing batch backtests has different needs from a trading interface refreshing every few seconds.
Compliance posture
Analytics endpoints expose data derived from public on-chain activity. The platform inherits our regulated posture: Taiwan VASP registration, ISO 27001 and ISO 27701 certifications, SOC 2 Type II examined controls, Cure53 audit. Where analytics are paired with subscription billing or with a wallet product that holds customer balances, the same compliance posture extends to those surfaces. See Compliance and Certifications for the full picture.
Chains supported today
| Chain | Coverage |
|---|---|
| Solana | Most complete — clustering, labels, top-holder, fresh-address, signal feed, DCA and limit-order activity |
| EVM (Ethereum, Base, Arbitrum, Optimism, Polygon and others) | Selective coverage; per-endpoint coverage confirmed during scoping |
| Tron | Limited coverage |
Real-time price feeds are integrated from third-party sources where appropriate; the integration shape is confirmed per partnership.
Typical integration timeline
| Phase | Bucket |
|---|---|
| Read-only integration of a small set of analytics endpoints into an existing product | Under one month |
| Full analytics surface with custom auth and rate-limit policy | One to three months |
| Bespoke analytics product or new derived signals | Three to six months |
Current scope
- The analytics surface is in production today and powers our own consumer analytics product at scale.
- Solana is the primary chain. EVM and Tron coverage are added per partnership scope.
- Schema versioning and a public, partner-facing contract are confirmed per partnership; not every endpoint has a fully versioned schema today.
- A self-service developer portal for these endpoints is in design. Partners today integrate against documentation provided during scoping.
Talk to us
If you want to integrate on-chain analytics into a trading, research, or signal product, the fastest way to scope is a 45-minute discovery call. Reach our partnerships team via the address on www.kryptogo.tw .
Where to go next
- Subscriptions and referrals — the monetisation layer that analytics products are typically paired with.
- Transaction webhooks — push notification on payment status, useful when analytics is sold via subscription.
- Architecture Overview — how the analytics surface fits into the wider platform.
- Compliance and Certifications — the regulated posture inherited by every endpoint.