> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Senteon API

> Read Senteon endpoint hardening from Neo: an endpoint's configuration health, compliance, drift and alarms on its ticket

The common use is an endpoint hardening, CIS or compliance ticket in your PSA: the agent finds the endpoint the ticket names in the customer's tenant, reads its configuration health, compliance counts and active alarms, and writes them in an internal note with the context a technician needs to open it in Senteon. Agents also answer for a whole customer and read its numbers for a review.

> [!NOTE]
>
> Automatically enabled when you configure Senteon permissions in your agent workflow.

## What It Does

* Read your tenants and each tenant's endpoint counts: online, offline, active, pending activation, disabled, uninstalled, and each setup step
* Read endpoints by tenant, host name or id: status, configuration health (Healthy, Drifted or Inactive), baseline, last check-in and verification
* Read an endpoint's compliance counts (settings managed and on target) and its evaluation data
* Read alarms per tenant or endpoint: settings that drifted or failed to apply, and agent states
* Read each tenant's baselines and Senteon's baseline templates

Senteon's Public API is read-only, so Neo changes nothing in Senteon.

## Permission Groups

| Group | Covers |
| - | - |
| Tenants | Your tenants and their endpoint status counts |
| Endpoints & Compliance | Endpoints, their configuration health, compliance counts and evaluation data |
| Alarms | Drift, failed-setting and agent alarms |
| Baselines & Templates | Tenant baselines and Senteon's baseline templates |

## Access Profiles

| Profile | What runs on its own | What asks a technician |
| - | - | - |
| **Read Only** | Every read | Nothing: Neo makes no change in Senteon |

## Safety Controls

| Control | Behavior |
| - | - |
| **The ticket's customer only** | On a run for a ticket that names a company, Neo sends a call only for the tenant that company is mapped to (the `tenant` parameter), and refuses the list of every tenant |
| **Answers stay in the tenant** | Every answer is cut to the tenant a call names. An endpoint's compliance or evaluation is read only after Neo confirms the endpoint is in that tenant, because host names repeat across tenants |
| **Read-only** | Every call is a GET; Neo refuses any other |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.