@1claw/openapi-spec 0.61.22 → 0.61.23

package/openapi.json

@@ -2,7 +2,7 @@
   "openapi": "3.1.0",
   "info": {
     "title": "1Claw API",
-    "version": "0.61.22",
+    "version": "0.61.23",
     "description": "Secure secret management for AI agents. Provides vaults, secrets,\npolicy-based access control, agent identity, Intents API,\nsharing, billing, and audit logging. Automations (workflow_spec,\nwebhook tokens, event triggers, Assist), cloud runtimes with\ninteractive shell sessions, agent memory, and discovery.\n\n## Domains\n\n`api.1claw.co` is canonical: it is the OIDC issuer, the `aud` the API\nmints, and the first entry in `servers` — a generated client takes its\nbase URL from there, and the previous ordering pointed every SDK at the\ndomain the issuer had already left. `api.1claw.xyz` still answers and is\nstill accepted on token validation, because tokens minted before the\nmove carry it; it is never minted now.\n\nOne deliberate exception: the Shroud attestation identity token is\nrequested from GCP with `audience: https://api.1claw.xyz`, so\n`/v1/shroud/attestation` reports that as its `expected_audience`. That\nis accurate rather than stale — the audience is a verification contract\nwith anyone already checking the token, and moving it is a breaking\nchange for them, not a rename.\n\nAll endpoints require JWT Bearer authentication unless marked with\n`security: []`.\n",
     "contact": {
       "email": "ops@1claw.co"
@@ -36339,6 +36339,10 @@
               "client_tss"
             ],
             "description": "`server` — 1claw holds the whole private key and can sign alone.\n`client_tss` — 2-party threshold key; the customer's passkey share is required.\n"
+          },
+          "owner_wraps": {
+            "type": "integer",
+            "description": "`client_tss` only (list responses). Wraps of the customer's share under\ntheir own credentials — passkey PRF or recovery code; runtime holder\nwraps are not counted. Below 2 the wallet should not be funded: one\nlost credential would lose the share.\n"
           }
         }
       },

package/openapi.yaml

@@ -2,7 +2,7 @@ openapi: 3.1.0
 
 info:
     title: 1Claw API
-    version: "0.61.22"
+    version: "0.61.23"
     description: |
         Secure secret management for AI agents. Provides vaults, secrets,
         policy-based access control, agent identity, Intents API,
@@ -23610,6 +23610,13 @@ components:
                     description: |
                         `server` — 1claw holds the whole private key and can sign alone.
                         `client_tss` — 2-party threshold key; the customer's passkey share is required.
+                owner_wraps:
+                    type: integer
+                    description: |
+                        `client_tss` only (list responses). Wraps of the customer's share under
+                        their own credentials — passkey PRF or recovery code; runtime holder
+                        wraps are not counted. Below 2 the wallet should not be funded: one
+                        lost credential would lose the share.
 
         TreasuryWalletListResponse:
             type: object

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@1claw/openapi-spec",
-  "version": "0.61.22",
+  "version": "0.61.23",
   "description": "OpenAPI 3.1.0 specification for the 1Claw Vault API \u2014 generate clients in any language",
   "license": "MIT",
   "repository": {