A realtime feed for autonomous systems
Wick or fakeout? Your agent gets the reason the price moved.
A prediction market price jumps. Wickfeed sends one event naming what happened, who caused it, and whether the market has already priced it in. When the cause is not established, the event says unknown instead of guessing. Every published verdict is scored against the price 5, 15 and 60 minutes later, and the miss rate is published. Prediction markets first.
Free tier, realtime, five events an hour.
The cost of a bare number
The number says something changed. Nothing more.
Your agent reads the new price and has to guess the cause. It has two ways to guess, and both cost money quietly, because neither one looks like a loss on the day.
It acts on noise
Every flicker reads as news. Your agent takes a position on movement that reverses inside a minute, and pays the spread each time it does.
Or it waits for confirmation
By the time a fact is obvious, the price already holds it. Arriving after the move is not discipline. It is late.
Both come from the same gap
A system asked to decide without being told what happened can only react or wait. Close the gap and the choice goes away.
What lands in your system
Write one handler. Keep it.
Four event types share one envelope with an explicit version. New books, venues and sources arrive inside that envelope, and adding one never bumps the version, so the handler you write this week keeps running.
Something moved A price crossed the threshold derived from that contract’s own recent volatility. on arrival Someone spoke A watched source said something about that contract, scored for relevance and novelty. on arrival Something official landed A result, filing or document arrived from a tracked source. on arrival It caught A move and a novel, relevant cause fell in the same window. This one carries the verdict. when the window closes verdict The first three report what happened. The fourth carries the judgement, and it is the one most agents filter on.
See what it sendsWick or fakeout, answered three ways
Three answers, then your agent can size a position.
These are the questions a system has to settle before it risks money. Every published verdict carries all three.
What happened information · liquidity · unknown
Tell a fact from money moving.
A move where the whole order book shifted together is never attributed to a contract specific cause. Your agent is told it was flow, even when a headline landed in the same minute.
Who moved it named source, relevance and novelty 0 to 100
Get the source, and how much weight it carries.
A source that spoke after the move is never presented as the cause, and a source we did not observe is never named at all.
What it is worth under · proportionate · over · unknown
See whether the move went far enough.
This is the field that becomes a trade. It is scored against the price 5, 15 and 60 minutes later, and the misses are published.
When the cause is not proven, the event says unknown.
Attribution below 0.30 sets the driver to unknown, and a verdict below the publish floor is withheld: you get the move with no cause named. Your agent stands down instead of trading a reason we invented.
See all three answers{
"driver": "unknown",
"cause": null,
"attribution": 0.0,
"reaction": "unknown"
}Eight lines
Get a key, subscribe, filter.
Wickfeed publishes to npayload and nowhere else. One key, one bill, one subscription, and no Wickfeed account to manage.
# one key, one command
npx npayload login
npx npayload subscribe wickfeed.lit
# filter to what your agent trades
npx npayload subscribe wickfeed.lit \
--filter 'book=midterms' \
--filter 'driver=information' \
--filter 'reaction=under'What comes with the subscription
- One npayload key and one bill, however many books you follow.
- Replay by offset, so your agent can read a past window again.
- History that matches the live feed byte for byte.
- Duplicate safe delivery. The same wick_id twice is safe to discard.
Machines read events as they publish. The public human surface is delayed by at least fifteen minutes and carries rendered cards, never JSON.
Why you can put money behind it
You should not take our word for it.
You are deciding whether a signal may move your money. Here is what you can check before it does.
Read the miss rate
The record page publishes the count of wicks, the count with driver unknown, and the count where the verdict was wrong, broken down by driver class. Every figure is computed from the archive, never typed in.
Replay any moment
A query for a past timestamp returns only what was known then. Corrections are stored as new versions and the original stays retrievable.
Reproduce the output
Replaying an archived input sequence produces a byte identical output sequence, because a window is ordered by the source clock rather than by arrival.
Keep your code working
An identifier is never reused, and a field once published is never removed or redefined. A new book arrives without a version bump.
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.