Skip to main content
Lists the tools available for execution in a project. Each result provides a tool summary, including its name, type, description, declared effect, and execution availability. The endpoint returns only tools whose types are enabled for public API execution. Use this endpoint to discover available tools before retrieving a tool’s input schema or invoking it. Results are paginated using a cursor based on the tool name. Permission: tool:read, granted by the platform API key scope tools.read.

​
Path parameters

​
Query parameters

Supported tool types include http, mcp, searchai, workflow, table, integration, and connector. The legacy persisted value connector represents integration. Types that this API surface never serves are rejected rather than silently returning an empty page.

​
Authentication

Use one of the supported credentials:
  • x-api-key: abl_... — platform API key.
  • Authorization: Bearer <abl_... | JWT> — platform API key or Studio user JWT.
  • auth: <assertion> — JWT App assertion.
Public SDK keys (pk_...) are not accepted. The JWT App assertion must be sent in the auth header, not the Authorization header.

​
Response

A successful response contains success and data. The data object includes: Each tool summary can include name, type, description, effect, requiresAuthProfile, operations, executable, and unsupportedReason, depending on the tool. The executable property indicates whether a tool can be invoked through this API. The unsupportedReason property, when present, explains why it cannot be executed. To retrieve the input schema for a tool, use the Describe a tool endpoint.

​
Errors

The 429 response uses a rate-limiter-specific response format rather than the standard API error envelope. Check the response headers for rate-limit information and retry guidance.