Install Jentic One Beta

Connect the NoiseAware API to your agent

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

Authenticate hosts and partner integrations using bearer tokens with refresh and password reset flows

List noise events across an entire portfolio or filter by a specific property

Retrieve activity zones configured on a property to understand which sensors triggered alerts

GET STARTED

Start building with NoiseAware API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use NoiseAware API for, with concrete tasks.

★ Vacation rental noise complaint investigation

Property managers handling guest complaints from neighbours need to verify whether actual noise events occurred at the unit and when. The NoiseAware API exposes historical event lists per property and a graph data endpoint that returns decibel readings over time, so a manager or agent can pull the relevant window and confirm or dismiss the complaint without driving to the property. This typically replaces manual log review that would otherwise take hours of back-and-forth with the guest.

List events for property 12345 between 2026-06-08T22:00 and 2026-06-09T06:00 and return the peak decibel reading from the noise graph for that window

Multi-property portfolio monitoring

Property management companies operating dozens of vacation rentals need to surface only the units currently in violation rather than poll every property individually. The events list endpoint accepts portfolio-wide queries so an agent can fetch all events across registered properties, then filter to those above the manager's noise threshold to drive a single morning briefing.

Call /events/list to fetch all events from the past night across the host's portfolio and group them by property

Property onboarding automation

When a new vacation rental joins a property management roster, the host needs the unit registered in NoiseAware before sensors start reporting. The /properties/create endpoint accepts the address and configuration, while /properties/list lets the agent confirm the unit appears in the host's account. This bundles unit setup into the same workflow as listing the property on Airbnb or VRBO.

Create a new property in NoiseAware for the address '742 Ocean Drive, Miami FL' and verify it appears in the host's property list

AI agent escalation workflow

Through Jentic, an AI agent acting on behalf of a vacation rental host can monitor properties continuously and only escalate to a human when noise events cross thresholds. The agent searches Jentic for 'list noise events by property', loads the schema for /events/listByProperty, and runs the call on a schedule, then composes a guest message via a separate communications API when intervention is needed.

Through Jentic, search 'list noise events by property', load /events/listByProperty, and execute it for property 12345 every 30 minutes

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/events/list

List noise events across all properties

POST

/events/listByProperty

List noise events filtered by property

POST

/properties/create

POST

/properties/list

List all properties on the account

GET

/properties/get

Get a single property's details

GET

/properties/getGraphData

Retrieve historical noise graph data for a property

GET

/properties/getActivityZones

Get configured activity zones for a property

POST

/login

Authenticate a host and obtain a bearer token

POST

/events/list

List noise events across all properties

POST

/events/listByProperty

List noise events filtered by property

POST

/properties/create

POST

/properties/list

List all properties on the account

GET

/properties/get

Get a single property's details

GET

/properties/getGraphData

Retrieve historical noise graph data for a property

GET

/properties/getActivityZones

Get configured activity zones for a property

POST

/login

Authenticate a host and obtain a bearer token

Why Jentic?

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

Setup

Wiring NoiseAware by hand means handling its bearer auth, building requests against its versioned host (https://api.noiseaware.io/v2), and shaping its list and event payloads yourself. Through Jentic you install once, import the NoiseAware API from the API Directory, store the token once, and your agent calls it.

Permission scoping

NoiseAware routes its targets through the request body rather than the URL path, so scope by operation: limit the agent to the operations it needs, such as listing noise events and reading properties, and leave out creating a property unless you add it. You choose the operations it may call.

Credential isolation

Your NoiseAware 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 'list noise events for a property' or 'read a property's activity zones', and Jentic returns the matching NoiseAware operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using NoiseAware API through Jentic.

Why is there no official OpenAPI spec for NoiseAware API?

NoiseAware does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call NoiseAware 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 NoiseAware API use?

NoiseAware uses HTTP bearer token authentication. Tokens are obtained via /login and refreshed via /refresh; partner integrations use /token to mint scoped tokens. Through Jentic, the bearer token is held in the encrypted vault and never enters the agent's prompt context.

Can I retrieve noise events for a single property with the NoiseAware API?

Yes. Call POST /events/listByProperty with the property ID in the request body. The response returns events scoped to that property only, which is useful when investigating a complaint about a specific unit rather than scanning the whole portfolio.

What are the rate limits for the NoiseAware API?

NoiseAware does not publish explicit rate limits in its OpenAPI spec. Treat the API as commercially scoped to a host's property count and avoid polling /events/list more than once per minute per property; use /events/listByProperty for targeted queries instead.

How do I monitor noise events through Jentic?

Install the Jentic SDK with pip install jentic, then search 'list noise events by property', load the /events/listByProperty operation schema, and execute with the property ID. The full search-load-execute flow runs without you ever holding a NoiseAware bearer token in code.

Can the NoiseAware API trigger guest messages or take corrective action?

No. The API exposes monitoring data only - events, graph data, activity zones - not guest communication. Pair it with a messaging API such as Twilio or SendGrid to send guest warnings when a noise threshold is crossed.

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

Yes. Because you run Jentic One yourself, you set the rules that decide which NoiseAware operations and credentials the agent may use, and it can only call what you allow. NoiseAware passes its targets in the request body rather than the URL, so you scope by operation: grant read-only operations like listing noise events and retrieving properties, graph data, and activity zones, while withholding write operations such as creating or deleting a property. Only the operations you approve are ever exposed to the agent.

NoiseAware API

Name: NoiseAware API
Brand: NoiseAware API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticIOTSensor Databearer12 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Monitor short-term rental noise levels, list noise events by property, and manage NoiseAware properties on behalf of hosts and property managers.

Use for: I need to list all noise events for a vacation rental property in the last 24 hours, Retrieve the noise graph data for a property to investigate a guest complaint, Register a new short-term rental in NoiseAware so its sensors start reporting events, Get the activity zones configured on a NoiseAware property

Not supported: Does not handle guest messaging, smart-lock control, or property listing distribution - use for noise event monitoring at short-term rentals only.

Jentic publishes the only available OpenAPI specification for NoiseAware API, keeping it validated and agent-ready. NoiseAware monitors noise levels at short-term rental properties and vacation homes, surfacing decibel events, activity zones, and historical noise graphs so hosts can intervene before guests trigger neighbour complaints. The API exposes property registration, event listings filtered by property, and per-property graph data alongside authentication endpoints for partner integrations. It is used by property managers, vacation rental platforms, and home automation tools that need real-time noise alerts.

Jentic One on Github View OpenAPI Document

Connect the NoiseAware API to your agent

Capabilities

Start building with NoiseAware API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

NoiseAware API