Public API & MCP

eChat exposes a public surface for setting up, managing, training, and evaluating agents outside the dashboard: a REST API and an MCP gateway that share one contract. Use them when you want to automate agent setup, pull evaluation results into your own tools, or connect an MCP client (such as Cursor) to your eChat account.

This article covers where the app and API live, how to authenticate, what the docs include, and how MCP relates to REST — including the one thing MCP deliberately does not do.

Where the app and API live

What it is

Sign in to eChat with your eWebinar login to manage your agents in the dashboard. The API and its docs are served on eChat's API host, which you can open from Open API docs in the eChat dashboard.

How it works

Call the API and browse generated docs on the API host.

Best practices

Open the docs from Open API docs in the dashboard so you always reach the current API host.


API and MCP docs

What it is

Reference docs are generated from the same contract the server enforces, and they're served on the API host.

How it works

  • Docs landing page
  • REST reference (Redoc)
  • OpenAPI document
  • MCP tool reference

In the eChat dashboard, Open API docs opens this docs host. Authenticate with an eChat API key (Pro and higher, when your team has keys) or with eWebinar OAuth / a signed-in dashboard session — see the sections below and Signing In & Account Access.


Who can manage API keys

What it is

API keys unlock the public REST API and MCP for your team. They are available on Pro and higher plans.

How it works

Only team Admins (and Ops) can create, rename, and delete keys. Creators, Editors, and Moderators see Ask an admin for an API key in Deploy and cannot open Account settings → API keys. Below Pro, Admins see an upgrade card instead of the key list.

There are two kinds of key:

  • Agent keys — made in an agent's Deploy → API tab. They work with that agent only (its chat and /agents/:agentId/… routes, and a list of agents that holds only it). Team-wide actions such as creating agents or running evaluations need a key for all agents.
  • All-agents keys — made in Account settings → API keys. That page lists every key on the team with a badge: All agents, or the agent's name. Existing keys made before agent-scoped keys existed stay all-agents.

Keys keep working whoever made them; they act for the account, not the person.


REST API

What it is

One ts-rest contract describes every public route. API-key requests are validated against it; invalid input returns 400 with an issues list.

How it works

You can create and update agents, change settings, manage training sources, run evaluations, and more. Agent CRUD and settings are available under /agents (including PATCH /agents/:agentId and GET/PATCH /agents/:agentId/settings). API keys can reach agent CRUD, settings, training, and evals (all-agents keys for team-wide routes); they cannot delete agents or act through a person's eWebinar session.

Visitor chat stays REST-only. Sending a visitor message (POST /chatbots/:agentId/chat) is documented on REST but has no MCP tool — MCP is for setup, training, and evaluation, not for running live visitor chats.

Best practices

Start from the OpenAPI file or Redoc page rather than guessing paths. Prefer an agent key when a script only talks to one agent. For eWebinar-linked agents, eWebinar still connects through its own managed moderator path — API keys aren't required for that; see Deploying Your Agent.


MCP gateway

What it is

MCP (Model Context Protocol) is available at /mcp on the API host. It exposes tools for creating, configuring, training, and evaluating agents. Eval suite and run tools require the echat:evals permission.

How it works

Each MCP tool call runs through the same server path as the matching REST request, so auth, validation, and permissions match. You can authenticate with:

  • eChat API keys (Pro and higher) — person-only tools are hidden
  • eWebinar OAuth access tokens bound to eChat's MCP resource (dashboard-equivalent access; available on every plan)
  • Dashboard session tokens when you're already signed in

Best practices

Use MCP when an assistant or IDE should manage agents for you. Use REST when you want a simple HTTP integration or to send visitor chat messages. Keep API keys in your secret store, not in client-side code.


What this is not

The public API and MCP do not replace deploying an agent as an eWebinar AI moderator. For webinar chat, connect the agent in Deploy as usual. Image chat and third-party inbox bridges are separate features and aren't covered here.