Skip to main content
OpenKol is built around one workflow: take a call → verify it → make it shareable.

​
Multi-platform input

  • Accepts X and Telegram post URLs
  • Detects the correct post/message identifiers
  • Prompts for a symbol choice when multiple tickers are detected

​
Token and market resolution

  • Token / market lookup to resolve assets and pairs
  • Pair details (price + liquidity context)
  • Candle data across multiple resolutions:
  • 5m, 15m, 30m, 1h, 4h, 12h, 1d

​
Scorecard output

Each analysis returns:
  • Social score (0–100)
  • Chart score (0–100)
  • Overall score (0–100)
  • Medal grade (fast filter)
  • A chart view anchored to the call timestamp
  • A breakdown of the drivers behind the score
Learn more:

​
KOL profiles (snapshot + aggregation)

  • KOL profile snapshot with aggregated metrics
  • Performance tiers (S–D) for fast scanning
  • History-based scoring so one lucky post doesn’t dominate
Learn more: KOL profile scoring

​
Discovery / browsing

  • “More posts” panels (top / worst / latest buckets)
  • Fast comparison across calls using consistent scoring

​
Sharing and reuse

  • Canonical analysis routes for each post/call
  • Open Graph images (OG cards) built for social previews
  • Local history caching + server-side caching for fast reloads

​
For developers (internal API surface)

If you’re integrating OpenKol inside another product or workflow, these internal routes exist:
  • POST /api/analyze/tweet — analyze a post and return scores, pair data, and candles
  • POST /api/x/tweet — fetch normalized X post details
  • GET /api/telegram/avatar — return channel avatar and metadata
  • GET /api/og/post — render a shareable OG image
  • GET /api/health — health checks (and subroutes)
Note: these endpoints are implementation details and may evolve. For stable integrations, use the documented product surface and/or request an official API.

​
Next