For developers
Build on Heybound with the same capabilities we use
Everything the product does is reachable through an open API. The contracts are typed and generated from OpenAPI and protobuf schemas, the agents you ship get the same capabilities the built-in ones have, and you can embed the whole chat surface in your own app. No walled garden, no second-class tier.
Open API
Everything the product does, reachable through an API
If the interface can do it, the API can too — conversations, cases, identities, history, and agents. REST for requests, a real-time channel for what needs to be live.
- Full coverage — every capability of the system is in the API.
- REST for requests; a real-time channel (WebSocket) for live updates.
- Fits your stack — call it from the systems you already run, no migration.
Typed SDKs
Typed SDKs that stay in sync
The API is described with OpenAPI (REST) and protobuf (real-time / WebSocket) schemas, and the SDKs are generated straight from them. They never drift from the API, and a wrong field or a renamed endpoint fails at compile time, not in production.
- OpenAPI describes the REST surface; protobuf the real-time / WebSocket one.
- SDKs are generated from those schemas — never hand-maintained.
- Always in sync — regenerate and you're current with the API.
- A wrong field or renamed endpoint fails at compile time, not in production.
Agents & marketplace
Build agents with full capability — and ship them to other teams
Outside agents connect to the same API and get the full set of capabilities internal agents have — no second-class integration tier. Build one for your own org, or publish it on the marketplace for other teams to install.
- Full parity — your agent reaches the same primitives the built-in ones do, through the open API.
- Post as itself or draft for a member; whisper privately; propose actions and wait for the green light.
- Publish to the marketplace — other teams install your agent the way they install Heybound's.
Chat SDK
Embed Heybound inside your own app
The Chat SDK ships the primitives — balloon rendering, real-time sync, attachments — so you drop a working conversation surface into your app instead of rebuilding one. Theme it to match your brand, and it runs on the same core as every other surface.
- Primitives, not a black box — balloons, sync, and attachments you compose.
- Themable to match your brand.
- Same core as every surface — a thread started in your app continues on web or mobile.
Start building on Heybound
Tell us what you're building and we'll get you API access, the SDKs, and a look at the agent surface — straight from our engineers.