Install Jentic One Beta

Connect the openITCOCKPIT API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the openITCOCKPIT 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%2Fopenitcockpit.io%2Fopenitcockpit" | 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%2Fopenitcockpit.io%2Fopenitcockpit" | 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 openITCOCKPIT API.

Provision new hosts and services into the monitoring configuration without using the web UI

List the current state of hosts and services to feed an alerting or reporting agent

Schedule downtime windows for planned maintenance to suppress alerts

Acknowledge active host or service problems so they stop paging on-call

Manage contacts and host groups to route alerts to the right teams

GET STARTED

Start building with openITCOCKPIT API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use openITCOCKPIT API for, with concrete tasks.

★ Maintenance Window Automation

Before a scheduled deployment, an agent can call POST /downtimes.json to suppress alerts on the affected hosts and services for the duration of the maintenance window. After the change is verified, the downtime can be removed or allowed to expire. This avoids paging on-call for self-inflicted alarms during deploys.

Schedule a 60-minute downtime starting now on the host with name 'app-prod-01' and all of its services so that planned restart alerts are suppressed.

Bulk Host Provisioning from Infrastructure-as-Code

When new servers are provisioned, an agent or pipeline can POST to /hosts.json and /services.json to create the matching monitored host and its standard service checks. This keeps the monitoring configuration in lockstep with the actual estate and removes the manual UI step that often lags behind infrastructure changes.

Create a new host named 'app-prod-04' in the 'production' host group and add three standard services for ping, disk, and HTTP checks to it.

On-Call Triage with Acknowledgements

When an alert fires, an on-call agent can list active problems through GET /services.json with a state filter, then POST to /acknowledgements.json to mark a chosen problem as acknowledged with a comment. This stops the alert from re-paging while the human investigates and keeps an audit trail of who acknowledged what.

Find the service with active CRITICAL state on host 'app-prod-01' and POST an acknowledgement with the comment 'investigating' so it stops re-notifying.

AI Agent Monitoring Operations via Jentic

An agent can take operator language like 'silence alerts on the payments box for an hour' and translate it into the right openITCOCKPIT calls. Through Jentic the API key is vaulted, the agent searches by intent rather than parsing the spec, and every call is auditable.

Use Jentic to search for 'schedule a downtime in openITCOCKPIT', execute POST /downtimes.json for the named host with a 60-minute duration, and confirm the response status indicates success.

Key Endpoints

25 endpoints — openitcockpit is an open-source it monitoring platform built on the nagios and naemon engines.

METHOD

PATH

DESCRIPTION

GET

/hosts.json

List all hosts

POST

/hosts.json

Create a host

GET

/services.json

List all services

POST

/services.json

Create a service

POST

/downtimes.json

Schedule a downtime window

POST

/acknowledgements.json

Acknowledge a host or service problem

GET

/contacts.json

List contacts

GET

/hosts.json

List all hosts

POST

/hosts.json

Create a host

GET

/services.json

List all services

POST

/services.json

Create a service

POST

/downtimes.json

Schedule a downtime window

POST

/acknowledgements.json

Acknowledge a host or service problem

GET

/contacts.json

List contacts

Why Jentic?

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

Setup

Wiring the openITCOCKPIT API by hand means pointing at your self-hosted instance host, sending the Authorization header with your API key, and mapping monitoring actions onto its .json endpoints. Through Jentic you install once, import the openITCOCKPIT API from the API Directory, store the key once, and your agent calls it.

Permission scoping

You limit the agent to the operations it needs, such as listing hosts or scheduling a downtime. You choose which operations it may call, so changes like creating hosts or services are not included unless you add them.

Credential isolation

Your openITCOCKPIT API key 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 'schedule a downtime' or 'list hosts in a critical state', and Jentic returns the matching openITCOCKPIT operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using openITCOCKPIT API through Jentic.

What authentication does the openITCOCKPIT API use?

API key authentication via the Authorization header. Through Jentic the key is stored in your Jentic One instance and added to each request automatically, so it is not exposed to the agent.

Can I schedule maintenance downtimes with the openITCOCKPIT API?

Yes. POST /downtimes.json accepts a host or service identifier, a start time, and a duration to suppress alerts during a planned change window.

What are the rate limits for the openITCOCKPIT API?

openITCOCKPIT is self-hosted, so there is no central rate limit imposed by a SaaS provider. Practical limits depend on the size of the host running the platform; avoid bursty bulk creates against a small instance and use host groups to apply settings to many hosts at once.

How do I acknowledge an active alert with the openITCOCKPIT API through Jentic?

Search Jentic for 'acknowledge an openitcockpit alert', load POST /acknowledgements.json, and execute it with the host or service identifier and a comment. Jentic injects the API key from the vault.

Is openITCOCKPIT free?

openITCOCKPIT is open-source and free to self-host. The vendor offers paid support and an enterprise edition with extra features; the API itself is the same in the community and enterprise editions.

Can I provision new hosts and services via the openITCOCKPIT API?

Yes. POST /hosts.json creates a host and POST /services.json creates a service tied to a host, so the monitoring configuration can be managed from infrastructure-as-code rather than the web UI.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which openITCOCKPIT operations and credentials the agent may use. You can allow it read-only calls like GET /hosts.json and GET /services.json, or add scheduling actions such as POST /downtimes.json and POST /acknowledgements.json, while leaving out write operations like POST /hosts.json and POST /services.json that create hosts or services. The agent can only call the operations you have granted it.

openITCOCKPIT API

Name: openITCOCKPIT API
Brand: openITCOCKPIT API
Availability: InStock

Official vendor OpenAPI document · agent-readyDeveloper ToolsMonitoring ObservabilityapiKey25 EndpointsREST

For Agents

Manage hosts, services, contacts, downtimes, and acknowledgements on a self-hosted openITCOCKPIT monitoring server, and query its monitoring status data.

Use for: List all hosts currently in a CRITICAL state, Create a new host entry for a server we just provisioned, Schedule a 2-hour downtime on the database service starting now, Acknowledge the active alert on the web frontend service

Not supported: Does not handle log aggregation, application performance monitoring, or hosted SaaS observability - use for self-hosted host and service monitoring management only.

openITCOCKPIT is an open-source IT monitoring platform built on the Nagios and Naemon engines. The REST API exposes the full configuration and runtime surface needed to manage a monitored estate: hosts, services, contacts, commands, time periods, host groups, service groups, downtimes, acknowledgements, and the data backing Grafana dashboards. Authentication is by API key in the Authorization header, and the base URL is the operator's own openITCOCKPIT host since the platform is self-hosted.

Jentic One on Github View OpenAPI Document

Connect the openITCOCKPIT API to your agent

Capabilities

Start building with openITCOCKPIT API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

openITCOCKPIT API