Rensei docs

Author an org-scope harness compatibility declaration.

Declares the protocols, session modes, and capability ceiling for one exact harness version, scoped to the authenticated organization. The compatibility digest is always recomputed from the submitted body, so a caller can never claim a ceiling its declaration does not contain. `scope: "system"` is refused: a system-scope entry is the cascade root for every organization without an override and is not a tenant write.

POST
/api/cli/harness/definitions

Authorization

headerAuthorizationBearer <rsk_live_*>

Rensei API key presented as Authorization: Bearer rsk_live_. Required API-key scopes are recorded per operation in x-rensei-required-scopes.

Request Body

application/json
  1. body
definition*

Response Body

The durable catalog entry.

application/json
  1. response
compatibilityDigest*string
Match^[0-9a-f]{64}$
harness*
lifecycle*string
Value in"configured""disabled""deleted"
Example Request
curl -X POST 'https://app.rensei.ai/api/cli/harness/definitions' \  -H 'Content-Type: application/json' \  -d '{  "definition": {    "definitionVersion": "rensei.harness-definition/v1alpha1",    "ref": {      "id": "string",      "version": "string"    },    "scope": "system",    "orgId": "string",    "displayName": "string",    "declaredProtocols": [      "string"    ],    "declaredSessionModes": [      "autonomous"    ],    "declaredCapabilityCeiling": [      "string"    ],    "lifecycle": "configured"  }}'
Example Response
{  "compatibilityDigest": "string",  "harness": {    "id": "string",    "version": "string"  },  "lifecycle": "configured"}