Turn every gaming moment into something audiences can answer.
PLLAY converts clips, creator streams and recorded gaming moments into interactive inventory without requiring the platform to become a wagering destination.
One clip, one question, one verified answer.
Illustrative — this is a demonstration of the concept, not a recording of live product behaviour.
What Happens Next?
ResearchIllustrative: ahead of a boss fight or a match-deciding play, fans call which of several outcomes occurs first.
The interaction mechanic ships today on Twitch, configured and run with the PLLAY team for every engagement — see /pulse for the product record. Running the same mechanic against a clip or archived moment, rather than only a live broadcast, is validated: every one of Vision AI's 38 benchmark trials is recorded video. Self-serve clip registration and a creator-run challenge tool are still being built.
Six ways to turn a moment into a call.
Predict the outcome
AvailableA fan calls a single outcome on a creator's live gameplay — the shipped mechanic every format on this page builds on.
Full OAuth + overlay + create-prediction path in code; cashier_config.beta_platforms_allowlist = 'twitch'.
Beat the Creator
ResearchIllustrative: a creator sets a target on their own run — a score, a time, a condition — and the audience calls whether it holds.
Creator versus creator
In DevelopmentTwo creators, one condition — each creator's own audience calls its own side of the same matchup.
Collaboration schema is merged but has zero consumers in any app or function; the creator UI cannot create one.
Fan challenge
In DevelopmentThe creator sets a condition on their own run and the audience calls whether it holds — the same mechanism as Beat the Creator, without the sponsor packaging.
Creator Challenges' own status is In Development, limited to "Not yet open to creators" (pages/CreatorChallenges.tsx) — the underlying mechanism, a challenge is a pool on the creator's own run, is shipped, but there is no self-serve challenge tool a creator can open today.
Weekly community streak
ResearchIllustrative: the same challenge runs weekly for a creator's community, building a streak fans return to defend.
Sponsored achievement
ResearchIllustrative: a sponsor funds the reward when a creator or fan clears a named achievement or milestone inside a clip.
What the mechanism produces for the platform.
Increased completion
A verified end to a clip's question, not just another play count.
Additional session depth
One more reason to keep watching past the moment that would otherwise end the session.
New sponsor inventory
A sponsorable moment inside the clip itself, not another pre-roll beside it.
Repeat participation
A call made or a streak defended gives a reason to come back for the next clip.
Creator monetization
A revenue line funded by brands buying verified participation, not carved out of an existing ad load.
Shareable results
A verified result is a real thing to share — not a screenshot of a guess.
How an answer gets confirmed.
Partner event data
AvailableA partner's own systems call PLLAY directly to open, collect and settle interactions.
partner-api is deployed with key auth, a documented rate limit, and signed, retried webhook delivery.
Vision AI where appropriate
AvailablePLLAY operates a Vision AI adapter tuned to a partner's broadcast, reading outcome evidence off the video.
38 recorded broadcasts benchmarked across 14 games, 31 auto-tier, 0 wrong auto-settles.
Signed clip metadata
In DevelopmentThe clip and its interaction marker carry cryptographically signed metadata that cannot be replayed or altered.
Webhook deliveries are HMAC-signed today (pages/Developers.tsx); the same signing discipline has not been built for clip-specific metadata.
Human review or decline
AvailableAn outcome is confirmed by the creator or an approved operator, or held and refunded rather than guessed when it can't be.
AWAITING_CREATOR_CONFIRMATION is a real prediction state and settlement is hard-gated on it; authority enforced in platform-api.
How a clip becomes an interaction.
Clip registration
In DevelopmentA clip or archived moment is registered with PLLAY before an interaction can be scheduled against it.
Clip-triggered campaigns are scoped with the PLLAY team today; there is no self-serve clip-upload flow.
Protected outcome metadata
AvailableThe outcome and its supporting evidence stay locked until the interaction window closes.
Live on every interaction today — the window locks before the outcome is knowable, the same mechanic config/pulse.ts's fan-experience record already ships.
Timeline marker
In DevelopmentA marker in the clip's own timeline opens and closes the interaction window at the right playback moment.
No timeline-marker primitive exists in the codebase for triggering an interaction at a specific playback timestamp within a clip — today's clip-triggered campaigns are scoped and timed directly with the PLLAY team.
Embedded interaction component
AvailableA chrome-free interaction surface, themed to your brand, embedded inside your own product's existing placements.
The themed embed renders from partner brand configuration and ships today — the same mechanism config/media-platforms.ts's Embed deployment pattern records.
Resolution webhook
AvailableSigned, retried webhook delivery reports the confirmed outcome back to your systems.
partner-api is deployed with key auth, a documented rate limit, and signed, retried webhook delivery.
Campaign reporting
In DevelopmentReward delivery and participation measurement, run by PLLAY on top of the events your platform reports.
Creator analytics are live in creator-platform, and the partner-facing surface (GET /v1/intelligence/summary, moments, audience, POST /v1/intelligence/exports) is deployed to production, gated behind scoped API keys and per-partner commercial terms (partner_commercial_plans). Reward delivery itself is live on every settlement; it is the partner-facing analytics half of this pairing that is still being built.
A defined set of clips. One sponsor. A real proof window.
10,000 clips or a defined creator cohort
100K+ eligible user path where available
One sponsor
Three interaction formats
Six weeks
"Where available" is load-bearing: this is a criterion PLLAY looks for when selecting a pilot surface, not a claim about audience PLLAY currently reaches.