Execute JavaScript in the device's Chrome browser (CDP)
Evaluates a JavaScript expression exactly once in the device’s single, confirmed foreground Chrome tab via the Chrome DevTools Protocol and returns its JSON-serialized result. A responsive browser state without exactly one visible page returns DEVICE_NO_BROWSER_TARGET (400). Transient discovery, page-dial, or visibility-probe transport failures return CDP_TRANSPORT_UNAVAILABLE (503) with Retry-After and an executionOutcome; the service may start Chrome once and retry selection before Runtime.evaluate, but dial or probe recovery is skipped for a backgrounded Chrome, and a user script is never retried after its write or read. Devices without browser support return an unsupported-feature error.
return and wrap multi-statement logic in an IIFE:
undefined comes back as null, and NaN, Infinity, and -0 are returned as strings. Scripts run in Chrome itself — in-app WebViews are not reachable. iOS devices don’t support browser control and fail with 400.
If CDP discovery, page connection, or the foreground visibility probe fails before Runtime.evaluate is sent, the service may start Chrome once and retry target selection. Dial and probe recovery only starts Chrome when it is already the foreground app (or the Chrome CDP socket itself is unavailable), so a backgrounded browser still fails closed. The response keeps the CDP_TRANSPORT_UNAVAILABLE 503 contract and reports the phase and recovery result in its details when recovery was attempted. A selection deadline shortfall, or failures while writing or reading Runtime.evaluate, is never replayed.
Body
JavaScript expression to evaluate in the device's foreground Chrome tab (CDP Runtime.evaluate). It is an expression, not a function body — the expression's value is returned (no top-level 'return'). Must evaluate to a JSON-serializable value; wrap multi-statement logic in an IIFE, e.g. (() => { ... ; return x })().
Response
OK