Rig Node Update
rig_node_updateConfigure ONE block (graph node) of a canvas rig in place — 'change step 2's instruction', 'point that block at a live endpoint', 'pin Sonnet on the judge step'. Identify the block by id/label/skill/position; pass only the fields to change (rig_author's node fields) — a MERGE, so tweaking the instruction never wipes a wired endpoint. skill re-resolves the registry binding. The block keeps its id, edges, and canvas position. Returns the fresh block summary; the Builder canvas updates live.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | ||
| node | Yes | Which block: node id, label, skill name, or 1-based position ('2') | |
| tool | No | ||
| label | No | ||
| model | No | ||
| skill | No | Re-bind the block to this registry skill (optional) | |
| method | No | ||
| params | No | ||
| rig_id | Yes | UUID of the rig | |
| data_op | No | ||
| expects | No | What this step expects from upstream, in plain words | |
| headers | No | Extra HTTP headers for a `url` fetch. | |
| sub_rig | No | Re-bind the block as a SUB-RIG step: {rig_id, name?} (or the rig_id string). An existing sub-rig binding survives every OTHER patch untouched — you only need this to point the block at a different rig. | |
| data_key | No | ||
| endpoint | No | ||
| produces | No | What this step produces for downstream | |
| data_type | No | ||
| doc_input | No | ||
| instruction | No | ||
| secret_refs | No | The runner's saved keys for this step: [{alias, as?}] — as = 'param:<key>' | 'header:<Name>[:<prefix>]', or omit and use {{secret:<alias>}} in a param value. This is how you wire an API key onto an existing block ('use my coingecko key here'). Resolved server-side; never stored in the step or the trace. | |
| model_policy | No | ||
| wallet_address | Yes | Owner scope |