Words, joined to wallets
Your users already follow these callers.
Put the receipts on your charts.
Every public call, matched against what the caller's wallet actually did on-chain — delivered as markers you drop straight onto a price chart.
Traders act on what other traders do — and that volume is yours.
Every endpoint needs a key — there is no open data path.
or read the docs first →$WIF · said × did · ● LIVE · GET /v1/tokens/WIF
Coverage
live counts · backfilled since Jan 2026What it moves
why teams put social proof next to price-
fee volume
More trades per session
A verdict beside the price gives a reason to act now.
-
retention
Longer sessions
Caller activity is what people come back to refresh.
-
re-activation
Alerts worth opening
Push only callers whose own money follows.
How attribution works
why the set is small on purpose19verified
of 122 tracked
-
Signed by the caller
They cryptographically verified the wallet against their social account. That is proof, and we take it.
-
Proven by behaviour
Their wallet repeatedly trades what they post, around the moment they post it. Enough independent matches and the link stands.
-
Everything else stays out
A wallet a tracker merely tagged is not evidence. Those callers keep flowing through the pipeline, unlisted, until attribution lands.
We would rather ship a set you can defend to your users than a large one you can't.
Integrate in minutes
one key, one request$ curl -H "x-api-key: rk_live_…" \\
https://kolapi.btcmu.info/v1/signals?min_score=80
{ "caller": "boru_insider", "score": 37, "verified": true,
"said": { "token": "WIF", "at": "2026-07-19T14:02:11Z" },
"did": { "verdict": "BOUGHT_AFTER", "entry_after_ms": 243000 } }
Five endpoints cover callers, signals, per-token markers and raw trades. See the full reference →
Pricing
in preview — keys issued by handBuild
Talk to us
- Volume that fits your app
- All endpoints, raw trades included
- Webhooks when a call lands