Skip to content
wickfeed

What you get

Everyone else stops at the number. We hand you the decision.

A price feed tells your agent that something changed. Wickfeed tells it what changed, who changed it, and whether it is worth acting on. That is the whole difference between a system that reacts and a system that decides.

From a number to a decision

Five things happen before your agent hears anything.

By the time a signal reaches you it has been watched, named, weighed, matched and judged. You get the conclusion. We carry the work.

01

We watch

Every market you follow is watched continuously, the moment it moves, with nothing batched and nothing sampled.

wickfeed

You never miss a move because a poll was due in forty seconds.

02

We name

The same real world question gets one permanent name, whatever venue it trades on and however that venue labels it.

wickfeed

Your stored history stays valid for years. No renames, ever.

03

We weigh

Everything said about that market is scored for whether it truly refers to it, whether it is genuinely new, and which way it pushes the outcome.

wickfeed

One fact repeated by two hundred accounts reaches you once.

04

We match

A move and its possible causes are lined up on the same clock, so a cause that arrived after the move can never be sold to you as the reason.

wickfeed

Every market judged on its own volatility, not one blunt rule for all.

05

We decide

You receive a judgement: what happened, who caused it, and whether the market has already accounted for it.

wickfeed

A price feed ends one step earlier. That step is what you are paying for.

The first four steps are what a serious data business owes you. The fifth is what nobody else will hand over.

The four signals

Write the handler once. It still runs in 2028.

Every signal arrives in the same shape, so your agent learns one format and keeps it. New elections, new markets and new sources arrive inside it without touching your code.

wickfeed.moved The mid crossed this contract’s adaptive threshold. Deterministic, no model in the path. ~90ms
wickfeed.mouth A watched source spoke about this contract, with relevance and novelty attached. ~90ms
wickfeed.print An official result, filing or document landed from a tracked source. ~90ms
wickfeed.lit A qualifying move and a novel, relevant cause coincided in the window. Carries the verdict. 1 to 3s verdict

Signal, not volume

On the loudest night of the year, you get one alert per fact.

When something big breaks, every account you follow repeats it within minutes. Your agent hears it once, with the corroboration attached, and keeps its judgement clean at exactly the moment noise peaks.

Relevance, 0 to 100

How strongly this text refers to this identified contract. Below the floor it cannot light a fuse, no matter how loud the source.

Novelty, 0 to 100

The first candidate reporting a fact in a 24 hour window scores 100. Every retelling decays. Only the most novel candidate can light; the rest become corroboration on the same wick.

Stance, not sentiment

Measured against the contract’s resolution criteria, as pro yes, pro no, or unclear. A statement can be positive in tone and still push the contract the other way.

Authority, learned

Whether a source is load bearing is not asserted, it is measured from our own archive: who historically leads the mid. This compounds every day the engine runs.

Published floors

Relevance to light a fuse 70
Novelty to light a fuse 60
Judge confidence to name a cause 0.55
Attribution below which driver is unknown 0.30

These are published because a subscriber who knows the floors can calibrate their own risk. Hiding them would make the feed less useful, not more defensible.

Your backtest tells the truth

What you test on is exactly what you traded on.

Ask us for any moment in the past and you get precisely what your agent received at the time. Strategies that work in your research run the same way in production, because the history and the live feed are the same thing.

Nothing is judged early

We wait until everything from a given moment has actually arrived before deciding what caused a move. Your agent gets a settled answer rather than a first guess that changes a second later.

Byte identical replay

Replaying an archived input sequence produces an identical output sequence. This is a tested requirement, not an aspiration.

Late events are recorded, never retrofitted

An event arriving after its window closed is marked late and counted. It never silently rewrites a wick that was already published.

Gaps are visible

A disconnected source produces a recorded gap with a start and an end, shown on the status page. A gap is never filled with interpolated data.

Your agent is already watching the price. Give it the reason.

Start free. Real time from the first minute, five events an hour. One key and eight lines of code.

Subscribe on npayload
$ npx npayload subscribe wickfeed.lit

No card. No login. No dashboard.