How a signal is built. Validated end to end.

Four stages, from the data that goes in to how the output is validated. Including the part most services leave out: what happens when the model doesn't know.

How the Pearlixa Engine Works

Four stages, from the data that goes in to how we validate what comes out.

CONTINUOUS INGESTPrice & Volume30+ venuesOn-chainflows · mempoolOrder Flowdepth · L2 bookSentimentsocial · news
Stage 1 · Data Input

From Data to Signal

The four stages above, running as one continuous system. Every source to one calibrated score, per horizon.

Price & Volume30+ venuesOn-chainblockchainOrder flowmarket depthSentimentsocialENGINESHORT0.71MID0.8LONG0.64SOURCESENGINECONFIDENCE

What comes out

Every signal carries its own parameters, so you always know how sure the model is and what levels it was reading. Or that it has no read at all.

Calibrated probability

How sure the model is, on a 0–1 scale

Three horizons

Intraday to weeks, days to weeks, weeks to months

Risk parameters

Entry band, take-profit and stop-loss levels

Or nothing at all

No read means no analysis at all

ETH/USDC0.58
BTC/USDC
Sample
Confidence
0.8/ 1.00Short horizon
Entry band$67,200–67,840
Take profit$71,250
Stop loss$65,720
Short

Sometimes it returns nothing.

A model that answers everything is not being confident. When a horizon has no read on an asset, it returns no analysis at all, instead of a weak number dressed up as a strong one.

That is the part worth checking before you trust anything else on this page. A service that produces a call on everything, always, is telling you about its incentives.

See the model in action