Skip to content
wickfeed

Pricing

Machines pay. Humans watch.

Every tier is realtime. The free tier is rate limited rather than delayed, because an agent cannot evaluate a delayed feed. Keys, metering and billing are npayload’s, so there is no setup fee, no Wickfeed account, and no card taken on this site.

Free

$0

For the agent you are still writing.

  • Realtime wickfeed.lit
  • Five events an hour
  • npayload key required
  • Free identifier registry
  • Published event schema
Subscribe on npayload

Pack

$29/mo

The whole feed, one consumer.

  • All four event types
  • Every contract in the registry
  • 24 hour replay
  • 1 consumer
  • Community support
Subscribe on npayload
Recommended

Desk

$99/mo

For an agent that is trading.

  • Filters by book, venue and driver
  • 7 day replay
  • 10 consumers
  • Reaction and reaction gap
  • Email support
Subscribe on npayload

Priority

$299/mo

When the window is the product.

  • 30 day replay
  • Priority publish
  • Unlimited consumers
  • Full corroboration payloads
  • Archive export
  • Direct line
Subscribe on npayload

Runtimes, terminals and desks

Embedding Wickfeed inside an agent platform, a broker terminal or a media system is a different shape: dedicated topics, a negotiated service level, and a seat count instead of a consumer count. Priced per deal, for teams that need to surface the output to their own users.

Talk to us

Before you subscribe

The questions that actually get asked.

Why is npayload the only way to subscribe? +

npayload already provides keys, metering, billing, replay, consumer groups and an audit trail, so Wickfeed runs no subscriber accounts and no billing of its own. It also means one realtime door: no public HTTP, WebSocket or SSE endpoint serves realtime event JSON to an unauthenticated caller.

Is the free tier delayed? +

No. The free tier is realtime and capped at five events an hour. Delay is the gate for the public human surface, which runs at least fifteen minutes behind. A rate limit is the gate for machines, because an agent cannot evaluate a delayed feed.

What happens when a book resolves? +

Resolved contracts are archived and their identifiers stay permanent. A new book is registry entries plus sources, and its events validate against the same envelope version with no schema change, so a handler written for one book processes the next one with no code changes.

Do you redistribute venue market data? +

No. Wickfeed observes public sources and publishes its own analysis. A registry mapping carries the venue name, that venue’s own reference and a public URL, and never a price, a size or order book depth.

Can I pass the feed on to my own users? +

Not on a standard subscription, which covers your own systems. Surfacing Wickfeed output to your users is a runtime deal, priced per deal.

What is the uptime commitment? +

There is no published uptime number yet, and we will not invent one before the engine has run. Every interruption is recorded as a gap with its exact start and end and shown on the status page. Named commitments come with desk and runtime agreements.

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.

Subscribe on npayload
$ npx npayload subscribe wickfeed.lit

No card. No login. No dashboard.