Creating Agents

​

Endpoints

• POST /agent/create creates a new agent.
• POST /agent//update updates metadata and mutates graph structure.
• POST /agent//duplicate duplicates an agent and returns its copied graph payload.
• POST /agent//delete soft-deletes an agent.

​

Agent Graph Model

• Node params are validated server-side using tile metadata and node schemas.
• Position is backend-managed (auto-layout), not client-managed.
• Agent node responses are represented as agent_node_id, node_type, and params_used (node_type contains node_type_id and docs metadata).
• New nodes in create_node operations can only use request-scoped temp_ref_id; persisted agent_node_id values are backend-generated and returned in the response.
• temp_ref_id values are never persisted and only work within the single update request where they are created.

​

Optional Dashboard Flow

​

Next Steps

• Use GET /agent/[agent_id] to inspect your template
• Use POST /agent/[agent_id]/duplicate to clone an existing template graph
• Use POST /agent/[agent_id]/update for both metadata and graph mutations
• Use POST /agent/[agent_id]/run to execute it
• Use GET /node_types to discover available node types