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

# network.machines.manage · OpenVibe.Services

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

# `network.machines.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).

Grantable to apps: request it for an app on its project page. Network approves it only inside the project's allowance.

Pair, rename, give roles to and revoke a person's own machines. Bot stays the registry underneath: Network asks Bot as the person, and Bot checks that the machine is theirs. An app needs the person's consent for this scope, and may then do only what the person could.

- Owner: network (token audience `openvibe.network`)
- Version: 1.0
- Status: active
- Visibility: public
- Resource constraints: owner
- Quota class: network-write
- Permissions: machines:pair, machines:rename, machines:roles, machines:revoke
- Input: [bot.machine-manage-request@1](/docs/contracts/bot.machine-manage-request)
- Output: network.machine-manage-result@1
- Events: network.machine.paired, network.machine.roles\_changed, network.machine.revoked
- Implemented by: - `POST /api/v1/machines/pairings`
- `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/network#cap-network.machines.manage)