Install Jentic One Beta

Connect the Omnidots Honeycomb API to your agent

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

Authenticate an API token and confirm scope before pulling measurement data

List all measuring points configured on the Omnidots account

List sensors associated with a measuring point and their configuration

Pull peak particle velocity (PPV) records for vibration compliance reporting

Pull VDV (Vibration Dose Value) records for human-comfort assessments

GET STARTED

Start building with Omnidots Honeycomb API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Omnidots Honeycomb API for, with concrete tasks.

★ Construction Site Vibration Compliance

Site managers monitoring against BS 7385 or DIN 4150 thresholds use GET /get_peak_records to pull peak particle velocity values, GET /get_vdv_records for vibration dose values, and GET /get_veff_records for the German Veff/KB metric. Records carry timestamps and measuring-point IDs so they can be aggregated into daily compliance reports.

GET /get_peak_records for measuring point 87 over the last 24 hours and aggregate values above the 5 mm/s threshold into a compliance summary.

Sensor Fleet Inventory

Operations teams running tens or hundreds of sensors across multiple sites use GET /list_measuring_points to enumerate active points and GET /list_sensors to map the sensor inventory at each. GET /configure_measuring_point returns the threshold and sampling configuration for each device, supporting audit and re-deployment workflows.

GET /list_measuring_points to enumerate all sites, then for each call GET /list_sensors and produce a CSV inventory of sensor IDs, locations, and configuration.

Forensic Waveform Analysis After an Alarm

When a vibration alarm fires near a critical structure, GET /get_traces_list returns the available trace records around that timestamp and GET /get_traces returns the detailed waveform sample data for forensic analysis. Engineering teams use this to determine whether a true threshold breach occurred or whether a transient (e.g. nearby traffic) triggered the alarm.

GET /get_traces_list for measuring point 87 between 14:25 and 14:35, then GET /get_traces for each trace ID to download waveform samples for review.

AI Agent Site Monitoring Assistant

An AI agent connected through Jentic can answer questions like 'were vibration thresholds exceeded yesterday on the Rotterdam project?' by calling GET /list_measuring_points and GET /get_peak_records, summarising the result. Jentic stores the API token and injects it on each call so the agent never sees the raw credential.

Search Jentic for 'get omnidots peak records', load /get_peak_records, and execute it for measuring point 87 over the last 24 hours.

Key Endpoints

11 endpoints — jentic publishes the only available openapi specification for omnidots honeycomb api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/list_measuring_points

List all measuring points

GET

/list_sensors

List sensors at a measuring point

GET

/get_peak_records

Get PPV records

GET

/get_vdv_records

Get VDV records

GET

/get_veff_records

Get Veff/KB records

GET

/get_traces

Get detailed waveform traces

GET

/list_measuring_points

List all measuring points

GET

/list_sensors

List sensors at a measuring point

GET

/get_peak_records

Get PPV records

GET

/get_vdv_records

Get VDV records

GET

/get_veff_records

Get Veff/KB records

GET

/get_traces

Get detailed waveform traces

Why Jentic?

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

Setup

Wiring the Omnidots Honeycomb API by hand means managing its API key as a query-string token and building each vibration readback call against honeycomb.omnidots.com yourself. Through Jentic you install once, import the Omnidots Honeycomb API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The Omnidots Honeycomb endpoints are read-only listings of measuring points, sensors, and peak, VDV, Veff, and trace records, so you limit the agent to the operations it needs, such as list_measuring_points or get_peak_records. It reads measurement data and does nothing else unless you add operations to the allowed set.

Credential isolation

Your Omnidots token 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 'get omnidots peak records' or 'list omnidots measuring points', and Jentic returns the matching Omnidots operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Omnidots Honeycomb API through Jentic.

Why is there no official OpenAPI spec for Omnidots Honeycomb API?

Omnidots does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Omnidots Honeycomb API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Omnidots Honeycomb API use?

Every request includes a token query parameter issued from the Honeycomb account. Jentic stores this token in its encrypted vault and appends it on each call, so agents reference a credential handle rather than the raw token string.

Can I export waveform traces around a vibration alarm?

Yes. GET /get_traces_list returns trace records inside a time window and GET /get_traces returns the underlying waveform samples for forensic review. Use both endpoints to drill from alarm timestamp to raw signal.

What are the rate limits for the Omnidots Honeycomb API?

Rate limits are not declared in the OpenAPI spec. In practice the API is intended for periodic polling rather than per-second pulls - fetch records on a 5-minute or 15-minute schedule for compliance reporting.

How do I check vibration thresholds via Jentic?

Search Jentic for 'get omnidots peak records', and the SDK returns GET /get_peak_records. Pass the measuring point ID and a date range, and the agent receives the records ready for threshold comparison.

Does the Omnidots Honeycomb API include real-time alerting?

No. Real-time alerting and SMS/email push are configured inside the Omnidots Honeycomb portal and webhook integrations. The API is for pulling stored measurement data and waveform traces.

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

Yes. Because you run Jentic One yourself, your own rules decide which Omnidots Honeycomb operations and credentials the agent may use, and the API is read-only to begin with. You can restrict the agent to just the operations it needs, such as list_measuring_points, list_sensors, or get_peak_records, and leave everything else out of the allowed set. The agent reads measurement and trace data and does nothing more unless you explicitly add operations to that set.

Omnidots Honeycomb API

Name: Omnidots Honeycomb API
Brand: Omnidots Honeycomb API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticIOTSensor DataapiKey11 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Read vibration sensor measurements (peak particle velocity, VDV, Veff/KB) and device traces from Omnidots Honeycomb sensors deployed on construction and demolition sites.

Use for: Get the latest peak vibration records for our Amsterdam construction site, List all measuring points on our Omnidots account, Retrieve VDV measurements over the last 24 hours, Check whether my API token is still valid

Not supported: Does not handle device provisioning, alert routing, or noise (dB) monitoring - use for vibration measurement readback only.

Jentic publishes the only available OpenAPI specification for Omnidots Honeycomb API, keeping it validated and agent-ready. The Omnidots Honeycomb API is the data interface for Omnidots' vibration-monitoring platform used on construction sites, demolition projects, and industrial installations to track ground vibrations against safety thresholds. It exposes 11 endpoints for authenticating tokens, listing measuring points and sensors, configuring devices, and pulling peak particle velocity, VDV, and Veff/KB measurement records along with detailed waveform traces. Authentication uses a token query parameter.

Jentic One on Github View OpenAPI Document