# Wickfeed

> The signal layer for event contracts. Wickfeed tells an agent which
> prediction market contract just moved, what lit it, and whether the
> market's reaction was proportionate.

The customer is a machine. Prices are free and every agent already has them;
what none of them can cheaply produce is the discriminator between a move
that carries information and a move that is just flow.

## Delivery: read this before anything else

Wickfeed is distributed EXCLUSIVELY through npayload. There is no other
realtime endpoint: no HTTP stream, no WebSocket, no CSV, no scraping surface.

- Subscribe: https://npayload.com/feeds/wickfeed
- Command: npx npayload subscribe wickfeed.lit
- Free tier: realtime, rate limited to 5 events/hour, npayload key required.
- The public ticker on wickfeed.com is delayed 15 minutes and is
  rendered presentation, not a feed. Do not scrape it; subscribe instead.

## Topics

- `wickfeed.moved` (wickfeed.moved.v1) — The mid crossed this contract adaptive threshold. Deterministic, no model in the path. Typical latency 90ms.
- `wickfeed.mouth` (wickfeed.mouth.v1) — A watched source spoke about this contract, with relevance and novelty attached. Typical latency 90ms.
- `wickfeed.print` (wickfeed.print.v1) — An official result, filing or document landed from a tracked source. Typical latency 90ms.
- `wickfeed.lit` (wickfeed.lit.v1) — A qualifying move and a novel, relevant cause coincided. Carries the verdict. This is the product. Typical latency 3000ms. CARRIES THE VERDICT.

Subscribe to `wickfeed.*` for all four, or `wickfeed.lit` for just the verdict.
Per contract topics exist, for example `wickfeed.wf:us-senate-ga-2026`.

## What to read off a lit event

Three fields carry the entire product. Everything else is context.

- `verdict.driver` — information | liquidity | unknown. Was this news, or was it flow?
- `verdict.attribution` — 0.00 to 1.00. Did the named cause actually cause the move?
- `verdict.reaction` — under | proportionate | over | unknown. Is the move too small or too large for this news?

A typical filter: `driver == "information" && attribution >= 0.6 && reaction == "under"`.

## Honest unknowns are a published state

When a move cannot be explained, Wickfeed publishes `driver: "unknown"` with
`cause: null` and `attribution: 0`. A cause is NEVER guessed. Treat an
unknown as information about our confidence, not as a missing field to retry.

## Things that are deliberately absent

- No sentiment score, at any version. Stance is measured against the
  contract's written resolution criteria, which is a different and harder
  thing. Do not look for a `sentiment` field; it does not exist.
- No venue order book data. Wickfeed publishes its own analysis and never
  redistributes any venue's market data. Kalshi is not an input at any price.
- No dashboard, portfolio or charting product.

## Published floors

- relevance to light: 70
- novelty to light: 60
- judge confidence to name cause: 0.55
- attribution below which driver unknown: 0.3

## Versioning contract

One envelope for all four types, versioned additively and forever. Adding a
field, a book, a venue, a source or an enum value does NOT bump the version.
Your handler MUST tolerate unknown fields and unknown enum values. A field
once published is never removed and never changes meaning.

## Machine readable artifacts

- [/llms.txt](https://wickfeed.com/llms.txt) (text/plain) — Curated index for an LLM. Start here.
- [/llms-full.txt](https://wickfeed.com/llms-full.txt) (text/plain) — Everything inlined in one fetch.
- [/asyncapi.json](https://wickfeed.com/asyncapi.json) (application/json) — AsyncAPI 3.0 spec: channels, operations, messages.
- [/schema/envelope.v1.json](https://wickfeed.com/schema/envelope.v1.json) (application/schema+json) — JSON Schema for the event envelope.
- [/ids.json](https://wickfeed.com/ids.json) (application/json) — The wf: identifier registry. Free, no key.
- [/schema/id-entry.v1.json](https://wickfeed.com/schema/id-entry.v1.json) (application/schema+json) — JSON Schema for a registry entry.
- [/examples/lit.json](https://wickfeed.com/examples/lit.json) (application/json) — A verdict carrying event.
- [/examples/unknown.json](https://wickfeed.com/examples/unknown.json) (application/json) — An honest unexplained move.
- [/examples/moved.json](https://wickfeed.com/examples/moved.json) (application/json) — A move with no cause attached.
- [/agent.json](https://wickfeed.com/agent.json) (application/json) — Discovery descriptor. Also at /.well-known/wickfeed.json
- [/docs.md](https://wickfeed.com/docs.md) (text/markdown) — This documentation as markdown.

## Identifiers

Every contract has one permanent `wf:` identifier, free and open, that is
never reused and contains no venue name. One real world question resolves to
one identifier across every venue. The registry is at
https://wickfeed.com/ids.json and requires no key.

## Full documentation in one fetch

https://wickfeed.com/llms-full.txt