Skip to content
SVEDA
Menu

HOST

Mint on the host. Open the chat from the page.

The browser never holds SVEDA_EMBED_HOST_API_KEY. Your backend calls POST /sveda/embed/token, then the page opens JS chat or an iframe.

Host SDK docs No framework

POST /sveda/session

host route

sveda_embed_

token prefix

9

language guides

The problem

A widget that mints tokens in the browser ships your host key. A Vue-only kit leaves PHP and Go hosts rewriting the handshake. The mint belongs on the server, in the language you already run.

Key in the page

SVEDA_EMBED_HOST_API_KEY stays on the sidecar and the host process. The page only receives origin + token.

One handshake

Every SDK returns origin, token, expires_in, appearance. sveda-host.js does not care which backend minted it.

Framework optional

Laravel, Django, Nest, Rails, Spring, ASP.NET are wrappers. PHP, Go, and a static page plus curl still work.

How to connect

Same five steps on every host. The language pages only change the install line and the mint helper.

  1. 1

    Run sveda-server

    Enable embed, set a host API key, and list the page origin in CORS.

  2. 2

    Install or skip

    Language SDK if you have a backend. No framework if you only need HTML plus a tiny POST.

  3. 3

    Match keys

    Host SVEDA_CLIENT_HOST_API_KEY equals sidecar SVEDA_EMBED_HOST_API_KEY.

  4. 4

    Mint on POST

    Expose POST /sveda/session. Return origin, token, expires_in.

  5. 5

    Open chat

    Page buttons data-sveda-open for JS or iframe.

Pick a language

Step-by-step install for each stack, plus a no-framework path.

HOST

No framework

A static page can open the chat. Something on your origin still has to mint the embed token — curl for local, or a tiny POST /sveda/session.

HOST

PHP

Framework-agnostic PHP. Factory::factory() → embed()->createToken(). Your page only receives origin and token.

HOST

Laravel

The package wraps sveda-ai/client, mints Sanctum MCP tokens, and exposes StartSidecarSessionController.

HOST

Python

One client. Flask, Django, and FastAPI are route wrappers. start_host_session returns origin, token, expires_in, appearance.

HOST

Node

Native fetch. startHostSession talks to the sidecar. The page still opens chat with data-sveda-open buttons.

HOST

Ruby

The gem mints embed tokens with Bearer host auth. Rails is a controller and a layout. Plain Ruby is the same HTTP call.

HOST

Go

No framework required. net/http plus the module is the host. Templates only render chat buttons when the origin is set.

HOST

Java

HttpClient transport. Spring Boot is a controller and Thymeleaf. The SDK does not need Spring.

HOST

.NET

net8.0 Sveda.Client. ASP.NET is MapPost plus a layout. The library is usable from any HttpClient host.

Related

No framework

HTML, iframe, tiny HTTP.

PHP

sveda-ai/client.

Laravel

sveda-ai/laravel-client.

Python

Flask, Django, FastAPI.

Node

Express, Nest, Next.

Ruby

Rails or plain Ruby.

Go

net/http, no framework.

Java

Spring Boot or Java 17.

.NET

ASP.NET Core or Sveda.Client.

Embed token

The mint contract.

Pick a host.

Nine step-by-step guides. Same session JSON. Same two chat openers.

Host SDK docs