API reference · schema
ToolRuleCondition
3 fields · used by 3 operations
Last reviewed 2026-10-02
Fields
| Field | Type | Meaning |
|---|---|---|
field required | string | dotted path into the payload, e.g. amount_usd or query |
op required | string | eq neq gt gte lt lte contains not_contains matches exists |
value | any or null |
Smallest valid example
{
"field": "field",
"op": "op"
}Used by 3 operations
| POST | /fabric/tool-rules | Add a tool rule |
| POST | /fabric/tool-rules/test | Which rule would decide this call? (no evidence, no quota) |
| PUT | /fabric/tool-rules/{rule_id} | Change a tool rule (its version increments) |
JSON Schema
Show the raw definition
{
"properties": {
"field": {
"type": "string",
"title": "Field",
"description": "dotted path into the payload, e.g. amount_usd or query"
},
"op": {
"type": "string",
"title": "Op",
"description": "eq neq gt gte lt lte contains not_contains matches exists"
},
"value": {
"anyOf": [
{},
{
"type": "null"
}
],
"title": "Value"
}
},
"type": "object",
"required": [
"field",
"op"
],
"title": "ToolRuleCondition"
}Try CAIN-42 on your own agents
Create a free account and every new account starts with a 7-day trial of the full platform. Or try the sandbox first, with no account at all.
Create a free account → · Try the sandbox · See the whole ecosystem