Toolkits · Attach a toolkit to an agent
Attaches a toolkit by name. Without allowed_tools, every tool in it
becomes available to the agent, which costs prompt budget on every run —
so pass allowed_tools for a large toolkit and attach only what the agent
needs.
Attached toolkits are stored on the agent record rather than as separate rows,
so they are keyed by name — there is no toolkit ID.
resource: agent://build-guide covers narrowing a toolkit already attached.
Authentication
Header authentication of the form Api-Key <token>
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
Agent UUID or slug — both are accepted. From agents_listAgents.
Request
Toolkit name, from agents_listToolkits.
Restrict the toolkit to these tool names, from agents_listToolkits. Omit to expose everything it provides. Narrowing here rather than afterwards means the agent is never briefly attached to the whole set.
