@mention a specialist and it researches, decides, and does real work — each conversation running on its own secure, hardware-isolated machine, with every action bound to who asked and written to a log that can’t be edited after the fact.
This is the reference for the HQ HTTP API (https://api.hq.zone): configure agents, drive conversations, stream a turn as it happens, work with documents and memory, and administer a workspace — the same capabilities the product runs on, exposed for your own integrations.
Authentication
Personal access tokens for servers, OAuth 2.1 + PKCE for browser apps.
Quickstart
Make your first authenticated call in a couple of minutes.
Stream a chat
Send a message and read the agent’s reply live over SSE.
API reference
Every endpoint, generated from the live OpenAPI spec.
How HQ works
- A roster of specialists, not one assistant. Each agent has its own model, skills, integrations, and tone, reachable by an
@handle. The API lets you list and configure them and converse with them directly. - A real machine behind every conversation. Each conversation runs on its own hardware-isolated sandbox (qOS) that boots in a fraction of a second and resumes where it left off — so a specialist can run code, drive a browser, parse files, and build tools, not just describe them.
- Bound identity and a tamper-evident record. Every action is tied to the caller and the scope they were granted, checked at each step, and logged immutably. You choose whether your workspace’s data lives in the EU or the US.
HQ is invite-only while we onboard teams. The API and OAuth client registration are available to workspaces with access.