All case studies
Crypto exchangeNLP · Streaming analytics

Real-time sentiment intelligence that speaks fluent crypto.

How we built an autonomous social intelligence platform for MEXC — separating real market signals from bots, slang and coordinated FUD across X, Telegram, Discord and Reddit.

CLIENT
MEXC
INDUSTRY
Crypto exchange
MODEL
Self-hosted Qwen on vLLM
STACK
pgvector · Zod · Next.js
XTelegramDiscordReddit
Bullish
Neutral
Bearish
Panic / FUD
FUD spike alert sent to Slack
telegram ›
“liquidation cascade incoming, dev rugged??”
CLASSIFIEDsentiment = PANIC/FUD · alert = slack

Generic social listening can’t read “rekt”.

MEXC needed 24/7 visibility into brand perception, user sentiment and campaign performance across hyper-active, fragmented crypto communities on X, Telegram, Discord and Reddit.

The chatter moves fast and is dominated by slang, bot-driven spam, rapid market swings and coordinated FUD campaigns. Traditional social listening tools couldn’t tell actionable signals from noise — or measure whether a campaign actually landed.

Four layers from raw chatter to a decision.

A · INGESTION

Streaming ingestion & noise scrubbing

Pipelines across X, Telegram, Discord and Reddit, with deterministic filters for bot spam, duplicate airdrop promos and cashtag hijacking.

B · CLUSTERING

Semantic narrative clustering

1024-dim embeddings in pgvector HNSW group chatter into narrative threads in real time — feedback, feature requests and emerging controversies.

C · AI CORE

Crypto-native sentiment engine

A self-hosted Qwen with Zod-enforced JSON reads HODL, rekt, moon and rugpull to classify Bullish, Bearish, Neutral and Panic/FUD — and attributes spikes to campaigns.

D · ACTION

FUD alerts & command center

Influence scoring separates high-impact voices from retail noise; anomaly alerts hit Slack and Telegram, and a live Next.js command center tracks it all.

Two analytics tracks, one private AI core — and alerts within seconds.

  1. LAYER 1Ingestion routerX · Telegram · Discord · Reddit
  2. LAYER 2ACampaign analytics#Airdrop · #Listing · KOLs
  3. LAYER 2BCommunity sentimentpgvector HNSW clustering
  4. LAYER 3Qwen AI corePrivate vLLM + Zod
  5. LAYER 4Alerts & command centerSlack · Telegram · Next.js
SIGNAL HYGIENEBot spam pruningAirdrop spam dedupCashtag hijack filteringInfluence-weighted scoring
LAYERMODULETECHNOLOGYSCOPE
1Multi-channel ingestion & filter routerAPI streams & webhooksX, Telegram, Discord, Reddit; bot spam pruning & cashtag dedup
2ACampaign & post analyticsMarketing analytics pipelineCampaign hashtags, KOL amplification & virality metrics
2BBrand & community sentimentReal-time NLP + pgvector HNSWMood index, FUD anomaly detection, narrative clustering
3Self-hosted Qwen AI corePrivate vLLM + Zod schemasCrypto-slang understanding, campaign attribution, structured JSON
4AReal-time operational actionsAutomated dispatchInstant Telegram & Slack alerts on FUD spikes or sentiment shifts
4BExecutive command centerNext.js real-time analyticsLive sentiment, campaign ROI, competitive share of voice, heatmaps

Signal, not noise — in real time.

4channels in one stream — X, Telegram, Discord and Reddit
Secondsfrom a coordinated FUD spike to an alert for PR, risk and comms
0trading intelligence sent to third-party LLM APIs — Qwen runs on private vLLM

More case studies

Have hardware, data or a process that needs AI it can trust?Evaluate your use case

Evaluate your use case

Tell us what you want AI to do. We'll come back to you by email.