bot.resource.control
Generated at from
openvibe-contracts v0.177.0 and
openvibe-sdk v0.44.0.
Control a person's robots through the authority's control API (ADR-048 amendment 2026-10-15, step 8 phase 2): POST /api/v1/resources/control takes one common.owned-resource-control-request@1 naming a bot.robot (id rob_<ULID>) from a first-party service (OpenVibe.Services) acting for the person in on_behalf_of. Actions: stop (latch the robot's remote e-stop, as POST /api/v1/robots/:id/estop: every actuator stops and nothing moves until it is cleared) and resume (clear that e-stop, as POST /api/v1/robots/:id/estop/clear; a local stop on the robot itself still holds); any other action is refused unsupported. Only the resource's owner may act: the request's owner must be the owner the authority holds. dry_run decides and explains without applying. The first answer per (caller, idempotency_key) is kept and returned for a repeat; the same key with another request is refused. Answers common.resource-control-result@1 without resource (person-owned resources have no OVRN).
- Owner
- bot (token audience
openvibe.bot) - Version
- 1.0
- Status
- active
- Visibility
- first-party
- Resource constraints
- owner
- Quota class
- standard
- Permissions
- resources:control
- Input
- common.owned-resource-control-request@1
- Output
- common.resource-control-result@1
- Events
- —
- Implemented by
POST /api/v1/resources/control