---
title: "Api Restart Agent"
method: POST
path: "/dashboard/api/hosts/{host_id}/restart"
tags: ["dashboard"]
---

# Api Restart Agent

`POST /dashboard/api/hosts/{host_id}/restart`

## Request

- Base URL: `https://mcp.sentinelx.app` (the document declares no server; this is the origin it was published from)
- URL: `https://mcp.sentinelx.app/dashboard/api/hosts/{host_id}/restart`
- Auth: none declared

Restart the SentinelX agent on a host (owner-only).

Low-risk: a restart just re-reads the existing config — it changes no
permissions and touches no allowlist. It's how a config edit takes
effect. Only the session cookie is required (no arm token): restarting
can't escalate anything on its own.

The agent restarts *itself*, so its WebSocket drops mid-command and the
call raises a disconnect. That's the EXPECTED success signal, not a
failure — the agent reconnects to the hub on its own within seconds.

## Path parameters

- `host_id` string, required

## Cookies

- `sentinelx_dash_session` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/sentinelx/apis/sentinelx-hub.md) · [All operations](https://skmtc.dev/sentinelx/apis/sentinelx-hub/llms.txt) · [OpenAPI document](https://skmtc.dev/sentinelx/apis/sentinelx-hub/revisions/d1f84924795e?raw)