GET /v1/tools
List tools — The names-only tool catalogue: each tool's name, display name, category, one-line description, plan tier and whether it runs on a GPU.
ivy_ API key (Authorization: Bearer ivy_…), a signed-in session token (Authorization: Bearer …) or the session cookie (browser sessions). See Authentication.The names-only tool catalogue: each tool's name, display name, category, one-line description, plan tier and whether it runs on a GPU. Needs an API key or a signed-in session; without one the call returns 401. Only tools this deployment offers are listed: deprecated, stopped and disabled tools are left out. Tools the agent uses for its own bookkeeping (memory, background tasks, delegation to sub-agents, planning and review) are not listed either.
Parameter schemas are not part of this catalogue; read them from GET /api/v1/tools/{name}. Send If-None-Match with the last ETag to get a 304 when nothing has changed.
Request
Headers
The ETag from an earlier response.
Responses
200 OK
Response shape:
When the deployed tool catalog was generated. Fixed per deploy, so every instance returns the same value
304 Not Modified
If-None-Match ETag401 Unauthorized
Response shape: object
429 Too Many Requests
Response shape: object
Was this page helpful?
POST /v1/sessions/{sessionId}/interrupt/{interruptId}/resolve
Resolve an interrupt — Approve or reject a pending interrupt. The executing session must still be live (i.e., the /execute SSE stream is still open).
GET /v1/tools/{name}
Get a tool by name — Returns full metadata for a single tool including its JSON Schema for inputs and outputs.