Install Jentic One Beta

Connect the home-iot-api to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the home-iot-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%2Fswaggerhub.gmacem%2Fhome-iot-api" | 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%2Fswaggerhub.gmacem%2Fhome-iot-api" | 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 home-iot-api.

getDevices

setDimmer

getSwitchState

setSwitch

Use Cases

Patterns agents use home-iot-api for, with concrete tasks.

GET STARTED

Start building with home-iot-api

Explore with Jentic One

View OpenAPI Document

Automated Device Management

Automate device operations by combining multiple home-iot-api endpoints. Agents can getdevices and then setdimmer in a single workflow.

Call GET /devices to getdevices, then verify the result

AI Agent Integration via Jentic

AI agents discover and call home-iot-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 none tokens manually.

Search Jentic for 'register', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

15 endpoints — the api for the eatbacon iot project.

METHOD

PATH

DESCRIPTION

POST

/devices

GET

/devices

getDevices

POST

/lighting/dimmers/{deviceId}/{value}

setDimmer

POST

/lighting/dimmers/{deviceId}/{value}/timer/{timeunit}

setDimmerTimer

GET

/lighting/switches/{deviceId}

getSwitchState

POST

/lighting/switches/{deviceId}/{value}

setSwitch

POST

/lighting/switches/{deviceId}/{value}/timer/{minutes}

setSwitchTimer

GET

/lightingSummary

getLightingSummary

POST

/devices

GET

/devices

getDevices

POST

/lighting/dimmers/{deviceId}/{value}

setDimmer

POST

/lighting/dimmers/{deviceId}/{value}/timer/{timeunit}

setDimmerTimer

GET

/lighting/switches/{deviceId}

getSwitchState

POST

/lighting/switches/{deviceId}/{value}

setSwitch

POST

/lighting/switches/{deviceId}/{value}/timer/{minutes}

setSwitchTimer

GET

/lightingSummary

getLightingSummary

Why Jentic?

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

Setup

Wiring the home-iot-api by hand means coding device registration and the lighting dimmer and switch controls against its virtual host and handling responses and retries yourself. Through Jentic you install once, import home-iot-api from the API Directory, store the connection once, and your agent calls it.

Permission scoping

The home-iot-api puts the device id in the URL path (/lighting/switches/{deviceId} and /lighting/dimmers/{deviceId}), so a rule can pin your agent to one device: it can read and set that device and nothing else. You choose the operations it may call, so registering new devices or timed controls are not included unless you add them.

Credential isolation

This API declares no authentication, so there is no secret to hand around; any connection settings are held once by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'turn on a light switch' or 'set a dimmer level', and Jentic returns the matching home-iot-api operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using home-iot-api through Jentic.

What authentication does the home-iot-api use?

The home-iot-api uses no 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 register with the home-iot-api?

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

What are the rate limits for the home-iot-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 register through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'register'. Jentic returns the matching home-iot-api operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the home-iot-api have?

The home-iot-api exposes 15 endpoints covering device, environment, z-wave operations.

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

Yes. Because you run Jentic One yourself, you write the rules that decide which Home IoT API operations and connection settings your agent may use. Since the device id sits in the URL path for calls like GET /lighting/switches/{deviceId} and POST /lighting/dimmers/{deviceId}/{value}, you can pin the agent to a single device so it only reads and sets that one and nothing else. You choose the operations it may call, so registering new devices with POST /devices or setting timed controls stays off unless you add it.

Gmacem home-iot-api

Name: home-iot-api
Brand: home-iot-api
Availability: InStock

Browse all Swaggerhub Gmacem APIs

Community OpenAPI document · agent-readyIOTHome Automationnone15 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically register, getdevices. Covers 15 operations.

Use for: I need to register, I want to getdevices, Search for setdimmer, Find all setdimmertimer

Not supported: Does not handle payments, communications, or crm - use for iot and hardware only.

The API for the EatBacon IOT project. The API exposes 15 endpoints.

Jentic One on Github View OpenAPI Document

Connect the home-iot-api to your agent

Capabilities

Use Cases

Start building with home-iot-api

Key Endpoints

Why Jentic?

Related APIs

FAQs

Gmacem home-iot-api