A valid request URL is required to generate request examples{
"confirmed": 123,
"items": [
{}
],
"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": "payload_too_large",
"message": "<string>"
}
}{
"error": {
"code": "rate_limited",
"message": "<string>"
}
}{
"error": {
"code": "backend_resolution_failed",
"message": "<string>",
"retryable": true
}
}Confirm a phone looks right
A person looked at the phone and says it looks right after exactly the unclear actions they were shown, named by ref. Those actions stop keeping agent tasks waiting; the receipts themselves do not change. An agent task whose own action is confirmed takes a new screenshot before its next action.
UNLIKE marking a receipt reviewed, THIS IS A SIGN-OFF, so it needs a signed in person and devices:act. References that are not unclear actions you may confirm on this phone now (already confirmed, another phone, a robot hand, an install, an action still inside its 30 second wait) are ignored rather than refused, so answering a list another tab already confirmed is harmless. The answer says how many were newly confirmed, what is still unclear (with retryAfterMs on any still waiting) and whether agent tasks may use the phone now.
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{
"confirmed": 123,
"items": [
{}
],
"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": "payload_too_large",
"message": "<string>"
}
}{
"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.
Body
The unclear actions you were shown.
Response
How many were newly confirmed, what is still unclear and whether agent tasks may use the phone now.