@1claw/openapi-spec 0.61.45 → 0.61.46

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/openapi.json CHANGED
@@ -2,7 +2,7 @@
2
2
  "openapi": "3.1.0",
3
3
  "info": {
4
4
  "title": "1Claw API",
5
- "version": "0.61.45",
5
+ "version": "0.61.46",
6
6
  "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",
7
7
  "contact": {
8
8
  "email": "ops@1claw.co"
@@ -28291,6 +28291,55 @@
28291
28291
  }
28292
28292
  }
28293
28293
  },
28294
+ "/v1/connectors/suggest": {
28295
+ "get": {
28296
+ "tags": [
28297
+ "Connectors"
28298
+ ],
28299
+ "summary": "Is there a connector for this credential?",
28300
+ "description": "Asked before a secret is written, so the caller can offer to connect the service properly instead of filing a key that cannot do the job. A user stored an X bearer token, a consumer key and a consumer secret and asked their agent to post daily; none of the three can post, because X needs a user-context OAuth grant. Nothing said so until the agent failed.\n\nMatches on both a provider name and a credential word, so `api-keys/x-bearer-token` suggests the X connector and `notes/slack-migration-plan` suggests nothing — a hint that fires on every path is one people learn to scroll past.\n",
28301
+ "operationId": "suggest_connector",
28302
+ "parameters": [
28303
+ {
28304
+ "name": "path",
28305
+ "in": "query",
28306
+ "required": true,
28307
+ "schema": {
28308
+ "type": "string"
28309
+ },
28310
+ "description": "The secret path about to be written."
28311
+ }
28312
+ ],
28313
+ "responses": {
28314
+ "200": {
28315
+ "description": "The matching connector, or null.",
28316
+ "content": {
28317
+ "application/json": {
28318
+ "schema": {
28319
+ "type": "object",
28320
+ "required": [
28321
+ "preset"
28322
+ ],
28323
+ "properties": {
28324
+ "preset": {
28325
+ "nullable": true,
28326
+ "allOf": [
28327
+ {
28328
+ "$ref": "#/components/schemas/ConnectorPreset"
28329
+ }
28330
+ ]
28331
+ }
28332
+ }
28333
+ }
28334
+ }
28335
+ }
28336
+ },
28337
+ "401": {
28338
+ "description": "Unauthenticated"
28339
+ }
28340
+ }
28341
+ }
28342
+ },
28294
28343
  "/v1/billing/promo/preview": {
28295
28344
  "get": {
28296
28345
  "tags": [
package/openapi.yaml CHANGED
@@ -2,7 +2,7 @@ openapi: 3.1.0
2
2
 
3
3
  info:
4
4
  title: 1Claw API
5
- version: "0.61.45"
5
+ version: "0.61.46"
6
6
  description: |
7
7
  Secure secret management for AI agents. Provides vaults, secrets,
8
8
  policy-based access control, agent identity, Intents API,
@@ -18065,6 +18065,45 @@ paths:
18065
18065
  answered GET would look like a working unsubscribe to a
18066
18066
  person and a broken one to the providers scoring the domain.
18067
18067
  operationId: marketing_unsubscribe_post
18068
+ /v1/connectors/suggest:
18069
+ get:
18070
+ tags: [Connectors]
18071
+ summary: "Is there a connector for this credential?"
18072
+ description: >
18073
+ Asked before a secret is written, so the caller can offer to
18074
+ connect the service properly instead of filing a key that
18075
+ cannot do the job. A user stored an X bearer token, a consumer
18076
+ key and a consumer secret and asked their agent to post daily;
18077
+ none of the three can post, because X needs a user-context
18078
+ OAuth grant. Nothing said so until the agent failed.
18079
+
18080
+
18081
+ Matches on both a provider name and a credential word, so
18082
+ `api-keys/x-bearer-token` suggests the X connector and
18083
+ `notes/slack-migration-plan` suggests nothing — a hint that
18084
+ fires on every path is one people learn to scroll past.
18085
+ operationId: suggest_connector
18086
+ parameters:
18087
+ - name: path
18088
+ in: query
18089
+ required: true
18090
+ schema: { type: string }
18091
+ description: The secret path about to be written.
18092
+ responses:
18093
+ '200':
18094
+ description: The matching connector, or null.
18095
+ content:
18096
+ application/json:
18097
+ schema:
18098
+ type: object
18099
+ required: [preset]
18100
+ properties:
18101
+ preset:
18102
+ nullable: true
18103
+ allOf:
18104
+ - $ref: '#/components/schemas/ConnectorPreset'
18105
+ '401':
18106
+ description: Unauthenticated
18068
18107
  /v1/billing/promo/preview:
18069
18108
  get:
18070
18109
  tags: [Billing]
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@1claw/openapi-spec",
3
- "version": "0.61.45",
3
+ "version": "0.61.46",
4
4
  "description": "OpenAPI 3.1.0 specification for the 1Claw Vault API — generate clients in any language",
5
5
  "license": "MIT",
6
6
  "repository": {