capabilities
What each connected channel can do RIGHT NOW (publish verdict with the reason when blocked — missing scope, disconnected, unsupported), plus every provider's platform manifest (text limits, metrics, platform_options sch…
What each connected channel can do RIGHT NOW (publish verdict with the reason when blocked — missing scope, disconnected, unsupported), plus every provider’s platform manifest (text limits, metrics, platform_options schema). Consult this before composing instead of discovering limits by error.
Input
| Field | Type | Required | Description |
|---|---|---|---|
organization | string | no | Organization slug to act in (see organizations_list). Optional: API keys are bound to one organization; OAuth connections default to your active organization. |
Result
JSON on success. A refusal comes back as an error prefixed with its code (NOT_FOUND, FORBIDDEN, TOO_MANY_REQUESTS, …) and a message written to be acted on — read it before retrying.
The same operation elsewhere
This tool and the REST operation capabilitiesList and the CLI command inklate capabilities run the same guarded procedure the dashboard uses — same permissions, same validation, same tenant isolation.