Buyers · Platforms & publishers
Embed the oracle.
Ship the proof.
Add interactive entertainment and monetization to your community.
Objectives this is built for.
The problem
Building verification in-house means vision models, rule engines, dispute flows and a ledger. That isn't your product.
PLLAY use case
Call POST /v1/events from your product and listen for event.settled and event.held. Stake, KYC and payments stay on your rails.
What PLLAY verifies
- VERIFYOutcomes on Vision-verified titles via adapter
- VERIFYPartner-verify results you send us
- VERIFYConfidence against your threshold, per event
What PLLAY settles
- SETTLEState through the six-state machine
- SETTLEWebhooks: event.settled, event.held, event.reversed, event.voided
- SETTLEReversals as compensating entries, never edits
Commercial model
LicensePlatform license, $500K+ a year.
UsageOracle usage on verified events, evidence and settlement calls.
KeysSandbox and production keys are arranged with the PLLAY team.
Example activationIllustrative
A stream tool adds "call the round" to its overlay. It registers each round by API, receives event.settled or event.held, and renders the result in its own UI.
- POST /v1/events
- → locked
- → Vision read
- → event.settled
- → Rendered in your UI