// live chat for developer tools
Webhooks signed with HMAC, docs scraped automatically, deploy with one <script> tag.
Developer tools sell to developers. Developers don't want a chat widget that talks down to them; they want one that knows the docs, answers in code-comfortable language, and signs its webhooks so it can plug into their existing tooling without a vendor SDK. Generic live chat fails on all three: dumbed-down AI, knowledge base that requires manual entry, webhooks (when they exist) that ship unsigned.
Drop your docs site URL into the knowledge base and Agentbot indexes the live pages. Update a tutorial, the next conversation uses the new content. Combined with markdown uploads, the AI ends up with the same context your dev advocates would.
Every event (conversation, message, ticket) fires a signed webhook — HMAC SHA-256 over the raw body. Verify in three lines server-side, then pipe to Linear / GitHub / Discord / your own backend. The payload shape is published; no SDK required.
Configure the AI persona to match developer tone: it knows when to drop a code fence, when to link to a specific docs path, when to suggest an open issue instead of restating the docs. Configurable in the system prompt; no per-reply prompt engineering required.
Drop one line of script into your site head. The widget is live immediately; the AI starts answering once you upload your knowledge base. Full install docs →
<script src="agenbot.vercel.app/w/YOUR_SITE_KEY" defer></script>Every webhook ships with an X-Agentbot-Signature header — HMAC SHA-256 over the raw request body, signed with your secret. Three lines on your end to verify (HMAC the body, constant-time compare to the header). The payload shape and signature scheme are documented at /docs/webhooks.
Yes — enable web search and provide your docs URL. The AI fetches relevant pages live on every conversation turn. Combine with uploaded knowledge base entries for internal-only context (architecture, support runbooks, deprecation notes) that isn't on the public docs.
Yes, with sensible formatting. The system prompt is configurable — set the tone to 'developer audience' and the AI emits code fences with language tags, links to specific doc paths instead of just doc homepages, and drops the marketing-speak. The bundled markdown rendering displays code blocks correctly in the widget.
Via webhook. When the AI files a ticket, the ticket-created event fires; pipe it to Linear's API (via Zapier, n8n, or direct) to create an issue. Same for GitHub. We don't ship native Linear / GitHub integrations yet — webhooks cover the use case in 20 minutes of setup.
Agentbot itself is hosted (Vercel + Supabase). We don't currently offer a self-hosted distribution. The widget is one script tag and the data export gets your data out at any time, so the lock-in surface is small — but if you must self-host, we are not the right pick today.
Read-side API for conversations and tickets is on the roadmap. Today, the webhook surface covers most read-side needs (subscribe to events and stream them into your warehouse). For write operations (create a ticket via API, post a message via API), the API is being designed; reach out via /contact if you have a specific use case so we can prioritise.
One <script> tag. No credit card. See pricing.