Describe the AI operations available in a workspace
Returns the operation catalog revision along with each operation's label, icon, presentation, and the Ask/Build/Act modes it supports, which is what the client uses to render the AI surface. Requires an authenticated caller who is a member of the workspace.
Authorization
apiKey Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.
In: header
Path Parameters
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/v1/workspaces/string/ai/capabilities"{ "data": { "revision": "string", "operations": [ { "name": "string", "kind": "string", "method": "string", "description": "string", "permission": "string", "riskCeiling": "none", "verifiability": "verified", "inputSchema": {}, "outputSchema": {}, "strict": true, "doc": { "summary": "string", "useWhen": "string", "avoidWhen": "string", "useInstead": "string", "keywords": [ "string" ], "returns": "string", "examples": [ "string" ], "errors": [ { "code": "string", "message": "string" } ] }, "label": "string", "icon": "string", "presentation": "read", "modes": [ "ask" ] } ] }}{ "_tag": "ApiNotFound", "error": "not_found", "message": "That item does not exist, or this key cannot see it.", "status": 404}{ "_tag": "ApiNotFound", "error": "not_found", "message": "That item does not exist, or this key cannot see it.", "status": 404}Revoke a standing approval for an operation
Deletes the standing "always allow" policy for one operation so the agent asks about it again, and returns the policies that remain. Requires a workspace member with the `ai:write` permission, because starting to ask again is a workspace setting rather than a chat action. Naturally idempotent: revoking an operation that has no standing policy leaves the list unchanged.
Plan a database configuration from a prompt
Runs a generator grounded in the database's current fields and persists the result as a `planned` run: a list of typed operations, each annotated with the stake needed to run it, plus the highest stake across the plan. Nothing is applied. Requires a workspace member with both the `ai:write` and `records:write` permissions and the `ai.database_builder.enabled` control switched on, and the workspace AI allowance is checked before the model is called so an exhausted budget is refused up front. An empty prompt is rejected.