boxLink
shallowdev.arcgate/arcgate · Verify this server
Links the box to an account, so the box's watch hits draw the account's units and its limits are the account's tier's. A box belongs to at most one account. - **Cost:** Free. Signed by the box over method `POST`, path `/agent/v1/<address lowercased>/box/link` and the body `{"accountId": ...}`, and authorized by the account: its key in `ARCGATE-KEY`, or the owner's `AccountRequest` over the same method, path and body in `ACCOUNT-SIGNATURE`, `ACCOUNT-NONCE` and `ACCOUNT-EXPIRY`. The box's signature alone is a 401 `signature_required`. - **Inputs:** `address` (path), the box, and `accountId` (body). - **Returns:** `address`, `accountId`, `linkedAt` and `keyId`, the id of the key that made the link, or null when the owner's signature did. A link made with a key sends a notice to the owner's box. - **Errors:** - 404 `box_not_found`: the address has no box. Create one with `boxCreate`. - 404 `account_not_found`: no account has that id. - 403 `key_wrong_account`: the key belongs to another account than `accountId`. - 409 `box_linked`: the box belongs to an account already. Unlink it first with `boxUnlink`. - 409 `account_lapsed`: the account has lapsed (its grace has ended), so no box can be linked to it. - 409 `box_limit`: the account holds as many boxes as its tier allows, or as the tier it has a downgrade scheduled to (`accountTier`), which the message names and the body carries as `scheduledTier`. Unlink one first. - 409 `watch_limit`: while the account has a downgrade scheduled (`accountTier`), the box holds more watches, screens or agent screens than the scheduled tier allows; the message names it and the body carries `scheduledTier`. Delete what is over, then link. - **Next:** - `accountStatus`: read the account's linked boxes. - `boxStatus`: read the box's `linkedAccount`. - `boxUnlink`: end the link.
1 trials · measured 33 days ago
boxLink scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against dev.arcgate/arcgate, measured 20 Oct 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- self-provisionable
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-10-20 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/d3f3b607-9e1b-4777-84df-b689ef57fdbf)