Rules
The Rules operations of the Hub REST API (4 operations).
bearerAuthAuthorizationBearer <API key>Pod API key (Bearer) issued via /api/hub/setup/agent or pod admin tooling. Browser/web clients may use the X-Session-Token header instead. See GET /api/hub/auth/status to introspect the calling key.
application/json- body
text*string1 <= lengthcontext?Intent route
application/json- response
shapes*array<>primary*stringoneShot*booleanneedsClarification?curl -X POST 'https://pod.example.com/api/hub/rules/classify' \ -H 'Content-Type: application/json' \ -d '{ "text": "string"}'{ "shapes": [ { "shape": "string", "confidence": 0, "cues": [ "string" ] } ], "primary": "string", "oneShot": true, "needsClarification": { "reason": "string", "question": "string" }}bearerAuthAuthorizationBearer <API key>Pod API key (Bearer) issued via /api/hub/setup/agent or pod admin tooling. Browser/web clients may use the X-Session-Token header instead. See GET /api/hub/auth/status to introspect the calling key.
application/json- body
text*string1 <= length <= 2000workspaceId?stringuuidParsed sentence
application/json- response
[key: string]?unknowncurl -X POST 'https://pod.example.com/api/hub/rules/parse' \ -H 'Content-Type: application/json' \ -d '{ "text": "string"}'{ "property1": null, "property2": null}bearerAuthAuthorizationBearer <API key>Pod API key (Bearer) issued via /api/hub/setup/agent or pod admin tooling. Browser/web clients may use the X-Session-Token header instead. See GET /api/hub/auth/status to introspect the calling key.
workspaceId?stringuuidlimit?number1 <= value <= 100offset?|0 <= valueincludeProposed?boolean|Rules
application/json- response
rules*array<>curl -X GET 'https://pod.example.com/api/hub/rules'{ "rules": [ { "id": "string", "name": "string", "approved": true, "workspaceId": "string", "createdAt": "string", "rule": { "property1": null, "property2": null }, "status": "active", "proposalId": "string" } ]}bearerAuthAuthorizationBearer <API key>Pod API key (Bearer) issued via /api/hub/setup/agent or pod admin tooling. Browser/web clients may use the X-Session-Token header instead. See GET /api/hub/auth/status to introspect the calling key.
application/json- body
intent*string1 <= lengthscope*expiresAt?stringdate-timefactSkillId?stringuuidautomationIds?array<>[]sentence?agentUserId?stringuuiduserId?stringuuidCreated or proposed
application/json- response
status*"created""created"ruleId*stringcurl -X POST 'https://pod.example.com/api/hub/rules' \ -H 'Content-Type: application/json' \ -d '{ "intent": "string", "scope": { "kind": "pod" }}'{ "status": "created", "ruleId": "string"}