Skip to main content
Out of the box, an agent can only talk. Tools let it act: fetch an order status mid-call, open a page in your app, or hang up when the conversation is over. You describe what a tool does and what arguments it takes; the agent decides when to call it.

Webhook tools

The platform calls your HTTP endpoint and speaks the result.

Client tools

Your application executes the tool through the SDK.

System tools

Built-in capabilities you switch on per agent.

Choose a tool type

Webhook and client tools are custom tools: you define a name, a description, and arguments, and the agent fills in the argument values when it calls. System tools are ready-made — enable them with a switch on each agent.

Where tools live

Custom tools are workspace resources, not part of a single agent. Define a lookup_order tool once and attach it to your support, sales, and after-hours agents. You manage them in two places:
  • Builder → Tools shows the tools attached to the agent you are editing, plus that agent’s system-tool switches. Tools you create here are attached to the agent immediately.
  • The workspace tool library lists every custom tool with how many agents use it. Tools you create here start unattached — grant agents access afterwards.
Editing a shared tool updates the draft of every agent that uses it. Those agents show unpublished changes until they are published again — see Versions & publishing.

Detach vs. delete

  • Detach is agent-scoped. Removing a tool from an agent in the Builder leaves the tool — and its other attachments — untouched.
  • Delete is workspace-wide. Deleting a tool from the library in the console detaches it from every agent that uses it, and those agents show unpublished changes.
Over the API, DELETE is stricter: it returns 409 while the tool is still attached to any agent. List the tool’s dependent agents first and detach it from each one.

Manage tools over the API

Every endpoint requires your API key — see Authentication. Create a webhook tool:
Arguments can be referenced anywhere in the request with {{name}} placeholders. Before deleting a tool, check which agents depend on it:
The response lists each dependent agent’s agent_id and name, plus a total count. Field-level configuration — custom headers, request body templates, timeouts, error handling, and mock responses — is covered in Webhook tools.

Going further

Test it live

Call your draft agent before publishing.

Versions & publishing

Drafts, published versions, and what “unpublished changes” means.

Web SDK

Register client tool handlers in your application.

Authentication

API keys for the endpoints above.