---
title: "bot.machine.manage · OpenVibe.Services"
canonical: "https://openvibe.services/docs/capabilities/bot.machine.manage"
updated: null
---

# bot.machine.manage · OpenVibe.Services

HTML: [bot.machine.manage · OpenVibe.Services](https://openvibe.services/docs/capabilities/bot.machine.manage)

# `bot.machine.manage`

Generated at 2026-11-13 06:25:48 UTC from [`openvibe-contracts v0.419.0`](https://github.com/OpenVibers/OpenVibe.Contracts/tree/v0.419.0) and [`openvibe-sdk v0.161.0`](https://github.com/OpenVibers/OpenVibe.SDK/tree/v0.161.0).

Not grantable to apps (active, first-party).

A service acts for a person on their machines through Bot's machines API: it lists, renames, gives roles to and revokes the machines of the person it names (X-OV-Subject). Network holds it for the machines hub (openvibe.link/machines): Bot stays the registry underneath, so Bot checks that the machine is the named person's own. Never grantable to apps.

- Owner: bot (token audience `openvibe.bot`)
- Version: 1.0
- Status: active
- Visibility: first-party
- Resource constraints: owner
- Quota class: bot-machine
- Permissions: bot:machine:read, bot:machine:rename, bot:machine:roles, bot:machine:revoke
- Input: [bot.machine-manage-request@1](/docs/contracts/bot.machine-manage-request)
- Output: bot.machine-manage-result@1
- Events: —
- Implemented by: - `GET /api/v1/machines`
- `GET /api/v1/machines/:id`
- `PATCH /api/v1/machines/:id`
- `PUT /api/v1/machines/:id/roles`
- `POST /api/v1/machines/:id/revoke`

[These routes in the API explorer](/docs/api/bot#cap-bot.machine.manage)