List the capabilities this credential may use

The catalogue, as this credential sees it. Not a fixed list: it is computed per call from the plan, the permissions of the bearer, the allowlist of the consent that produced the token, and the project the token carries. Two credentials on the same project can see different catalogues, and the same credential can see a different one tomorrow.

Each entry carries its paramsSchema — the JSON Schema of what invoke accepts. An empty properties means the capability takes no parameters, and nothing else.

Read writesOnInvoke before calling anything. It marks the capabilities whose invocation already starts the work and consumes quota — there is no dry run for those. The others declared propose only compute a diff: calling them changes nothing until applyProposal follows.

curl -X GET "https://app.digitalyser.io/api/v1/capabilities" \  -H "Authorization: Bearer <token>"

{  "projectId": "8f14e45f-ea0e-4b1e-9b7a-2c3d4e5f6071",  "capabilities": [    {      "id": "audit.overview.get",      "description": "Reads the cross-module audit overview of the project.",      "effect": "read",      "requiresProject": true,      "writesOnInvoke": false,      "paramsSchema": {        "type": "object",        "properties": {},        "additionalProperties": false      }    }  ],  "unavailableHere": {    "reason": "session_required",    "message": "These capabilities exist on this project but need a session to confirm a change.",    "capabilities": [      {        "id": "brandvoice.style.propose",        "description": "Proposes a new brand-voice style."      }    ]  }}

Generated from the capability registry — API version 1, 18 paths, from 4815355 (2026-10-12).