Skip to main content
POST
Archive Agent Node

Overview

Stores a self-contained copy of a node in the organization archive, attributed to this agent, so you can retire it from the canvas without losing it. Archiving never changes the agent’s graph: remove the node yourself by saving a new version with Create Agent Version. Browse the archive with List Archived Nodes. Requires an admin, owner, operator, or prompter role.

Headers

string
required
Your API key for authentication.

Path Parameters

string
required
The agent the node is being archived from. Returns 404 NOT_FOUND if the agent does not exist in your organization.

Body Parameters

object
required
The node to archive, exactly as it appears in a version snapshot’s behavior.nodes. Must have a non-empty string id, a non-empty string type, a position object with finite numeric x and y, and an object data. A container node’s data.flow is validated too: every nested node needs id, position, and data, every nested edge needs string id, source, and target that reference nodes in the same flow, and flows may nest at most 10 levels deep. The serialized node may not exceed 1,048,576 bytes. Returns 400 INVALID_NODE with one error entry per problem.

Response

Returns 201 on success.
object
The new archive entry.
null | array
null on success, or a list of error objects if the request failed.

Docs for agents: llms.txt