@1claw/openapi-spec 0.61.47 → 0.61.48

package/openapi.json

@@ -2,7 +2,7 @@
   "openapi": "3.1.0",
   "info": {
     "title": "1Claw API",
-    "version": "0.61.47",
+    "version": "0.61.48",
     "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"
@@ -11372,6 +11372,146 @@
         }
       }
     },
+    "/v1/treasury/wallets/{chain}/sign-message": {
+      "post": {
+        "tags": [
+          "Treasury"
+        ],
+        "summary": "Sign a message with a human wallet (EIP-191)",
+        "description": "`personal_sign` over the given text, hashed as `\\x19Ethereum Signed Message:\\n<len>` + message — what viem's `verifyMessage` and ethers' `verifyMessage` expect.\n\nHuman callers only; an agent signs with its own key via `POST /v1/agents/{agent_id}/sign`. Gated exactly as a send is: `X-Auth-Confirm` step-up scored as a Send action, wallet access policies (`WalletAction::Sign`), and a refusal for wallets whose key is split or passkey-owned — those have no server-side key and will not fall back to one.\n\nEVM chains only.\n",
+        "operationId": "signTreasuryMessage",
+        "parameters": [
+          {
+            "name": "chain",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string",
+              "example": "ethereum"
+            }
+          },
+          {
+            "name": "X-Auth-Confirm",
+            "in": "header",
+            "required": true,
+            "schema": {
+              "type": "string"
+            },
+            "description": "Account password, or a `rat_` token from `POST /v1/auth/reauth/complete`."
+          }
+        ],
+        "requestBody": {
+          "required": true,
+          "content": {
+            "application/json": {
+              "schema": {
+                "type": "object",
+                "required": [
+                  "message"
+                ],
+                "properties": {
+                  "message": {
+                    "type": "string",
+                    "maxLength": 16384,
+                    "example": "Sign in to Example at 2026-10-01T10:00:00Z"
+                  }
+                }
+              }
+            }
+          }
+        },
+        "responses": {
+          "200": {
+            "description": "Signature",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/WalletSignature"
+                }
+              }
+            }
+          },
+          "400": {
+            "description": "Empty or oversized message, or a non-EVM chain"
+          },
+          "403": {
+            "description": "Agent caller, missing or insufficient step-up, denied by a wallet access policy, or a self-custody wallet the server cannot sign for.\n"
+          },
+          "404": {
+            "description": "No wallet on that chain for this user"
+          }
+        }
+      }
+    },
+    "/v1/treasury/wallets/{chain}/sign-typed-data": {
+      "post": {
+        "tags": [
+          "Treasury"
+        ],
+        "summary": "Sign EIP-712 typed data with a human wallet",
+        "description": "Hashes and signs a full EIP-712 payload. Include `EIP712Domain` in `types` — viem and ethers synthesise that entry and omit it, and this hashes exactly what you send.\n\nSame gates as `sign-message`.\n",
+        "operationId": "signTreasuryTypedData",
+        "parameters": [
+          {
+            "name": "chain",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string",
+              "example": "base"
+            }
+          },
+          {
+            "name": "X-Auth-Confirm",
+            "in": "header",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "requestBody": {
+          "required": true,
+          "content": {
+            "application/json": {
+              "schema": {
+                "type": "object",
+                "required": [
+                  "typed_data"
+                ],
+                "properties": {
+                  "typed_data": {
+                    "type": "object",
+                    "description": "`types`, `primaryType`, `domain`, `message`."
+                  }
+                }
+              }
+            }
+          }
+        },
+        "responses": {
+          "200": {
+            "description": "Signature",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/WalletSignature"
+                }
+              }
+            }
+          },
+          "400": {
+            "description": "Malformed EIP-712 payload, or a non-EVM chain"
+          },
+          "403": {
+            "description": "Same refusals as sign-message"
+          },
+          "404": {
+            "description": "No wallet on that chain for this user"
+          }
+        }
+      }
+    },
     "/v1/treasury/wallets/{chain}/swap": {
       "post": {
         "tags": [
@@ -28565,6 +28705,10 @@
                     "granted_read": {
                       "type": "boolean",
                       "description": "False when the secret was stored but the read grant could not be written — the agent will need access granted by hand.\n"
+                    },
+                    "bound_new_vault": {
+                      "type": "boolean",
+                      "description": "True when the agent had to be bound to a vault it was not bound to before. Its access is correct from now on, but a JWT carries the `vault_ids` it was minted with, so a token the agent already holds is refused until it re-mints. Answering into a vault the agent already reaches avoids this.\n"
                     }
                   }
                 }
@@ -28572,7 +28716,7 @@
             }
           },
           "400": {
-            "description": "Already answered, expired, or an invalid path"
+            "description": "Already answered, expired, an invalid path, or nothing is stored at that path — the location the agent is sent to has to be real.\n"
           },
           "403": {
             "description": "Called by an agent"
@@ -42408,6 +42552,27 @@
           }
         }
       },
+      "WalletSignature": {
+        "type": "object",
+        "required": [
+          "signature",
+          "address",
+          "chain"
+        ],
+        "properties": {
+          "signature": {
+            "type": "string",
+            "description": "65-byte `0x`-prefixed signature, r‖s‖v."
+          },
+          "address": {
+            "type": "string",
+            "description": "The signing wallet, so it can be passed straight to `verifyMessage`."
+          },
+          "chain": {
+            "type": "string"
+          }
+        }
+      },
       "SecretRequest": {
         "type": "object",
         "description": "An agent's open ask, as the human sees it. Carries the request and, once fulfilled, a reference — never a value.\n",

package/openapi.yaml

@@ -2,7 +2,7 @@ openapi: 3.1.0
 
 info:
     title: 1Claw API
-    version: "0.61.47"
+    version: "0.61.48"
     description: |
         Secure secret management for AI agents. Provides vaults, secrets,
         policy-based access control, agent identity, Intents API,
@@ -7207,6 +7207,109 @@ paths:
                 "404":
                     $ref: "#/components/responses/NotFound"
 
+    /v1/treasury/wallets/{chain}/sign-message:
+        post:
+            tags: [Treasury]
+            summary: "Sign a message with a human wallet (EIP-191)"
+            description: >
+                `personal_sign` over the given text, hashed as
+                `\x19Ethereum Signed Message:\n<len>` + message — what
+                viem's `verifyMessage` and ethers' `verifyMessage` expect.
+
+
+                Human callers only; an agent signs with its own key via
+                `POST /v1/agents/{agent_id}/sign`. Gated exactly as a send
+                is: `X-Auth-Confirm` step-up scored as a Send action, wallet
+                access policies (`WalletAction::Sign`), and a refusal for
+                wallets whose key is split or passkey-owned — those have no
+                server-side key and will not fall back to one.
+
+
+                EVM chains only.
+            operationId: signTreasuryMessage
+            parameters:
+                - name: chain
+                  in: path
+                  required: true
+                  schema: { type: string, example: ethereum }
+                - name: X-Auth-Confirm
+                  in: header
+                  required: true
+                  schema: { type: string }
+                  description: Account password, or a `rat_` token from `POST /v1/auth/reauth/complete`.
+            requestBody:
+                required: true
+                content:
+                    application/json:
+                        schema:
+                            type: object
+                            required: [message]
+                            properties:
+                                message:
+                                    type: string
+                                    maxLength: 16384
+                                    example: Sign in to Example at 2026-10-01T10:00:00Z
+            responses:
+                '200':
+                    description: Signature
+                    content:
+                        application/json:
+                            schema:
+                                $ref: '#/components/schemas/WalletSignature'
+                '400':
+                    description: Empty or oversized message, or a non-EVM chain
+                '403':
+                    description: >
+                        Agent caller, missing or insufficient step-up, denied by a
+                        wallet access policy, or a self-custody wallet the server
+                        cannot sign for.
+                '404':
+                    description: No wallet on that chain for this user
+    /v1/treasury/wallets/{chain}/sign-typed-data:
+        post:
+            tags: [Treasury]
+            summary: "Sign EIP-712 typed data with a human wallet"
+            description: >
+                Hashes and signs a full EIP-712 payload. Include
+                `EIP712Domain` in `types` — viem and ethers synthesise that
+                entry and omit it, and this hashes exactly what you send.
+
+
+                Same gates as `sign-message`.
+            operationId: signTreasuryTypedData
+            parameters:
+                - name: chain
+                  in: path
+                  required: true
+                  schema: { type: string, example: base }
+                - name: X-Auth-Confirm
+                  in: header
+                  required: true
+                  schema: { type: string }
+            requestBody:
+                required: true
+                content:
+                    application/json:
+                        schema:
+                            type: object
+                            required: [typed_data]
+                            properties:
+                                typed_data:
+                                    type: object
+                                    description: '`types`, `primaryType`, `domain`, `message`.'
+            responses:
+                '200':
+                    description: Signature
+                    content:
+                        application/json:
+                            schema:
+                                $ref: '#/components/schemas/WalletSignature'
+                '400':
+                    description: Malformed EIP-712 payload, or a non-EVM chain
+                '403':
+                    description: Same refusals as sign-message
+                '404':
+                    description: No wallet on that chain for this user
     /v1/treasury/wallets/{chain}/swap:
         post:
             tags: [Treasury Wallets]
@@ -18279,8 +18382,22 @@ paths:
                                             the read grant could not be written —
                                             the agent will need access granted
                                             by hand.
+                                    bound_new_vault:
+                                        type: boolean
+                                        description: >
+                                            True when the agent had to be bound to
+                                            a vault it was not bound to before. Its
+                                            access is correct from now on, but a
+                                            JWT carries the `vault_ids` it was
+                                            minted with, so a token the agent
+                                            already holds is refused until it
+                                            re-mints. Answering into a vault the
+                                            agent already reaches avoids this.
                 '400':
-                    description: Already answered, expired, or an invalid path
+                    description: >
+                        Already answered, expired, an invalid path, or nothing is
+                        stored at that path — the location the agent is sent to has
+                        to be real.
                 '403':
                     description: Called by an agent
                 '404':
@@ -27298,6 +27415,18 @@ components:
                         an approval by reply.
                 created_at: { type: string, format: date-time }
 
+        WalletSignature:
+            type: object
+            required: [signature, address, chain]
+            properties:
+                signature:
+                    type: string
+                    description: 65-byte `0x`-prefixed signature, r‖s‖v.
+                address:
+                    type: string
+                    description: The signing wallet, so it can be passed straight to `verifyMessage`.
+                chain: { type: string }
+
         SecretRequest:
             type: object
             description: >

package/package.json

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