Install Jentic One Beta

Connect the Thruk REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Thruk REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fthruk.org%2Fthruk" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fthruk.org%2Fthruk" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Thruk REST API.

List all hosts

Get a specific host

Schedule downtime for a host

Query and filter Thruk REST API records by parameters

Monitor Thruk REST API operational status and events

GET STARTED

Start building with Thruk REST API

Explore with Jentic One

View OpenAPI Document

Automated Alerts Management

Automate alerts operations by combining multiple Thruk REST API endpoints. Agents can get a specific host and then schedule downtime for a host in a single workflow.

Call GET /hosts/{name} to get a specific host, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Thruk REST API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, basic tokens manually.

Search Jentic for 'list all hosts', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

42 endpoints — thruk rest api exposes monitoring data from naemon, nagios, icinga, and shinken monitoring systems.

METHOD

PATH

DESCRIPTION

GET

/hosts

List all hosts

GET

/hosts/{name}

Get a specific host

POST

/hosts/{name}/cmd/schedule_host_downtime

Schedule downtime for a host

GET

/services

List all services

GET

/hosts/{hostName}/services/{description}

Get a specific service

GET

/hostgroups

List all host groups

GET

/servicegroups

List all service groups

GET

/contacts

List all contacts

GET

/hosts

List all hosts

GET

/hosts/{name}

Get a specific host

POST

/hosts/{name}/cmd/schedule_host_downtime

Schedule downtime for a host

GET

/services

List all services

GET

/hosts/{hostName}/services/{description}

Get a specific service

GET

/hostgroups

List all host groups

GET

/servicegroups

List all service groups

GET

/contacts

List all contacts

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Thruk REST API by hand means choosing between its X-Thruk-Auth-Key header and basic auth, filling in the {server} host for your own Thruk install, and building the host and service calls yourself. Through Jentic you install once, import the Thruk REST API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Thruk puts the host name in the URL path (/hosts/{name}, /hosts/{name}/cmd/schedule_host_downtime), so a rule can pin your agent to one host: it can read that host and its services and nothing else. You choose the operations it may call, so state-changing ones like scheduling host downtime are not included unless you add them.

Credential isolation

Your Thruk credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list all hosts' or 'schedule host downtime', and Jentic returns the matching Thruk REST API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Thruk REST API through Jentic.

What authentication does the Thruk REST API use?

The Thruk REST API uses apiKey, basic authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I list all hosts with the Thruk REST API?

Yes. Use the GET /hosts endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Thruk REST API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I list all hosts through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list all hosts'. Jentic returns the matching Thruk REST API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Thruk REST API have?

The Thruk REST API exposes 42 endpoints covering alerts, checks, cmd operations.

Can I limit what my agent is allowed to do with the Thruk REST API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Thruk operations and credentials the agent may use. Because Thruk puts the host name in the URL path (for example /hosts/{name} and /hosts/{name}/cmd/schedule_host_downtime), you can pin the agent to a single host and let it read only that host and its services. State-changing calls such as scheduling host downtime are not available to the agent unless you explicitly allow them.

Thruk REST API

Name: Thruk REST API
Brand: Thruk REST API
Availability: InStock

Official vendor OpenAPI document · agent-readyCommunicationsPush NotificationsapiKey, basic42 EndpointsREST

For Agents

Programmatically list all hosts, get a specific host. Covers 42 operations with apiKey, basic authentication.

Use for: I need to all hosts, I want to a specific host, Search for schedule downtime for a host, Find all all services

Not supported: Does not handle payments, crm, or developer tools - use for communications only.

Thruk REST API exposes monitoring data from Naemon, Nagios, Icinga, and Shinken monitoring systems. It provides access to hosts, services, hostgroups, servicegroups, contacts, commands, downtimes, comments, notifications, and more. The API exposes 42 endpoints secured with apiKey, basic authentication.

Jentic One on Github View OpenAPI Document

Connect the Thruk REST API to your agent

Capabilities

Start building with Thruk REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Thruk REST API