orgasm.dev

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

A woman's orgasm: onset, then end: imminence and orgasm calls over 11 minutes00.510 min2 min4 min6 min8 min10 minbaselinesubject: womanonsetend
A woman's orgasm: onset, then end. The face reads as a woman’s after about 30 seconds, imminence climbs over nine minutes, and the onset and end of one orgasm are called a few seconds after each happens. Bold line: p30; light line: p60. Solid verticals: the moment a call names; dashed: when it was made.
sequencestreamTimeStypeconfidencedata
10session.status—ready
20session.status—calibrating
30input.warning—baseline_pending raised
432subject.identifiedhighwoman (pWoman 0.94), detectors onset_end
562session.status—analyzing
662input.warning—baseline_pending cleared
969542.6orgasm.onsethigh#1 at 538 s, called 4.6 s later, score 0.71
1046580.2orgasm.endhigh#1 at 575 s after 37 s, onset_end, called 5.2 s later
1205660session.status—ended, media_ended

man-peak

A man's orgasm: peak, then end: imminence and orgasm calls over 13 minutes00.510 min2 min4 min6 min8 min10 min12 minbaselinesubject: manpeakend
A man's orgasm: peak, then end. The face reads as a man’s, imminence climbs to a peak, which is called about three seconds after it happens; the end is then read from his face. Bold line: p30; light line: p60. Solid verticals: the moment a call names; dashed: when it was made.
sequencestreamTimeStypeconfidencedata
10session.status—ready
20session.status—calibrating
30input.warning—baseline_pending raised
431subject.identifiedhighman (pWoman 0.07), detectors peak, face_end
562session.status—analyzing
662input.warning—baseline_pending cleared
1293704.2orgasm.peakhigh#1 at 701 s, called 3.2 s later, score 0.66
1376745.5orgasm.endhigh#1 at 742 s after 41 s, face_end, called 3.5 s later
1445780session.status—ended, media_ended

undetermined

Subject undetermined: every detector runs: imminence and orgasm calls over 12 minutes00.510 min2 min4 min6 min8 min10 min12 minbaselinesubject: undeterminedonsetpeakend
Subject undetermined: every detector runs. The face read stays undetermined, so the onset-and-end detector and the peak detector both run, and their calls arrive with low confidence and a shared orgasm index. Bold line: p30; light line: p60. Solid verticals: the moment a call names; dashed: when it was made.

face-only

Face only: no microphone: imminence and orgasm calls over 10 minutes00.510 min2 min4 min6 min8 min10 minbaselinesubject: woman
Face only: no microphone. The device publishes the camera without the microphone: imminence and the subject read arrive, onset, peak and end cannot, and an audio warning says why. With no orgasm called, the approach that recedes counts as an edge. Bold line: p30; light line: p60. Solid verticals: the moment a call names; dashed: when it was made.

face-lost

Face lost for 20 seconds: imminence and orgasm calls over 12 minutes00.510 min2 min4 min6 min8 min10 minbaselinesubject: womanonsetend
Face lost for 20 seconds. The face leaves the frame at five minutes: imminence goes null, a warning is raised and the session is degraded until the face returns 20 seconds later. Bold line: p30; light line: p60. Solid verticals: the moment a call names; dashed: when it was made. Shaded: no face in view.
sequencestreamTimeStypeconfidencedata
10session.status—ready
20session.status—calibrating
30input.warning—baseline_pending raised
431subject.identifiedhighwoman (pWoman 0.89), detectors onset_end
562session.status—analyzing
662input.warning—baseline_pending cleared
483300input.warning—face_not_visible raised
484300session.status—analyzing, degraded
525320input.warning—face_not_visible cleared
526320session.status—analyzing
937524.8orgasm.onsethigh#1 at 520 s, called 4.8 s later, score 0.69
1012561.4orgasm.endhigh#1 at 556 s after 36 s, onset_end, called 5.4 s later
1289700session.status—ended, media_ended

edge

Edge: three approaches, no orgasm: imminence and orgasm calls over 15 minutes00.510 min2 min4 min6 min8 min10 min12 min14 minbaselinesubject: man
Edge: three approaches, no orgasm. Imminence rises past the hold and back-off levels three times and falls each time stimulation is backed off, and the session ends without an orgasm: three edges, each an edge.completed. Bold line: p30; light line: p60. Solid verticals: the moment a call names; dashed: when it was made.

Each approach ends in an edge.completed:

sequencestreamTimeStypeconfidencedata
10session.status—ready
20session.status—calibrating
30input.warning—baseline_pending raised
431subject.identifiedhighman (pWoman 0.05), detectors peak, face_end
562session.status—analyzing
662input.warning—baseline_pending cleared
706411edge.completedhighedge 1: p30 0.6 at 362 s, peak 0.687, below 0.3 49 s later
1067591edge.completedhighedge 2: p30 0.6 at 548 s, peak 0.669, below 0.3 43 s later
1468791edge.completedhighedge 3: p30 0.6 at 747 s, peak 0.684, below 0.3 44 s later
1686900session.status—ended, media_ended

ruin

Ruin: past the point of no return: imminence and orgasm calls over 13 minutes00.510 min2 min4 min6 min8 min10 min12 minbaselinesubject: manpeakend
Ruin: past the point of no return. Imminence crosses the stop level, stimulation is reported off for good, and the peak still comes a few seconds later: a ruined orgasm, whose end says so. Bold line: p30; light line: p60. Solid verticals: the moment a call names; dashed: when it was made.

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.

sequencestreamTimeStypeconfidencedata
10session.status—ready
20session.status—calibrating
30input.warning—baseline_pending raised
431subject.identifiedhighman (pWoman 0.08), detectors peak, face_end
562session.status—analyzing
662input.warning—baseline_pending cleared
1115615.3orgasm.peakhigh#1 at 612 s, called 3.3 s later, score 0.57
1172643.9orgasm.endhigh#1 at 640 s after 28 s, face_end, called 3.9 s later, ruined
1445780session.status—ended, media_ended

finish

Finish: two orgasms: imminence and orgasm calls over 12 minutes00.510 min2 min4 min6 min8 min10 min12 minbaselinesubject: womanonsetendonsetend
Finish: two orgasms. A build-up to an onset and an end, a second, shorter build-up, and a second onset and end, each with its own orgasm index. Bold line: p30; light line: p60. Solid verticals: the moment a call names; dashed: when it was made.

How the sandbox differs from live analysis

  • Free. Sandbox sessions count orgasms, ruins and edges as live ones do, in their charges and your test usage, and draw no credits: credits stays 0. Credits and billing says what each scenario counts.
  • No media. A sandbox session starts its scenario as soon as it is created. ingest.url answers 501 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 stimulationAware from 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 score and threshold values 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.

On this page