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.

Every endpoint needs a key — there is no open data path.

or read the docs first →

GET /v1/signals● live

{
  "caller": "boru_insider",
  "score": 37, "verified": true,
  "said": {
    "token": "WIF", "text": "aping $WIF",
    "at": "14:02:11Z"
  },
  "did": {
    "verdict": "BOUGHT_AFTER",
    "entry_after_ms": 243000
  }
}

$WIF · said × did · ● LIVE · GET /v1/tokens/WIF

Coverage

live counts, refreshed every 5 minutes

13,008calls parsed from public channels

466wallet ↔ social pairs confirmed by 2+ sources

19verified callers

122callers in the pipeline

2chains — Hyperliquid + Solana

5 minsignal freshness

Jan 2026backfilled since

Use cases

what teams build with it

Turn a token page into a verdict

Next to the chart, show who called this token and whether their wallet followed. A page that answers "can I trust this" is a page people stay on.

Give follow-lists a spine

Rank the callers your users already watch by whether their own money agreed. Sorting by receipts beats sorting by follower count.

Send alerts worth opening

A call from someone who reliably backs their words is a different event from one who never does. Filter on score, push only the ones that earned it.

How attribution works

why the set is small on purpose

Signed by the caller

Where a caller has cryptographically verified a wallet against their social account, we take that as proof and mark the pair verified.

Proven by behaviour

Otherwise we look for a wallet that repeatedly trades the tokens that caller posts, around the moment they post them. 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, so you never score someone on a wallet that isn't theirs.

This is why 19 callers are verified out of 122 tracked. We would rather ship a small 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 hand

Trial

Free

1,000 requests a month
Verified callers only
Everything except raw trades

Start free

Build

Talk to us

Volume that fits your app
All endpoints, raw trades included
Webhooks when a call lands