---
title: "Opt a rental in or out of Hyperbolic telemetry"
method: POST
path: "/v2/on-demand/rentals/monitoring-opt-out"
tags: ["rentals"]
---

# Opt a rental in or out of Hyperbolic telemetry

`POST /v2/on-demand/rentals/monitoring-opt-out`

## Request

- Base URL: `https://api.hyperbolic.ai`
- URL: `https://api.hyperbolic.ai/v2/on-demand/rentals/monitoring-opt-out`
- Auth: HTTP bearer

Opt a running or pending virtual machine rental in or out of Hyperbolic telemetry. Takes effect within a few minutes, without a restart. Collection is on unless a rental is opted out. Only standalone virtual machine rentals in supported regions can opt out, not Kubernetes cluster node pools: other rentals get a 400. An unknown rental gets `RENTAL_NOT_FOUND`, and a failed update a 500 that is safe to retry.

## Request body

- object
  - `rentalId` union, required
    - string: The rental's `rentalId`.
    - integer: Deprecated. The rental's legacy numeric id; use `rentalId`.
  - `monitoringOptOut` boolean, required: Opt the rental out of Hyperbolic telemetry: the GPU health and system metrics (CPU, memory, root filesystem, network interfaces) Hyperbolic collects from inside the virtual machine to detect hardware faults. No logs, process lists or file contents are collected.

## Response `200`

Successful response

- SuccessResponse: Result of an operation that returns no payload.
  - `success` boolean, required

## Other responses

- `400`: Invalid input data
- `401`: Authorization not provided
- `403`: Insufficient access
- `500`: Internal server error

## Changes

- **2026-10-27** `dbf29b4ec8ea`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/hyperbolic/apis/castle-api/changes/v2/on-demand/rentals/monitoring-opt-out/post.md)

---

[API](https://skmtc.dev/hyperbolic/apis/castle-api.md) - [All operations](https://skmtc.dev/hyperbolic/apis/castle-api/llms.txt) - [OpenAPI document](https://skmtc.dev/hyperbolic/apis/castle-api/revisions/d4d4f25214b8?raw)