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
The eChat dashboard is at https://app.ewebinar.chat. The API (and its docs) is at https://api.ewebinar.chat. Older hosts such as echat.ewebinar.com redirect to the app host and keep the path and query.
How it works
Open the dashboard at app.ewebinar.chat. Call the API and browse generated docs on the API host. Websocket, media, and email hosts stay on echat.ewebinar.com — you only need the new app and API hosts for the dashboard and public API.
Best practices
Bookmark app.ewebinar.chat and the docs landing page below. Update any scripts that still point at older API hostnames.
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
- https://api.ewebinar.chat/docs — docs landing page
- /docs/rest — REST reference (Redoc)
- /docs/openapi.json — OpenAPI document
- /docs/mcp — MCP tool reference
In the eChat dashboard, Open API docs opens this docs host. Account API Keys (Pro and higher) live at /settings/api-keys — see Signing In & Account Access.
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; 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. 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 roughly 95 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.