Build on the API
The same endpoints the household console and the phone use, under /api/v1, with a key that reaches your own sandbox and nothing else. Rooms, devices, things, telemetry, commands, notifications.
ALYT Developers
One governed interface to the physical environment. Build the connections between intelligence and physical space—through rooms, capabilities, state, events and scoped controls.
Build a connector
Describe a device family with one descriptor and speak four routes. Reviewed by ALYT, and once approved it reaches every ALYT installation and keeps receiving your updates.
A sandbox that is the real platform
Not a crippled tier: your own tenant, a home with rooms, five virtual devices on the real broker, the same limits production enforces, free and metered from day one.
Written for you and your AI
Every page has a markdown twin and every catalogue a JSON twin. Start an agent at /llms.txt; start yourself at Get started.
Build on the environment
Section titled “Build on the environment”ALYT is the persistent context and execution layer for physical spaces, starting with the home. Instead of integrating every light, thermostat, access system, sensor and vendor cloud separately, build against supported rooms, capabilities, reported state, events and controls. Connectors normalize physical systems; application scopes govern access.
AI agents, autonomous software, OEM intelligence and physical-world applications can use the published contract today. Simone is ALYT’s own resident intelligence; voice is one interface to this environment. Richer contextual views and bounded agent proposals are in development and are not implied by the public REST API.
Robotics is a platform direction: a future robot could use an authorized machine-readable environment model alongside its own perception. This is not a deployed robot integration. Explore the environment-layer architecture.
Platform hosting is a separate choice from the hub model: ALYT can host the platform, or a customer can run a dedicated installation. The API contract, client library and capability descriptors remain the same; the base URL identifies the installation.
Events and execution
Section titled “Events and execution”Signed webhooks and a resumable Server-Sent Events stream expose supported platform events. Use the published API and application scopes; the internal MQTT transport is not a public device-control surface.
ALYT owns environment state. Intelligence proposes intent; platform permissions and capability contracts govern execution. A command acknowledgement is not proof of physical completion. Inspect reported state and command outcomes, and preserve uncertainty when an outcome cannot be confirmed.