Toolkit builder

What it does

The Toolkit Builder (Tools → Toolkit Builder) turns a plain-English goal into a working set of tools. Describe what you want ("let the agent check order status and issue refunds in Shopify") and optionally pin a specific API docs URL, and the platform reads the vendor's live documentation and drafts a full tool set — not a single tool.

Reviewing the draft

The draft shows each proposed tool with its HTTP method, whether it reads or writes data, a link to the source documentation it was drafted from, and a checkbox to include or exclude it. Anything the drafting process discarded as invalid is listed too, with a reason, so you can see what didn't make the cut and why.

Credentials

If the API needs a static API key, you're prompted for it right in the wizard — only an organization admin can save it; if you're not an admin, the toolkit still saves and starts working automatically once an admin adds the key. OAuth-based APIs are connected after saving, from the toolkit's card — see Connecting credentials for the different credential types.

Saving and testing

Saving a toolkit puts it on the Tools tab immediately, but the tools are not automatically tested — testing is a deliberate, separate step. Use Test all or test tools individually from the toolkit's card. Read-only tools can be safely test-run; tools that write or mutate data are never auto-run during testing and always show as "untested by design" — you decide when to exercise those for real.

Managing a toolkit

Because a toolkit owns the tools it created, it enables, tests, and deletes as a single unit from its card on the Tools tab, alongside the goal it was built for and the guidance text that gets added to the agent's behavior while any of its tools are enabled.