Google Home

Name: Google Home API
Brand: Google Home
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTHome AutomationapiKey30 EndpointsREST

For Agents

Read and control Google Home and Nest speakers over the local network: query device info, manage alarms and timers, scan for Bluetooth devices, and trigger setup actions.

Connect the Google Home to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Google Home, 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 Google Home API.

Discover Google Home devices on the local network and read their app device ID, supported locales, and timezones

Inspect the assistant readiness state to decide whether a device can accept voice or cast commands

List, create, and delete alarms and timers on a specific Google Home or Nest speaker

Scan for nearby Bluetooth devices and trigger pairing from the speaker side

GET STARTED

Start building with Google Home API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Google Home, keeping it validated and agent-ready. The Google Home Local API exposes the local HTTP control surface used by the Google Home app to communicate with Google Home and Nest speaker devices on the same network. It covers device discovery, assistant readiness checks, alarms and timers, Bluetooth pairing, network setup, and supported locales and timezones. The endpoints are reverse-engineered from the Home app and require a cast-local-authorization-token retrieved from the Google account that owns the device.

Use Cases

Patterns agents use Google Home API for, with concrete tasks.

★ Local Smart Home Dashboard

Build a local-network dashboard that lists every Google Home and Nest speaker, shows current alarms and timers, and surfaces assistant readiness state. The Google Home Local API is reached over HTTP on the device IP with a cast-local-authorization-token, so the dashboard works without round-tripping through Google's cloud and stays responsive on the LAN.

Discover all Google Home devices on the 192.168.1.0/24 subnet and return a JSON list of each device's app device ID, supported locale, and active alarms.

Bedtime and Wake Routines

Manage alarms and timers on Google Home and Nest speakers programmatically as part of a home automation routine. The local alarms endpoints let an automation set a wake alarm at 06:30, clear leftover timers from yesterday, and confirm the change without depending on the Google Assistant cloud.

Create a 06:30 weekday alarm on the bedroom Google Home Mini and delete any existing alarms scheduled before that time.

Bluetooth Pairing Helper

Trigger Bluetooth scans and pairing flows on a Google Home speaker from another device. This is useful for headless setup or for home automation routines that need to pair a phone or wearable with a specific speaker without using the Home app UI.

Initiate a Bluetooth scan on the living room Google Home and return the list of nearby devices with signal strength.

AI Agent Local Smart Home Control

An AI agent running on a home server uses the Google Home Local API through Jentic to read speaker state, check assistant readiness, and adjust alarms in response to natural language commands. Jentic stores the cast-local-authorization-token securely and exposes typed operations so the agent never has to parse the unofficial documentation directly.

When the user says 'cancel my morning alarm', look up the bedroom Google Home, list alarms scheduled before 09:00, and delete the first matching alarm.

Key Endpoints

30 endpoints — jentic publishes the only available openapi specification for google home, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/setup/get_app_device_id

Get the app device ID of a Google Home

GET

/setup/supported_timezones

List supported timezones on the device

GET

/setup/supported_locales

List supported locales on the device

GET

/setup/assistant/check_ready_status

Check whether the assistant is ready to accept commands

GET

/setup/offer

Read the current cast offer and active media state

GET

/setup/get_app_device_id

Get the app device ID of a Google Home

GET

/setup/supported_timezones

List supported timezones on the device

GET

/setup/supported_locales

List supported locales on the device

GET

/setup/assistant/check_ready_status

Check whether the assistant is ready to accept commands

GET

/setup/offer

Read the current cast offer and active media state

Why Jentic?

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

Credential isolation

The cast-local-authorization-token is stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped execution rights — the raw token never enters the agent's context, and rotation is handled centrally.

Intent-based discovery

Agents search by intent (e.g., 'list google home alarms') and Jentic returns matching local API operations with input schemas, so the agent calls the right endpoint without needing to read the GHLocalApi documentation.

Time to first call

Direct Google Home Local API integration: 1-2 days to capture the auth token, parse the unofficial docs, and handle device discovery. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Google Home API through Jentic.

Why is there no official OpenAPI spec for Google Home?

Google does not publish an OpenAPI specification for the Google Home Local API — it is an undocumented surface used by the Home app. Jentic generates and maintains this spec from the GHLocalApi reverse-engineering project so that AI agents and developers can call Google Home via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Google Home Local API use?

Each request must include a cast-local-authorization-token header bound to the Google account that set up the speaker. The token is short-lived and must be refreshed via Google's account services. Jentic stores the token in its encrypted vault and injects it at request time so the raw value never enters the agent's context.

Can I set alarms on a Google Home speaker through this API?

Yes. The /setup/assistant/alarms endpoints let you list existing alarms and create or delete entries on a specific device, and /setup/assistant/timers covers the equivalent timer operations. Each call targets one device by IP, so the agent must first discover the speaker on the local network.

What are the rate limits for the Google Home Local API?

Google does not publish rate limits for the local API because it is intended to be reached over the LAN by a single Home app instance. In practice, polling more than once every few seconds per device can cause the speaker to drop the connection, so back off after any 5xx response.

How do I list alarms on a Google Home speaker through Jentic?

Run jentic search 'list google home alarms', load the returned operation schema, and execute it with the device's local IP and the stored cast-local-authorization-token. The agent receives a typed list of alarm objects with fire time, recurrence, and ID, ready to be used in subsequent delete or update calls.

Does the API work over the internet or only on the local network?

The Google Home Local API only responds on the same LAN as the speaker — port 8443 on the device's IP. It is not reachable from the public internet, so any agent using it must run on a host inside the home network or via a VPN tunnel.