A roster of specialists, by API
List and configure agents, then converse with them directly: post a message, stream the reply live over SSE, interrupt or nudge a turn in flight. The same loop the product runs on.
Developers
The same decision intelligence your team @mentions in Slack and Teams, as an HTTP API. Configure specialists, drive conversations and stream a turn as it happens, and work with documents, memory, and schedules, with bound identity and an immutable audit on every call.
Base URL https://api.hq.zone · OpenAPI 3.1 · personal access tokens for servers,
OAuth 2.1 + PKCE for apps.
Why build on HQ
List and configure agents, then converse with them directly: post a message, stream the reply live over SSE, interrupt or nudge a turn in flight. The same loop the product runs on.
Each conversation runs on its own hardware-isolated qOS sandbox that boots in a fraction of a second and resumes where it left off. A specialist can run code, drive a browser, and parse files, not just describe them.
Extend any specialist with your own MCP servers and skills. The agents speak the Model Context Protocol natively, so what your integration can hand off keeps growing without a release to wait on.
Every call is tied to the caller and the scope it was granted, checked at each step, and written to a log that cannot be edited after the fact. Choose whether the workspace data lives in the EU or the US.
What you can build
Every endpoint is generated from the live OpenAPI spec, with guides and an interactive reference in the docs.
Authentication, a two-minute quickstart, guides, and the full API reference live at docs.hq.zone. HQ is invite-only while we onboard teams; the API and OAuth client registration are available to workspaces with access.