Skip to main content
Synapse is the client SDK for MedAssist — Eka Care’s AI medical-assistant chat experience. Configure an agent once in the Eka Care console, then drop the assistant into your product at whatever level of control you need.
Synapse is the client counterpart to Echo Agent Kit (the server-side framework). Synapse connects your end users to an agent over a real-time session.

​
Three ways to integrate

Pick the tier that matches how much control you want. They build on each other — the embed widget wraps the React widget, which is built on the core SDK — so you can start simple and drop down a level whenever you need more control.
  1. Embed widget — the easiest path, for any website. A lightweight Web Component (<eka-medassist-widget>) you add with a single custom element and a script tag. No React, no build step — it works on plain HTML, WordPress, Webflow, or any framework. The widget assets are lazy-loaded when the user first opens the chat, so your page stays fast, and everything runs inside a Shadow DOM so its styles never clash with your site. The assistant appears as a floating button (or a fullscreen view). Best when you want it live in minutes.
  2. React SDK — the prebuilt UI, for React apps. The full, polished MedAssist chat interface as a React package. You mount it into any element with renderMedAssist(container, agentId, config) and get back a root you can unmount — or load the bundle from a CDN and call window.renderMedAssist. You get streaming replies, file/audio inputs, and tool components out of the box, all themeable to your brand with the Eka design system. Best when you’re already in React and want the ready-made widget rather than a Web Component.
  3. Core SDK — full control, for custom UIs. The TypeScript foundation both widgets are built on. It handles session management, the real-time WebSocket/SSE connection, message transport, tool calls, and audio — and emits everything as events (MESSAGE_CHUNK, TOOL_CALL, END_OF_STREAM…) so you can render your own message bubbles, inputs, and tool components. No UI is included. Best when you need a fully bespoke chat experience.

​
How they relate

​
Core concepts

Agent

An assistant you create in console.eka.care. Identified by an agentId — the one value every integration needs.

Session

A live connection between a user and the agent. Started once, then carries messages and events both ways.

Tool calls & elicitation

The agent can ask the UI to collect input (pills, OTP, doctor cards…) and run tools mid-conversation.

Environments

production (default), staging, or development — selects which backend the client talks to.

​
Start in the console

Every integration begins the same way:
1

Create an account

Sign up at console.eka.care.
New here? Follow the detailed setup guide to create your account and get authorized step by step.
2

Create an agent

Configure its persona, tools, theme, and initial message. This is stored in the backend.
3

Copy your agent ID

You’ll pass this agentId to whichever integration you choose.
Most customization — theme, title, initial message, allowed inputs — lives with the agent in the console, so the same agent looks consistent across every integration. You only override things in code when you need to.