# orgasm.dev

> Know when your users orgasm, with live updates as they get close: the orgasm API for games, sex toys, AI companions, creators and adult entertainment. Live camera streams and recorded videos go in as two separate endpoints; events about imminence, onset, peak and end come back over server-sent events, a WebSocket, webhooks and event lists. The sandbox is open to any key that starts with `sk_test_`, with no account; live sessions take a `sk_live_` key from the developer's dashboard, after signing up at https://orgasm.dev/signup, and recorded videos are analysed in the sandbox only for now.

Everything an agent needs to integrate, in machine-readable form:

- OpenAPI 3.1 (REST): https://orgasm.dev/openapi.json
- AsyncAPI 3.1 (events): https://orgasm.dev/asyncapi.json
- Action MCP server (tools that call the API with your key): https://orgasm.dev/mcp
- Docs MCP server (list, search and read these docs): https://orgasm.dev/api/mcp
- Every page as Markdown: append `.md` to a docs URL, or send `Accept: text/markdown`
- API catalog (RFC 9727): https://orgasm.dev/.well-known/api-catalog

## Docs
- [Overview](https://orgasm.dev/docs): What orgasm.dev measures, how it reaches your product, and what it asks of you.
- [Quickstart](https://orgasm.dev/docs/quickstart): A sandbox live session in five minutes, followed by its events, with curl and with TypeScript.
- [For AI agents](https://orgasm.dev/docs/agents): The prompt to give your coding agent, how to connect Cursor, Claude Code or Codex to the two MCP servers, and every machine-readable surface of orgasm.dev.
- [Credits and billing](https://orgasm.dev/docs/credits): What live sessions are charged for and how each charge is counted, where charges show up, what happens at zero, what each of your users and sessions cost, reconciling with your invoices, and testing it in the sandbox.

### Concepts

- [Signals](https://orgasm.dev/docs/concepts/signals): What imminence, onset, peak, end, edges, the display signals and the subject read mean, how sure each is, and what none of them are.
- [Inputs](https://orgasm.dev/docs/concepts/inputs): The face is the minimum.
- [Subject](https://orgasm.dev/docs/concepts/subject): How orgasm.dev decides whether the face reads as a woman's or a man's, why that decides the detectors, and how to treat the read.
- [Timing](https://orgasm.dev/docs/concepts/timing): The two clocks, why calls arrive late, ordering and deduplication, and how to act on signals without flapping.
- [Edge, ruin and finish](https://orgasm.dev/docs/concepts/presets): Three experiences as policies your product runs on the signals, with reference code, the cues each gives on the sandbox scenarios, and the safety they need.
- [Trust](https://orgasm.dev/docs/concepts/trust): Where the video goes, what the enclave guarantees, which code you can read, what the device verifies, and where the guarantee stops.
- [Acceptable use](https://orgasm.dev/docs/concepts/compliance): Adults only, consent first, never covertly.

### Guides

- [Live sessions](https://orgasm.dev/docs/guides/live-sessions): A live camera stream end to end, from the capability on the device to the final status.
- [Camera and microphone](https://orgasm.dev/docs/guides/capture): Ask for the camera and microphone after explaining why, from a click, with every refusal named along with what to do about it.
- [Recordings](https://orgasm.dev/docs/guides/recordings): Submit a recorded video by upload or by URL, follow its processing, and read its result and timeline.
- [Realtime](https://orgasm.dev/docs/guides/realtime): The event stream and subscribe, the WebSocket and stimulation reports, face frames, view tokens for other screens, long polling, how to resume after a drop, and which to choose.
- [Show the HUD](https://orgasm.dev/docs/guides/hud): A heads-up display of the session for your users, as a siderail, a bottom bar, a card in a game or the whole panel with the face and the timeline, or drawn natively from the same model.
- [Webhooks](https://orgasm.dev/docs/guides/webhooks): Receive events as signed POSTs, verify them, and handle retries and duplicates.
- [Verify the enclave](https://orgasm.dev/docs/guides/verify): Read the enclave's source, check a release's SLSA provenance and signature, and check that the machine a live session runs on is that release, without taking orgasm.dev's word for any of it.
- [Your own GPUs](https://orgasm.dev/docs/guides/own-gpus): Run the same signed enclave on your own Google Cloud GPUs, inside your VPC, and lease it through the orgasm.dev API, so media is decrypted only in your project.
- [Teams and roles](https://orgasm.dev/docs/guides/teams): Your company's people on orgasm.dev, as Admins, Developers and Billing members.
- [Errors](https://orgasm.dev/docs/guides/errors): Problem details, every error code and what to do about it, retries and idempotency.
- [Sandbox](https://orgasm.dev/docs/guides/sandbox): The deterministic scenarios behind test keys, how to choose and speed them up, and how the sandbox differs from live analysis.

### REST API

### Live sessions

- [List live sessions](https://orgasm.dev/docs/api/live-sessions/listLiveSessions): Lists your company's live sessions, newest first.
- [Create a live session](https://orgasm.dev/docs/api/live-sessions/createLiveSession): Starts analysis capacity for one person's live camera stream and returns where their device publishes (`ingest`) and where events arrive (`results`).
- [Purge a person's live sessions](https://orgasm.dev/docs/api/live-sessions/purgeLiveSessionsByUserReference): Purges every live session created with this `userReference`, as `purgeLiveSession` does one: each is ended if it is still running, then deleted with all its events.
- [Get a live session](https://orgasm.dev/docs/api/live-sessions/getLiveSession): Returns the session's status, which inputs are arriving, the subject read once it is made, and the latest imminence (`latestImminence`).
- [End a live session](https://orgasm.dev/docs/api/live-sessions/endLiveSession): Ends the session now: the device's connection is closed, a final `session.status` with `endedReason: client_ended` is emitted, and the analysis capacity is released.
- [Purge a live session](https://orgasm.dev/docs/api/live-sessions/purgeLiveSession): Ends the session if it is still running, then deletes it and all its events now rather than at `resultsExpireAt`, and erases its `userReference`, `clientReferenceId` and metadata from your company's charges, which stay, unattributed.
- [List a live session's events](https://orgasm.dev/docs/api/live-sessions/listLiveSessionEvents): Returns the session's events in order, oldest first.
- [Stream a live session's events](https://orgasm.dev/docs/api/live-sessions/streamLiveSessionEvents): A server-sent events stream of the session's events.
- [Create a view token](https://orgasm.dev/docs/api/live-sessions/createViewToken): A read-only token for one session's events, for a screen other than the person's device: a heads-up display drawn into a stream, a coach's view, a second monitor.
- [Report stimulation](https://orgasm.dev/docs/api/live-sessions/reportStimulation): Tells the analysis when stimulation starts, stops or changes, if your product controls it (a device, an e-stim unit, a scene).

### Recordings

- [List recordings](https://orgasm.dev/docs/api/recordings/listRecordings): Lists your company's recordings, newest first.
- [Submit a recording](https://orgasm.dev/docs/api/recordings/submitRecording): Submits a recorded video for analysis.
- [Get a recording](https://orgasm.dev/docs/api/recordings/getRecording): Returns the recording's status and progress and, once `completed`, its `result`: the subject read, a summary of each orgasm, and the timeline of discrete events.
- [Delete a recording](https://orgasm.dev/docs/api/recordings/deleteRecording): Deletes the recording's results and events now and stops processing if it is still running.
- [List a recording's events](https://orgasm.dev/docs/api/recordings/listRecordingEvents): Returns the recording's full event timeline in order, including `imminence.updated` for every second of analysed face.

### Webhooks

- [List webhook endpoints](https://orgasm.dev/docs/api/webhooks/listWebhookEndpoints): Lists your company's webhook endpoints for the key's mode, newest first, without their secrets.
- [Create a webhook endpoint](https://orgasm.dev/docs/api/webhooks/createWebhookEndpoint): Registers an HTTPS URL on your server to receive events as POSTs, signed per the Standard Webhooks specification (`webhook-id`, `webhook-timestamp`, `webhook-signature`).
- [Get a webhook endpoint](https://orgasm.dev/docs/api/webhooks/getWebhookEndpoint): Returns one webhook endpoint and the event types it receives, without its secret.
- [Update a webhook endpoint](https://orgasm.dev/docs/api/webhooks/updateWebhookEndpoint): Changes an endpoint's URL, the event types it receives, its description, or whether it is enabled.
- [Delete a webhook endpoint](https://orgasm.dev/docs/api/webhooks/deleteWebhookEndpoint): Stops all deliveries to the endpoint, including retries in flight.
- [Roll a webhook endpoint's secret](https://orgasm.dev/docs/api/webhooks/rollWebhookSecret): Replaces the endpoint's signing secret and returns the new one, once.
- [Send a test webhook](https://orgasm.dev/docs/api/webhooks/sendTestWebhook): Sends one signed sample event of the given type to the endpoint now and reports how your server answered.

### Account

- [Get usage](https://orgasm.dev/docs/api/account/getUsage): Your company's live-session and recording minutes per day for the key's mode, and the orgasms, ruins, edges and session minimums counted, with the credits they drew (always 0 in test mode).
- [Get credits](https://orgasm.dev/docs/api/account/getCredits): Your company's credit balance: what is available, what is left of the 20 free credits, and each package with its price per credit, what it has left and when it expires.
- [List charges](https://orgasm.dev/docs/api/account/listCharges): Every orgasm, ruin, edge and session minimum your company's live sessions were charged for, newest first, with what each cost in US dollars and the session's `userReference`, `clientReferenceId`, metadata and key, so that you can break your costs down by person, by your own session or by any metadata value.
- [List models](https://orgasm.dev/docs/api/account/listModels): The models behind each signal: what each produces, which inputs it needs, who it applies to, and where it is available.
- [List API keys](https://orgasm.dev/docs/api/account/listApiKeys): Lists your company's API keys, newest first, with only their prefix and last four characters, who made each, and when a rolled key stops working.
- [Create an API key](https://orgasm.dev/docs/api/account/createApiKey): Creates a key for your company.
- [Roll an API key](https://orgasm.dev/docs/api/account/rollApiKey): Makes a replacement for a key, with the same name, mode and type, and returns its secret once.
- [Delete an API key](https://orgasm.dev/docs/api/account/deleteApiKey): Revokes the key immediately.

### Trust

- [Get the attestation policy](https://orgasm.dev/docs/api/trust/getAttestationPolicy): What a device must check in an enclave's attestation before it publishes media: the token issuer, the confidential-computing hardware, the enclave image's source and minimum release, and the sealing scheme.

### Sandbox

- [Upload a sandbox recording](https://orgasm.dev/docs/api/sandbox/uploadSandboxRecording): The target of `uploads.face.url` and `uploads.body.url` in test mode.

### Events

- [Stream a live session's events](https://orgasm.dev/docs/events/streamLiveSessionEvents): Open the stream once the session is created; it carries every event of the session, in `sequence` order, until its final `session.status`.
- [Receive events on the socket](https://orgasm.dev/docs/events/sendSocketEvents): The same events as the stream, one JSON text frame each, in `sequence` order, and a `socket.error` frame when a client message is refused.
- [Send messages on the socket](https://orgasm.dev/docs/events/receiveSocketMessages): `stimulation` is the socket form of `POST /v1/live-sessions/{sessionId}/stimulation`.
- [Receive webhooks](https://orgasm.dev/docs/events/deliverWebhooks): Register endpoints with `POST /v1/webhook-endpoints`, choosing the event types each receives.

## Pricing

[Pricing](https://orgasm.dev/pricing): prepaid credits for companies; the sandbox (any `sk_test_` key) is free. Every company domain starts with 20 free credits, shared by its team of Admins, Developers and Billing members ([Teams and roles](https://orgasm.dev/docs/guides/teams)).

- Orgasm: 1 credit. Each orgasm the detectors call, once, however many of its onset, peak and end you receive.
- Ruin: 1 credit. An orgasm that began within 30 seconds of your product stopping stimulation at the point of no return.
- Edge: ½ credit. Imminence reached 0.6 and fell back below 0.3 with no orgasm called in between.
- A session with none of them: ½ credit. A live session with more than a minute of media that counted no orgasm, ruin or edge.

Packages: Pilot 500 credits for $3,000 ($6.00 a credit); Launch 2,500 credits for $12,500 ($5.00 a credit); Growth 10,000 credits for $40,000 ($4.00 a credit); Scale 50,000 credits for $162,500 ($3.25 a credit); Enterprise from 200,000 credits, in the SOW, from $2.75 a credit. Bought by MSA and SOW, invoiced payable on receipt, from sales@orgasm.dev. [Credits and billing](https://orgasm.dev/docs/credits) says how each is counted and where charges show up. To see what each of your users and sessions cost, pass `userReference` (your pseudonymous id for the person, never an email) and `clientReferenceId` when you create a live session, and read `listCharges` ([cost attribution](https://orgasm.dev/docs/credits#cost-attribution)).

## Industries

Case studies: how each industry turns the signals and the presets into its product.

- [Game developers](https://orgasm.dev/industries/games): Difficulty, power-ups and unlocks that follow how close the player is and how many orgasms they have had.
- [Sex toy manufacturers](https://orgasm.dev/industries/toys): The toy builds while the person is far off, backs off at the edge and carries them through, on rules they chose.
- [Adult entertainment](https://orgasm.dev/industries/adult): Interactive and generative scenes that build, hold and resolve with the viewer, from the viewer’s own camera.
- [AI chatbots](https://orgasm.dev/industries/chatbots): Voice and video companions that pace the conversation to the user and know when it is time for aftercare.

## Optional

- [llms-full.txt](https://orgasm.dev/llms-full.txt): every guide, the REST reference and the events reference in one file
- [API reference](https://orgasm.dev/reference): interactive, with a sandbox key filled in
- [MCP manifest](https://orgasm.dev/.well-known/mcp.json): both MCP servers and their tools
- [The enclave's source](https://github.com/Masseuse-ai/masseuse-video-tee): the image every live session is analysed in, its release workflow and its verifier (Apache-2.0)
- [The device SDK's source](https://github.com/Orgasm-dev/device-sdk): what the person's device runs, `@orgasm-dev/device` (Apache-2.0)
- [Privacy Policy](https://orgasm.dev/privacy): what orgasm.dev keeps about developers and the people on camera, for how long, and who receives it
