What you get
A price feed stops at the number. This one carries the verdict.
You get what moved, who moved it, and whether the market has already priced it in. Every floor that gates an emission is published, so you can calibrate your own risk against it.
From a number to a decision
Five steps run before your agent hears anything.
A move is watched, named, weighed, matched and judged. You receive the conclusion and the evidence behind it.
Watch
Every subscribed contract is watched over a push connection. Nothing is polled and nothing is sampled.
Name
One real world question gets one wf: identifier, whatever venue it trades on and however that venue labels it.
Weigh
Every candidate carries relevance from 0 to 100 and novelty from 0 to 100. The first report of a fact in a 24 hour window scores 100.
Match
A window is ordered by the source clock, and a candidate that spoke after the move cannot be its cause.
Judge
Every qualifying move is judged and scored against its outcomes. A verdict publishes only at or above the publish floor, which starts at 0.70.
The publish floor is listed on the record page with the date of every change, and the count of moves judged in private is published beside the miss rate.
The four event types
Write the handler once. It still runs in 2028.
Every event arrives in the same envelope, so your agent learns one shape and keeps it. New books, venues and sources arrive inside it without touching your code.
wickfeed.moved A qualifying move with no candidate cause. The threshold in force travels in the envelope. on arrival wickfeed.mouth A watched source spoke about this contract, with relevance and novelty attached. on arrival wickfeed.print An official result, filing or document from a tracked source. on arrival wickfeed.lit A qualifying move and a novel, relevant cause in the same window. Carries the verdict. when the window closes verdict Signal, not volume
One fact, one event.
When something breaks, every account you follow repeats it within minutes. Novelty scoring means your agent hears it once, with the repeats attached as corroboration on the same wick.
Relevance, 0 to 100
How strongly this text refers to this identified contract. Below 70 a candidate cannot light a fuse, however loud the source.
Novelty, 0 to 100
The first candidate reporting a fact in a 24 hour window scores 100. Later candidates score lower and appear as corroboration, never as a second event.
Stance, never sentiment
Measured against the contract’s resolution wording as pro yes, pro no, or unclear. No sentiment field exists in the envelope, at any version.
Attribution, 0 to 1
Confidence that the named cause produced the move. It weighs whether the candidate predates the move and whether the broader order book moved at the same time.
Published floors
70 60 0.55 0.30 0.70 2.2 sigma of that contract, clamped to 0.02 and 0.12 The floors are published so you can calibrate your own risk against them. A change to the publish floor is dated on the record page, and it is lowered only when the private record for that band beats the book’s stated quality bar.
Your backtest tells the truth
What you test on is what was published.
Ask for a past timestamp and you get only what was known then. Research and production read the same bytes.
Windows close on the source clock
A window is ordered by the source’s own timestamp and closes on a watermark with bounded lateness, so inputs arriving out of order do not change the output.
Replay is byte identical
Replaying an archived input sequence produces an identical output sequence. A spec driven test asserts it on every run.
Late events are recorded, never retrofitted
An event arriving past the lateness bound is marked late and counted. It never alters a wick that was already published.
Gaps are visible
A dead source connection is recorded as a gap with a start and an end and shown on the status page. A gap is never filled with interpolated data.
Your agent sees the price move. Send it the reason.
Subscribe with an npayload key. The free tier is realtime, capped at five events an hour, and eight lines of code print your first event.
No card. No login. No dashboard.