← Back to the tool

How it works & proof

We detect coordinated engagement — not follower counts. A "bot-pod" is a group of accounts that like the same posts, together, inside tight time windows, over and over. That is the social-graph equivalent of coordinated on-chain wallet clusters.

The two signals

1. Temporal coordination — accounts engaging within a tight window (≤8 min) of each other, repeatedly
2. Co-engagement lift — a group whose shared engagement far exceeds chance (normalized by each account's own activity, so real super-fans are NOT flagged)
+ k-core & relative-degree — a real pod is a dense clique; coincidental overlap is sparse and gets pruned
+ account metadata — empty bio, low followers, and batch-created FIDs (consecutive ids = mass registration) separate real super-fans from bots

Validation (how we know it works)

Adversarial synthetic scenarios (tight pod, loose pod, mixed)100% caught
  ↳ false-positives across 800+ organic accounts0
Power-fan test (real super-fans who like everything)0 flagged
Hybrid test: 15-account bot-pod injected into a real account's engagement15/15 caught
  ↳ real accounts wrongly flagged (out of 250)0
Real legit accounts scanned (dwr, vitalik.eth, …)clean ✓

The hybrid test is the key one: we take a real account's genuine engagement (with all its natural noise), inject a coordinated bot-pod, and confirm the detector catches the whole pod while leaving every real account untouched.

For developers / agents — 4 tools

Account authenticity (0-100 score + bot-pods)GET /v1/authenticity?username=X
Who's boosting (list the bot accounts)GET /v1/bots?username=X
Compare two accountsGET /v1/compare?a=X&b=Y
Cast check (is a cast bot-heavy?)GET /v1/cast?hash=0x…
MCP (streamable-http)POST /mcp — 4 tools: check_farcaster_authenticity, who_is_boosting, compare_accounts, check_cast
Payment discovery/.well-known/x402.json (free beta)

Honest limits

← Try the tool