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

# network.link.self.manage · OpenVibe.Services

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

# `network.link.self.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, internal).

A paired machine presents its own capabilities and rotates its own credential, never another machine's. It also announces itself for its owner's machine pools (bot.machine-pool@1), reads, approves and renews the pools it is a member of, and leaves them; it never acts for another machine.

- Owner: network (token audience `openvibe.network`)
- Version: 1.0
- Status: active
- Visibility: internal
- Resource constraints: owner
- Quota class: admin
- Permissions: nodes:self
- Events: —
- Implemented by: - `PUT /api/v1/link/self/capabilities`
- `POST /api/v1/link/self/credential`
- `POST /api/v1/link/self/pools/announce`
- `GET /api/v1/link/self/pools/:id`
- `POST /api/v1/link/self/pools/:id/approve`
- `POST /api/v1/link/self/pools/:id/status`
- `POST /api/v1/link/self/pools/:id/leave`

[These routes in the API explorer](/docs/api/network#cap-network.link.self.manage)