orgasm.dev

Overview

What orgasm.dev measures, how it reaches your product, and what it asks of you.

orgasm.dev turns the front camera of a consenting adult, live or recorded, into events about their orgasm. Your app, device, game or scene reacts to those events: to hold someone at the edge, to ruin an orgasm at the point of no return, or to carry it through.

What you get back

EventWhat it saysNeeds
imminence.updatedThe probability that orgasm begins within 30 and within 60 seconds, about once a secondFace
signals.updatedVocalizations, loudness, contractions, movement and how each region of the face has moved, about once a second, for a displayEach field its own input
orgasm.onsetA woman's orgasm beganFace and microphone
orgasm.peakA man's orgasm peakedFace and microphone
orgasm.endThe orgasm endedFace, and the microphone for women
subject.identifiedWhether the face reads as a woman's or a man's, which decides the detectorsFace

Every signal carries confidence, which says how complete the input behind it was. Signals explains each one, including what it is not.

Two ways in

You never have to say whether the person is a woman or a man: the face is read, and the detectors that apply follow. You may say so with subjectHint when the person told you.

The shape of a session

Where things stand

The sandbox is open. Any key that starts with sk_test_ reaches it; it plays deterministic scenarios through the same contract, so you can build and test an integration end to end today. Keys that start with sk_live_, from your dashboard once you sign up, run live sessions on attested enclaves: the end user's device publishes its front camera and microphone straight to one (trust). Recorded videos are analysed in the sandbox only for now: with a live key, createRecording answers live_mode_unavailable.

What we ask of you

Everyone on camera is a verified adult who agreed to the analysis and can stop it at any time; every request that starts an analysis says so in consent. Read acceptable use before you build, and trust for what the enclave does and does not guarantee.

Next

  • Quickstart: a sandbox session in five minutes.
  • For AI agents: the prompt, the MCP servers and the machine-readable contracts.
  • REST reference: every operation, with a sandbox key filled in.

On this page