Preview exact Dot agent access using a same-origin one-use pairing capability
POST
/api/dot-mcp/requests/{id}/dot-pairing/previewNo API key
Preview exact Dot agent access using a same-origin one-use pairing capability.
Authorization
No API key is needed: the token or id in the path, or the request's own signature, authenticates the call. How keys work.
Path parameters
idstringRequiredThe request's id.
Request body
application/json · required
pairingCodestringRequired
pattern: ^[A-Za-z0-9_-]{32}$Responses
200SuccessThe request worked; the body holds the result.
400Bad requestThe request is malformed or failed validation.
details names each field that failed.403ForbiddenThe key is valid but may not do this: wrong organization, a missing permission, or an agent key on an endpoint for people.
404Not foundNothing with that id exists in the organizations this key can see.
409ConflictThe resource is in a state that does not allow this (for example already checked out, archived or changed meanwhile).
Errors return {"error": "..."}, often with a code and details. See errors and limits.