Skip to main content
POST
Error

Authorizations

Authorization
string
header
required

The control surface credential. Send Authorization: Bearer <token>.

Two kinds of token are accepted and they are told apart by shape, not by a separate header. A token beginning pbk_ or puk_ is an org scoped API key, whose public half and secret half are generated together and of which only a hash of the secret is ever stored; anything else is treated as an OAuth 2.1 access token and verified against the authorization server's keys.

Both resolve to the same context: an org, a principal and a set of scopes. Nothing downstream branches on which channel you used, with one deliberate exception, key management, which requires a signed-in person so that a key can never mint another key.

Scopes are enforced when MCP tools are REGISTERED rather than when they are called, so a tool your credential cannot use is absent from tools/list rather than refused mid gesture.

Path Parameters

deviceId
string
required

The phone.

Body

application/json

The unclear actions you were shown.

refs
string[]
required

The ref of each unclear action you looked at, 1 to 50.

Required array length: 1 - 50 elements
Pattern: ^[0-9a-f]{64}$

Response

How many were newly confirmed, what is still unclear and whether agent tasks may use the phone now.

confirmed
integer
required

Actions this call confirmed. 0 when there was nothing left to confirm.

items
object[]
required

What is still unclear on this phone, in the shape the list returns.

agentReady
boolean
required

True when nothing on this phone keeps agent tasks waiting.

inProgress
boolean
required

True while an action of yours on this phone is still under way.