# Overview (https://orgasm.dev/docs)

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 [#what-you-get-back]

| Event | What it says | Needs |
| --- | --- | --- |
| `imminence.updated` | The probability that orgasm begins within 30 and within 60 seconds, about once a second | Face |
| `signals.updated` | Vocalizations, loudness, contractions, movement and how each region of the face has moved, about once a second, for a display | Each field its own input |
| `orgasm.onset` | A woman's orgasm began | Face and microphone |
| `orgasm.peak` | A man's orgasm peaked | Face and microphone |
| `orgasm.end` | The orgasm ended | Face, and the microphone for women |
| `subject.identified` | Whether the face reads as a woman's or a man's, which decides the detectors | Face |

Every signal carries `confidence`, which says how complete the input behind it was. [Signals](/docs/concepts/signals) explains each one, including what it is not.

## Two ways in [#two-ways-in]

<Cards>
  <Card title="Live sessions" href="/docs/guides/live-sessions">
    `POST /v1/live-sessions`. The person's device publishes its camera and microphone over WHIP; events arrive within seconds over server-sent events, a WebSocket or webhooks.
  </Card>
  <Card title="Recordings" href="/docs/guides/recordings">
    `POST /v1/recordings`. Upload a video or give a URL; the same events come back as a timeline once it is processed.
  </Card>
</Cards>

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 [#the-shape-of-a-session]

```mermaid
sequenceDiagram
  participant App as Your server
  participant API as orgasm.dev
  participant Device as The person's device
  participant Enclave as Enclave
  App->>API: POST /v1/live-sessions (secret key, consent, capability hash)
  API-->>App: ingest, results.clientToken
  App->>Device: ingest, client token
  Device->>Enclave: verify attestation, then publish camera + microphone (WHIP)
  Enclave-->>API: numbers only
  API-->>App: imminence.updated, subject.identified, orgasm.onset / peak / end
  App->>API: DELETE /v1/live-sessions/{id}
```

## Where things stand [#where-things-stand]

The sandbox is open. Any key that starts with `sk_test_` reaches it; it plays [deterministic scenarios](/docs/guides/sandbox) 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](/signup), run [live sessions](/docs/guides/live-sessions) on attested enclaves: the end user's device publishes its front camera and microphone straight to one ([trust](/docs/concepts/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 [#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](/docs/concepts/compliance) before you build, and [trust](/docs/concepts/trust) for what the enclave does and does not guarantee.

## Next [#next]

- [Quickstart](/docs/quickstart): a sandbox session in five minutes.
- [For AI agents](/docs/agents): the prompt, the MCP servers and the machine-readable contracts.
- [REST reference](/reference): every operation, with a sandbox key filled in.
