Bitcoinfinancier home-iot-api

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

Browse all Swaggerhub Bitcoinfinancier APIs

★ Only Publicly Available OpenAPI DocumentIOTHome Automationnone15 Endpoints

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.bitcoinfinancier%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.bitcoinfinancier%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

GET STARTED

Start building with home-iot-api

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use home-iot-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 Jentic?

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

Setup

Wiring the home-iot-api by hand means standing up its device and lighting endpoints, tracking which deviceId maps to which switch or dimmer, and handling request retries yourself. Through Jentic you install once, import the home-iot-api from the API Directory, and your agent calls it without you writing that plumbing.

Permission scoping

The API puts the deviceId in the URL path (/lighting/switches/{deviceId}, /lighting/dimmers/{deviceId}/{value}), 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 with POST /devices is not included unless you add it.

Credential isolation

This spec defines no authentication, so there is no credential to store. If you point it at a host that adds a key later, that key is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'turn on a light switch' or 'dim a lighting device', 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.

Bitcoinfinancier home-iot-api

Connect the home-iot-api to your agent

Capabilities

Start building with home-iot-api

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs