Skip to main content

Integrations

Secure Chat Integration

Secure Chat exposes a published agent through an authenticated chat API. Requests must be authorized with a workspace API key.

What It Enables

Secure Chat is a good fit when you want:

  • server-to-server integration
  • controlled access from internal tools
  • a stable API key boundary per workspace

Access Control

Secure Chat requires a workspace API key that matches the workspace in the request.

When To Use Secure vs Public

  • Choose Public Chat for website embeds and public entry points with strict origin controls.
  • Choose Secure Chat for authenticated traffic and system integrations where API key auth is required.