A valid request URL is required to generate request examples{
"items": [
{
"ref": "<string>",
"action": "<string>",
"requestedAt": "<string>",
"failedAt": "<string>",
"viaCopilot": true,
"earlierHolder": true,
"agentRunId": "<string>",
"retryAfterMs": 2
}
],
"agentReady": true,
"inProgress": true
}{
"error": {
"code": "backend_resolution_failed",
"message": "<string>",
"retryable": true
}
}{
"error": {
"code": "unauthorized",
"reason": "missing_credentials",
"hint": "<string>"
}
}{
"error": {
"code": "backend_resolution_failed",
"message": "<string>",
"retryable": true
}
}{
"error": {
"code": "backend_resolution_failed",
"message": "<string>",
"retryable": true
}
}{
"error": {
"code": "rate_limited",
"message": "<string>"
}
}{
"error": {
"code": "backend_resolution_failed",
"message": "<string>",
"retryable": true
}
}List a phone's unclear actions
The ordinary actions on a cloud phone your organization holds whose result could not be confirmed: taps, swipes, typing, keys, opening an app, rotating and waking. An agent task’s own action is listed once that task has stopped acting, with agentRunId naming it. Oldest first, at most 50, including any left by an organization that held the phone before (shown without its key, kind, times or run).
An action a signed-in person did not make directly (an agent task’s, Copilot’s, an API key’s or any other caller that is not a person) can be confirmed only 30 seconds after it ended, so a late result has time to show on the screen first; until then retryAfterMs says how long is left. A person’s own has no wait.
People can keep using the phone meanwhile. Until a person confirms it looks right, no agent task can start or act on the phone and giving it back in the background is refused. agentReady says whether agent tasks may use it now, and inProgress whether one of your actions is still under way, which also keeps them waiting briefly. A robot hand, a real device, an app install and an action still in progress are never listed: they keep their own paths.
Hosted deployments only. A local checkout does not mount this route, so calling it there is a 404.
A valid request URL is required to generate request examples{
"items": [
{
"ref": "<string>",
"action": "<string>",
"requestedAt": "<string>",
"failedAt": "<string>",
"viaCopilot": true,
"earlierHolder": true,
"agentRunId": "<string>",
"retryAfterMs": 2
}
],
"agentReady": true,
"inProgress": true
}{
"error": {
"code": "backend_resolution_failed",
"message": "<string>",
"retryable": true
}
}{
"error": {
"code": "unauthorized",
"reason": "missing_credentials",
"hint": "<string>"
}
}{
"error": {
"code": "backend_resolution_failed",
"message": "<string>",
"retryable": true
}
}{
"error": {
"code": "backend_resolution_failed",
"message": "<string>",
"retryable": true
}
}{
"error": {
"code": "rate_limited",
"message": "<string>"
}
}{
"error": {
"code": "backend_resolution_failed",
"message": "<string>",
"retryable": true
}
}Authorizations
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.
Response
The unclear actions a person may confirm, and whether agent tasks may use the phone now.