Sandbox
The deterministic scenarios behind test keys, how to choose and speed them up, and how the sandbox differs from live analysis.
Any key that starts with sk_test_ reaches the sandbox. It answers the whole contract, and its sessions and recordings play scenarios: scripted, deterministic event timelines, the same ones that generate the examples throughout these docs. The same scenario always produces the same events.
Choosing a scenario
{ "sandbox": { "scenario": "man-peak", "speed": 20 } }scenario defaults to woman-onset-end. speed plays it faster than real time, from 1 to 60: 10 by default for live sessions, 60 for recordings. Stream times in events stay on the scenario's own clock, so a call at streamTimeS: 704.2 arrives about 35 seconds in at speed 20.
subjectHint and inputs apply as they would live: a man hint on a woman's scenario suppresses its onset and end calls, and inputs.audio: false leaves only imminence and the subject read.
The scenarios
woman-onset-end
| sequence | streamTimeS | type | confidence | data |
|---|---|---|---|---|
| 1 | 0 | session.status | — | ready |
| 2 | 0 | session.status | — | calibrating |
| 3 | 0 | input.warning | — | baseline_pending raised |
| 4 | 32 | subject.identified | high | woman (pWoman 0.94), detectors onset_end |
| 5 | 62 | session.status | — | analyzing |
| 6 | 62 | input.warning | — | baseline_pending cleared |
| 969 | 542.6 | orgasm.onset | high | #1 at 538 s, called 4.6 s later, score 0.71 |
| 1046 | 580.2 | orgasm.end | high | #1 at 575 s after 37 s, onset_end, called 5.2 s later |
| 1205 | 660 | session.status | — | ended, media_ended |
man-peak
| sequence | streamTimeS | type | confidence | data |
|---|---|---|---|---|
| 1 | 0 | session.status | — | ready |
| 2 | 0 | session.status | — | calibrating |
| 3 | 0 | input.warning | — | baseline_pending raised |
| 4 | 31 | subject.identified | high | man (pWoman 0.07), detectors peak, face_end |
| 5 | 62 | session.status | — | analyzing |
| 6 | 62 | input.warning | — | baseline_pending cleared |
| 1293 | 704.2 | orgasm.peak | high | #1 at 701 s, called 3.2 s later, score 0.66 |
| 1376 | 745.5 | orgasm.end | high | #1 at 742 s after 41 s, face_end, called 3.5 s later |
| 1445 | 780 | session.status | — | ended, media_ended |
undetermined
face-only
face-lost
| sequence | streamTimeS | type | confidence | data |
|---|---|---|---|---|
| 1 | 0 | session.status | — | ready |
| 2 | 0 | session.status | — | calibrating |
| 3 | 0 | input.warning | — | baseline_pending raised |
| 4 | 31 | subject.identified | high | woman (pWoman 0.89), detectors onset_end |
| 5 | 62 | session.status | — | analyzing |
| 6 | 62 | input.warning | — | baseline_pending cleared |
| 483 | 300 | input.warning | — | face_not_visible raised |
| 484 | 300 | session.status | — | analyzing, degraded |
| 525 | 320 | input.warning | — | face_not_visible cleared |
| 526 | 320 | session.status | — | analyzing |
| 937 | 524.8 | orgasm.onset | high | #1 at 520 s, called 4.8 s later, score 0.69 |
| 1012 | 561.4 | orgasm.end | high | #1 at 556 s after 36 s, onset_end, called 5.4 s later |
| 1289 | 700 | session.status | — | ended, media_ended |
edge
Each approach ends in an edge.completed:
| sequence | streamTimeS | type | confidence | data |
|---|---|---|---|---|
| 1 | 0 | session.status | — | ready |
| 2 | 0 | session.status | — | calibrating |
| 3 | 0 | input.warning | — | baseline_pending raised |
| 4 | 31 | subject.identified | high | man (pWoman 0.05), detectors peak, face_end |
| 5 | 62 | session.status | — | analyzing |
| 6 | 62 | input.warning | — | baseline_pending cleared |
| 706 | 411 | edge.completed | high | edge 1: p30 0.6 at 362 s, peak 0.687, below 0.3 49 s later |
| 1067 | 591 | edge.completed | high | edge 2: p30 0.6 at 548 s, peak 0.669, below 0.3 43 s later |
| 1468 | 791 | edge.completed | high | edge 3: p30 0.6 at 747 s, peak 0.684, below 0.3 44 s later |
| 1686 | 900 | session.status | — | ended, media_ended |
ruin
The scenario reports stimulation as a product running the ruin preset would: on at the baseline, off where the preset stops. Its imminence is stimulation-aware from the baseline, and the orgasm's end says ruined: true.
| sequence | streamTimeS | type | confidence | data |
|---|---|---|---|---|
| 1 | 0 | session.status | — | ready |
| 2 | 0 | session.status | — | calibrating |
| 3 | 0 | input.warning | — | baseline_pending raised |
| 4 | 31 | subject.identified | high | man (pWoman 0.08), detectors peak, face_end |
| 5 | 62 | session.status | — | analyzing |
| 6 | 62 | input.warning | — | baseline_pending cleared |
| 1115 | 615.3 | orgasm.peak | high | #1 at 612 s, called 3.3 s later, score 0.57 |
| 1172 | 643.9 | orgasm.end | high | #1 at 640 s after 28 s, face_end, called 3.9 s later, ruined |
| 1445 | 780 | session.status | — | ended, media_ended |
finish
How the sandbox differs from live analysis
- Free. Sandbox sessions count orgasms, ruins and edges as live ones do, in their
chargesand your test usage, and draw no credits:creditsstays 0. Credits and billing says what each scenario counts. - No media. A sandbox session starts its scenario as soon as it is created.
ingest.urlanswers501 sandbox_no_media, and the attestation policy for test mode says there is nothing to verify. - Scripted. Scenarios do not react to what you do. Reporting stimulation sets
stimulationAwarefrom then on but does not change the curve, or which orgasms are ruined. - Uploads are discarded. Recording uploads are read and thrown away. Use any small video file, never a real recording of a person.
- Thresholds are illustrative. Detector
scoreandthresholdvalues are the sandbox's, not live operating points. - Usage, credits and API keys answer with the examples in the contract.
- State lives in memory. Sessions, recordings and webhook endpoints last until the sandbox restarts.
Running it yourself
From this repository, npm run dev serves the sandbox with the docs at http://localhost:3000/v1, and npm run mock serves it alone at http://localhost:4010, together with the WebSocket channel.