Skip to main content
SiteGPT has developer tools for three kinds of work:
  • Control the widget on your own page. The widget SDK and tracking events run in the browser, next to the chat widget.
  • Get events out to your systems. Webhooks send messages, leads, and escalations to a URL you own.
  • Manage your account from code or an AI agent. The API v2, the SDKs, the CLI, and the MCP server all act on the same account data.

​
Browser surfaces

The widget SDK and tracking events need the chat widget on your page. See Add SiteGPT to your website to install it.

Widget SDK

Open and close the chat, send or prefill messages, add page context, sign in known visitors, and add CSS.

Tracking events

Send widget events such as chat_opened and lead_submitted to Google Tag Manager, GA4, or your own code.
These surfaces work only in the visitor’s browser. They do not need an API token. Identity verification is the one exception that needs a secret, and you use that secret only on your server.

​
Server-to-server events

Webhooks

SiteGPT sends a POST request to your URL for each message, lead, and escalation.
Webhooks push data to you as it happens. They are the best choice when another system must react to a new lead or an escalation. Webhooks are available on the Scale plan and above, or with the webhook add-on. See Plans and limits.

​
Account automation

The API v2, the SDKs, the CLI, and the MCP server all act on your account through API v2. Each one can do only what your dashboard role allows. They need the Growth plan or above. See Authentication. The A2A agent is different. It answers questions about SiteGPT and cannot access your account.

API v2

A REST API for chatbots, content, conversations, leads, settings, and members. Includes an OpenAPI document.

TypeScript SDK

@sitegpt/sdk, a typed client for API v2.

Python SDK

sitegpt, a client for API v2 that uses only the Python standard library.

Go SDK

A client for API v2 in Go.

Convex component

@sitegpt/convex, for answers and content sync in a Convex backend.

CLI

Manage chatbots from the terminal, in scripts, or through a coding agent.

MCP server

Connect AI assistants such as Claude or Cursor to your SiteGPT account.

A2A agent

Ask the SiteGPT support agent questions about SiteGPT from your own agent.

​
Which tool to use

​
Credentials

Each surface uses one kind of credential: Authentication explains tokens, scopes, access levels, device login, and the legacy API key.

​
API rules that apply to every call

API conventions describes the response format, pagination, errors, and delete confirmation. It also lists the errors that come from the conversation state, for example when your team has taken over a conversation. Conversations and handoff explains the conversation states.