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
An assistant as capable as the cloud ones, running on hardware the household owns. Build on it, or build the connector that brings your devices into it.
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.
What this platform is
Section titled “What this platform is”ALYT runs speech, reasoning and control on hardware in the house. A developer’s portal usually graduates you to a bigger cloud plan; this one graduates you to owning the infrastructure. The contract, the client library and the capability descriptors are the same whether ALYT hosts your tenant or you run the platform in your own building. Only the base URL changes.
Honest about what exists
Section titled “Honest about what exists”The platform behind this site runs a real house today. Accounts, keys, the sandbox with virtual devices, the gateway with its limits, connector submission and review, the generated SDKs and the changelog are built and proven. Webhooks and the event stream are being built next, and every page here says so where it matters rather than promising.