A valid request URL is required to generate request examples{
"found": false,
"kind": "order",
"requestId": "<string>"
}{
"error": {
"code": "rate_limited",
"message": "<string>"
}
}/v1/minute/requests/:requestId
Observe an existing committed original request without creating an account/intent, settling fees, dispatching work or invoking provider recovery. First-party OAuth administrator, devices:read, original organization and actor required. Supply only original kind/body fields: order quoteId+quantity; cancel orderId; return deviceId+expectedEpoch+expectedImpactVersion+expectedIncarnation; resume deviceId+expectedEpoch+quoteId+expectedIncarnation; topup quoteId with optional paired returnQuoteId+returnQuantity. Missing committed receipt returns found:false and does not prove an in-flight POST had no effects; changed identity is 409. Original return/resume binding is separate from the device’s current allocation. Historical rental receipts grant no new action authority; order cancellation eligibility retains its current unit-state fact and scope gate.
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{
"found": false,
"kind": "order",
"requestId": "<string>"
}{
"error": {
"code": "rate_limited",
"message": "<string>"
}
}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.