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
- MCP, for tool-using developer clients
Choose the surface that keeps credentials in the right place.
- For browser code, use the embed and its supported client actions.
- For backend services, 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 surfaces work together. Topics include authentication, pagination, rate limits, identity verification, and operational recovery. They do not duplicate every schema from the generated reference.
If you add chat to a site, start with the embed. If you automate AgentStack from a backend, start with REST API authentication. When a compatible coding or assistant client needs controlled access to agents, sources, or conversations, use MCP.
In this section
Use these guides based on your integration surface:
- Embed guides — page integration and browser events
- REST guides — resource workflows
- Webhooks — event capability discovery
- MCP guides — OAuth-connected clients