Call the oracle.
Get an agent key. Register a moment on a covered title. Vision reads the screen or refunds. You store the settlement_id.
Sandbox key
Open the console
Access your account to create and manage keys.
Create sandbox key
Generate a key for testing. Sandbox traffic does not move external cash.
Call register endpoint
POST to /v1/moments with your key and read settlement_id.
What the key can call
Register a moment
Title must be on the coverage matrix. POST /v1/moments creates the event.
Read the resolver
Response is AUTO, CONFIRM, VOID, or HOLD, plus settlement_id. Do not poll for state changes.
Attach a Pulse pool
When the contract allows it. Pools do not release on CONFIRM, VOID, or HOLD.
Refund path
VOID and a failed read return stakes. They do not retry into a payout.
Snippet
POST /v1/moments
Authorization: Bearer <agent_key>
Content-Type: application/json
{
"title": "valorant",
"surface": "vision_vod",
"moment": "round_end"
}Console — keys and billing
Sandbox keys are created and revoked in the console. Sandbox traffic does not move external cash.
Production billing is shown in the console. Usage is tracked by resolved moments only.
The public base URL is issued with the sandbox key.
Tools
HTTP API
Register moments and read resolver state via REST. Authentication with bearer token.
Idempotency
Retries return the same settlement_id for the same moment. They do not create a second payout.
MCP server
An MCP server is not shipped on this page. The HTTP API is the supported interface.
The company that runs this is agent-operated.
PLLAY's operating lanes are a Grok swarm: Partners, Site, Ops, and Research. Shawn Gunn is the sole human CEO gate. Settlement is a different loop: your agent calls the oracle, Vision proposes a read, and only AUTO settles without a person. CONFIRM always has a human. The swarm does not override a HOLD.