Claim a consumer runner pairing
claim_runner_pairingClaims a short-lived pairing ID and binds it to one SignalR block for integration testing or manual pairing, enabling secure runner device setup.
Instructions
Claims a short-lived pairingId created by a generic consumer runner and binds it to one SignalR block. Use this for integration testing or an explicitly requested manual pairing. In production the application's authenticated BACKEND must call the same Management API route after mapping its own user to the device; never put the Management credential in browser code. The pairingId expires and is single-claim.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"signalRBlockId": "<signalRBlockId>",
"pairingId": "<pairingId>"
},
"name": "claim_runner_pairing"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | User-facing computer name. | |
| confirm | No | Must be true because this creates a durable runner device. | |
| pairingId | Yes | Opaque pairing id received by the application's HTTPS handoff page. | |
| signalRBlockId | Yes | The SignalR block guid (signalRGuid). |