Skip to main content
POST
JavaScript
The gentle retirement. Archiving stops a tool set from syncing, hides it from the default list, and pulls its tools out of running agents, without throwing anything away.
Both directions are idempotent and return 200.

Archive works while assigned. Delete does not.

This is the reason archive exists. A tool set assigned to a variation refuses to delete with a 400. Archiving the same set succeeds:
So archive is how you retire a set that is still wired into an agent, without first hunting down every assignment.

The assignment survives

Archiving does not remove the variation assignment. It decouples the tools from running objectives while the set is archived, and unarchive restores it whole. Verified: a set assigned to a variation, archived, then unarchived, is still assigned to that variation afterward.
That is the difference from delete in one line: delete severs the assignment for good; archive parks it.

Finding archived sets

The default list shows only STATE_ACTIVE sets. An archived one appears only when you ask:
A synced set does not re-sync while archived. Unarchive it and the next sync cycle picks it back up.

Delete a tool set

The permanent version, refused while assigned.

List tool sets

?state=STATE_ARCHIVED to see what you retired.

Create a tool set

What archiving stops syncing.

Add an assignment

The assignment that archive keeps and delete severs.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

workspaceId
string
required

Workspace ID.

Example:

"workspace_01HXKD2E5NQM3T9AYWCF133E3Q"

id
string
required

Tool set ID. Accepts the canonical ts_… form or the external_id: form.

Example:

"toolset_01HXKD2E5NQM3T9AYWCFNRMN74"

Body

application/json

Archive tool set request

Response

OK

metadata
object
required

Standard metadata for persistent, named resources (e.g., agents, tools, prompts)

spec
object
required
state
enum<string>
required
read-only

The current lifecycle state of the tool set. Output only. Tool sets are created STATE_ACTIVE; use the :archive and :unarchive actions to transition between states.

Available options:
STATE_UNSPECIFIED,
STATE_ACTIVE,
STATE_ARCHIVED
info
object

Tool set information