---
title: "bot.machine-manage-result@1 · OpenVibe.Services"
canonical: "https://openvibe.services/docs/contracts/bot.machine-manage-result"
updated: null
---

# bot.machine-manage-result@1 · OpenVibe.Services

HTML: [bot.machine-manage-result@1 · OpenVibe.Services](https://openvibe.services/docs/contracts/bot.machine-manage-result)

# BotMachineManageResult `bot.machine-manage-result@1`

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).

- Version: 1.0.0
- Owner: bot
- Visibility: first-party
- Status: active
- Compatibility: backward
- Schema: [`https://openvibe.network/contracts/bot/machine-manage-result.v1.json`](/docs/contracts/bot.machine-manage-result.json)

bot.machine-manage-result@1: the machine as it is after the change (plan L34, step M2). Bot is the registry underneath: it answers with its own device record, never with a credential.

## Fields

| Field | Type | Required | Description | Constraints |
| --- | --- | --- | --- | --- |
| `machine` | [bot.device](/docs/contracts/bot.device) | yes |  |  |

## Examples

From the contract's own test fixtures: valid ones validate, rejected ones must fail.

 Valid: machine

~~~~
{
  "machine": {
    "id": "dev_01JAB2C3D4E5F6G7H8J9K0MNPS",
    "robot_ids": [],
    "kind": "server",
    "name": "Kitchen server",
    "agent_version": "0.15.0",
    "drivers": [],
    "capabilities": {},
    "last_seen": "2026-10-31T09:00:00.000Z",
    "revoked_at": null,
    "created_at": "2026-10-31T09:00:00.000Z",
    "updated_at": "2026-10-31T09:00:00.000Z",
    "online": true,
    "roles": [
      "codes.worker"
    ],
    "os": "linux"
  }
}
~~~~

Rejected: missing-machine

~~~~
{}
~~~~

## Validate

~~~~
const contracts = require('openvibe-contracts');
contracts.validate('bot.machine-manage-result@1', value);   // { valid, errors: [{ path, message }] }
~~~~
