Developers
Build reliable AgentStack integrations with the embed, REST API, webhooks, and MCP.
AgentStack has four integration surfaces: the browser embed for a hosted chat experience, the REST API for server-side automation, webhooks for setup and event discovery, and MCP for tool-using developer clients. Choose the surface that keeps credentials in the right place. Browser code should use the embed and its supported client actions; backend services should keep API keys on the server and call the REST API.
The generated API reference at /reference is the source for request and response schemas. Its OpenAPI document is available at /api/v1/openapi.json. These guides explain how the pieces fit together, including authentication, pagination, rate limits, identity verification, and operational recovery. They deliberately avoid duplicating every schema from the generated reference.
Start with the embed if you are adding chat to a site. Start with REST API authentication if you are automating AgentStack from a backend. Use MCP when a compatible coding or assistant client needs controlled access to agents, sources, and conversations.
In this section
Use the Embed guides for page integration and browser events, the REST guides for resource workflows, Webhooks for event capability discovery, and the MCP guides for OAuth-connected clients.