consult_node
Fetch a compliance node and record a verified entry in an open run, proving which rule was consulted at which version.
Instructions
The one-call governed turn: fetch the full vault node (this consumes one call on your key, exactly like unlocking a node) and record a verified node_consulted entry for it on an open run, in a single step. The entry pins the node to its current version and integrity hash, so the run receipt proves what the agent actually consulted. Use this instead of get_node when you are inside a run. Requires a Bidda subscription key (a free trial counts).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"run_id": "<run_id>",
"node_id": "<node_id>",
"api_key": "<api_key>"
},
"name": "consult_node"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| model | No | Optional: the model id/version making the decision. | |
| action | No | Optional: an action the agent took or checked. | |
| run_id | Yes | The open run to record into (from open_run). | |
| api_key | Yes | Your Bidda subscription API key. A free trial counts. | |
| node_id | Yes | The rule to fetch and record. | |
| decision | No | Optional: what the agent decided using this node. | |
| input_hash | No | Optional: a sha256:... hash of the user's message instead of the text. | |
| user_input | No | Optional: the end user's message as text. | |
| subject_hash | No | Optional: a sha256:... hash of an end-user identifier. Hash only. |