How signals work

Every signal in Rubick is a call somebody actually made in public, with the post attached.

The roster

Rubick monitors over 1,500 KOL accounts on X, continuously expanding. The roster includes exchange listing announcement accounts, such as Binance and Coinbase, so a listing headline can become a tradeable signal the moment it drops.

The classifier

An AI classifier reads each post with live market context and decides whether it is a genuine trade call, extracting the asset and the direction. Price reports, relayed headlines and market mood posts are filtered out. Only real calls become signals.

Where signals show up

Classified calls appear in your feed and as markers on charts, with the original post text quoted. Nothing is hidden behind a summary: you always see the source, so you judge the call in the caller’s own words rather than trusting a label.

Discord communities

Group call signals from Discord communities are ingested too, and show in the feed with the community name attached.

Grading the callers

Every classified call is scored against what the market actually did after it. Those scores follow the caller everywhere in the app, on their profile, on signals and on the leaderboards, so you can see who has receipts and who has vibes before you copy anyone.

Request a caller

Missing your favorite caller? Request any X handle from inside the app, with Compile and add or the ⌘K recommend action. User requests jump the queue ahead of background jobs.

Execution semantics

• Trades fire at signal ingest. The moment a post classifies as a call, copies execute.
• Deletions do not undo trades. If the KOL deletes the tweet later, the trade stands, and Rubick keeps the tweet as proof of what was called and when.
• Flips follow the caller. If a KOL flips direction, your position flips or closes, unless your own parameters already closed it.