@deepdockai/cli 1.0.11 → 1.0.12

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 1.0.12
+
+- The agent skill describes `rate_limited` for action calls: 600 calls and 120 writes per minute per API key, answered with `Retry-After: 60` and `retryAfterSeconds: 60`. It named only the pairing limit before.
+
 ## 1.0.11
 
 - Every system of a device carries `accessLastCheckedAt`, in the device list and in `GET /v1/devices/{deviceId}/systems`. It is set when `access` is the last known value because the device could not read it (its database stopped or unreachable), and then says when the device last read it. It is `null` whenever the latest report read the access. The agent skill's TypeScript client types it, and its concepts reference explains it.

package/dist/deepdock.js

@@ -11428,7 +11428,7 @@ import { spawn } from "node:child_process";
 import { homedir, hostname } from "node:os";
 
 // src/version.ts
-var VERSION = "1.0.11";
+var VERSION = "1.0.12";
 
 // src/runtime.ts
 var DEFAULT_BASE_URL = "https://api.deepdock.ai";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deepdockai/cli",
-  "version": "1.0.11",
+  "version": "1.0.12",
   "description": "Deepdock partner CLI: pair devices, see systems and actions, create the API key your code runs them with.",
   "type": "module",
   "license": "MIT",

package/skill/references/calling-actions.md

@@ -98,9 +98,12 @@ Never invent an id, copy one from another device, or hard-code one from a test r
 
 ## Rate limits
 
-The only documented limit is on pairing: 5 failed claim attempts per key per rolling 60 seconds
-(`429 rate_limited`). Handle `429` generically anyway (honour `Retry-After` when present, back off,
-do not loop), since limits can be added additively.
+Each API key has its own budget on every `/v1` call: 600 calls per minute, and 120 writes per
+minute. A write (an action run that needs an `Idempotency-Key`) counts against both. Over a budget
+the call answers `429 rate_limited` with `Retry-After: 60` and `retryAfterSeconds: 60` in the error
+body. Honour it, back off and do not loop; a retried write keeps its `Idempotency-Key`. The numbers
+can change, so treat them as approximate. Pairing has a tighter limit of its own: 5 failed claim
+attempts per key per rolling 60 seconds, whose `429` carries neither the header nor the field.
 
 ## Response headers worth reading
 

package/skill/references/errors.md

@@ -17,7 +17,7 @@ with the **same** `Idempotency-Key`); **Show** says what the end user should see
 | `payload_too_large` | 413 | the request body is over 1 MiB | no; send less | nothing; a developer bug, or shorten the text |
 | `unauthenticated` | 401 | the key is missing, malformed, for the other environment, unknown, revoked or expired | no | "Deepdock API key refused; check it in the dashboard" to an operator |
 | `not_found` | 404 | no such route; an update whose id matches no record; a write naming a record that does not exist or belongs to another one | no | "record not found" when it is a record; otherwise a bug |
-| `rate_limited` | 429 | too many failed pairing attempts with this key (5 per 60 s) | yes, after up to a minute (`Retry-After` when present) | "try again in a minute" |
+| `rate_limited` | 429 | more than 600 calls, or more than 120 writes (counted in both), with this key in a minute; or more than 5 failed pairing claims in 60 s | yes, after `Retry-After: 60` (`retryAfterSeconds: 60` in the body); a write keeps its key. The pairing claim answer has neither: wait up to a minute | "try again in a minute" |
 
 Codes your `/v1` code never receives, listed so the enum is complete: `organization_required`
 (403), `forbidden` (403), `conflict` (409), `already_member` (409) and `client_outdated` (400) are