home-iot-api

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

★ Only Publicly Available OpenAPI DocumentIOTHome Automationnone15 EndpointsREST

For Agents

Programmatically register, getdevices. Covers 15 operations.

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

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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 API.

getDevices

setDimmer

getSwitchState

setSwitch

GET STARTED

Start building with home-iot-api API

Explore with Jentic

View OpenAPI Document

Use Cases

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

★ IoT and Hardware Operations

Use the home-iot-api to perform iot operations programmatically. The API provides 15 endpoints covering core functionality including register, getdevices, setdimmer.

Call POST /devices to register

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

home-iot-api none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'register') and Jentic returns the matching home-iot-api operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct home-iot-api integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Particle

Alternative iot API

Choose Particle when you need a different approach to iot operations

Complementary

Stripe

Complementary API for broader integration workflows

Use alongside home-iot-api for multi-service workflows

Complementary

Twilio

Complementary API for broader integration workflows

Use alongside home-iot-api for multi-service workflows

FAQs

Specific to using home-iot-api 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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.