Agent API
Connect an external support agent without coupling it to the widget runtime.
RespondKit keeps the AI agent outside the core message pipeline. This lets each product run an isolated agent beside its source code, documentation, product tools, and operating manual.
Intended integration
An external agent can:
- consume new thread messages;
- inspect the supplied product and customer context;
- use product-specific read-only tools;
- draft or send an English response when confidence is high;
- let RespondKit translate and deliver the customer-facing reply.
The first public API surface focuses on client sessions, threads, messages, and polling. A pull consumer for long-running coding agents is planned after the base operator loop is stable.
Product isolation
Use one inbox and one agent configuration per product. The thread context exposes the identifiers the integration supplied, while the agent remains responsible for its own prompts, documentation, source access, and operational policies.