Predictions

The prediction model

Pick an outcome before it is known, and get paid for calling it right.

What a prediction is, how it ends, and the one setting that decides whether it works.

Predictions are their own feature, with their own place in the Hub and in your product. Today they run on the quest system underneath, and that is changing. This page describes the feature. How it ships today covers what that means for your code right now.

A prediction

A prediction asks fans to pick an outcome before it is known. A match result, a roster move, a scoreline, which colourway drops on Friday. Entries close at a set time, and when the thing happens your community team marks what was right. Everyone who picked it gets the reward.

It is free to enter. Nothing is staked and nothing is wagered, and a fan can never end up worse off for answering.

Options, the lock time and resolving the outcome are all done in the Hub. Predictions in the Hub docs covers that side.

Who wins on Saturday?Try it
PredictionCloses Sat 14:00
262 entries · Reward: Signed shirt raffle
Choose a side to see the latest split.
What the machine says
state.machine.reasonNORMAL
state.canClaimfalse
Move time along
Switch as often as you like. Submit sends { text: option.label }, and the pick is final. The split is useQuestResults. The lock and the pick come back as state.machine.reason. Example data.

How it ships today

This will change. Predictions are moving to a surface of their own in the SDK. Until that ships, a prediction is delivered as a quest, and the code on Building a prediction reflects that. Keep your prediction UI in its own component, so the move is a change to the data it reads rather than a rebuild.

Right now a prediction arrives as a quest whose template is basic.prediction. That means it:

So in your product, treat it as its own thing. Give predictions their own page or their own strip, filter them out of your quest list by template, and do not make a fan look for them among the quests.

Options

Each option has:

FieldWhat it is
labelThe plain answer. This is what your team resolves against, and what the fan's pick is sent as.
descriptionOptional. One line under the label, like "Unbeaten at home since March".
imageUrlOptional. A small image beside the label.

The label is the answer. The description is the reason to pick it. Render both.

The lock

Every prediction has a lock time, lockAt. Before it, fans can enter. After it, entries are closed, whether or not the outcome has been marked yet.

The platform enforces the lock by the clock. The quest machine reports it as PREDICTION_LOCKED and your options stop responding.

Show the lock time on the card before it passes. "Closes Saturday 14:00" is the deadline that makes the prediction feel live.

One pick, final

A fan picks once. The pick is final the moment they submit, and the machine then reports PREDICTION_SUBMITTED. A fan who comes back sees what they picked, not the options again.

The split

How everyone else has picked is visible, as a count per option. That is the one place a prediction behaves differently from a poll. A poll hides its result until you vote, so other people's answers cannot pull yours. A prediction shows it, because being with the crowd or against it is most of the fun.

Resolution

Until your team marks the right answer, the quest sits locked and unpaid. There is no automatic resolution, because the platform has no way to know what happened at your event.

Once it is resolved, a fan who picked the right option has the quest's reward waiting for them to claim, through the ordinary claim flow. A fan who picked anything else has nothing to claim, and loses nothing.

It is not betting

There is no stake, no odds and no payout that scales with how many people were wrong. Everyone who is right gets the same reward: the one set on the quest.

What is coming

A standalone predictions surface, outside the quest system. The behaviour on this page stays the same: options, a lock, one final pick, a visible split, a resolution that pays the fans who called it. What changes is where your code reads it from. Feature status.

On this page