Usa Phone Harness con Sokko.

Create an account-wide API bearer key that can manage API keys. The raw key is shown only once; store it securely and never log it.

Start a temporary or saved Android emulator session and return its admitted session data plus the internally generated idempotency key. If the initial POST has an ambiguous transport failure, this action recovers or safely replays that same keyed request once. A provisioning result is not ready; poll PHONE_HARNESS_GET_SESSION until state is ready or terminal error.

Enable or re-enable ADB access for a ready Android session and return its current connection endpoint and sensitive unlock code. Repeated calls are idempotent.

Request that a Phone Harness session end and billing closure be recorded. A cleanup_pending result is asynchronous and continues to consume capacity; use the durable create receipt to confirm cleanup_complete. Repeating cleanup after the session is gone can return session_not_found; that outcome does not prove release or cleanup, even on a repeated call.

Get the connected account's identity, balance, Android profile choices, active-session capacity, and whether a new session can be started.

Get the current ADB state for an Android session. Returns exactly a disabled result or the enabled connection endpoint and sensitive unlock credential.

Check public Phone Harness API-process liveness only. This does not certify phone availability, credits, capacity, video, or successful provisioning.

Create a secret, short-lived capability for interactive owner control of a ready session. Embedding is restricted to the configured Phone Harness dashboard origin, not arbitrary third-party origins. Reconnecting does not extend the phone deadline. Return it only for secure handoff to the intended account owner; never log, persist, or publish it.

Return up to 100 finished sessions ordered by creation time descending. Use LIST_HISTORY instead when complete cursor-based traversal is needed.

Get one session's current lifecycle state, deadline, screen geometry, and ADB details. Use it to poll provisioning; state=error is a terminal startup failure, not success.

Download the latest still image from a ready Phone Harness session as a file. The image is PNG or JPEG. A no-frame-yet response is retryable after the session is ready and has rendered a frame.

Create a short-lived view-only link for an intended person to watch a live session. Return the link for secure handoff; it grants no interactive owner control and must not be logged or published.

List metadata for the connected account's API keys, including hashes, labels, hints, creation times, and revocation times. This action never returns raw bearer keys.

Return one cursor-paginated page of finished-session history in newest-first order, with a next cursor for complete traversal.

List all active account sessions, including provisioning, terminal-error, closing, and cleanup-pending entries.

Read the durable receipt for an idempotent session create to resolve an ambiguous create result or confirm asynchronous release cleanup.

Rotate the ADB unlock code for an Android session, invalidate the previous code, and close all existing ADB connections. Returns sensitive replacement connection details that must be used for subsequent connections.

Irreversibly erase and reprovision an assigned iPhone, deleting its apps, accounts, and data. The reset takes a few minutes; poll PHONE_HARNESS_GET_ACCOUNT until the device state is available before starting it again. Phone Harness refuses the reset while a session holds the device.

Irreversibly delete the saved Android profile's apps, logins, and data. The next session using its profile ID starts with a fresh phone. Phone Harness refuses the reset while a live session holds the profile phone.

Revoke ADB access for an Android session. This changes only ADB access: the phone session remains active and session billing continues unaffected.

Idempotently revoke an API key by its hash. Identifier existence is not proven by a successful response, and active phone sessions are unaffected. Do not revoke the key used by the current connection if continued Phone Harness access is needed.