PATH
Install and first turn
Get started
is the shortest live path: install the client, bind the runtime, mint a token, call
session.send.
DOCS
Documentation
Reference for the client, host language SDKs, the runtime, and the wire. Copy is aligned to the source.
Get started
Two pieces: a JS client in the host, a Rust runtime beside it. This page is the shortest path to a live stream.
JS client
SvedaClient is the attach surface. Vue and web-component packages exist as optional UI — core does not require them.
Runtime
The binary is sveda-server. It is Axum. It is not in your application request cycle unless you choose to proxy it.
Deploy
Replicas are stateless. Histories and settings live in Postgres. Occupancy, throttle, and MCP creds live in Redis.
Stream protocol
One POST, one SSE response, a closed event list. Frontend vs backend tool.call targets.
MCP & tools
Three layers: builtin agent tools, client-registered frontend tools, and host MCP listed at token mint.
Models
The catalog is on the runtime. The client may pass model or provider on a turn; failover is still the ordered list.
Embed token
Tokens are HMAC, prefixed sveda_embed_, scoped to visitor_id. The host mints them. The browser only sends them.
How the docs are organized
These pages are a contract against the source: package names, route paths, event types, and env vars as they exist in
@sveda-ai/core
and
sveda-server.
CONTRACT
Client, runtime, stream
JS client, runtime, and stream protocol are the attach surface. Everything else hangs off this pair plus one SSE pipe.
ATTACH
Tools, models, auth
MCP and tools, models, and embed tokens document builtins, the catalog, and the host handshake. Language minting lives under Host SDKs.
Connect a host
Numbered install for each language, plus a path with no framework. Same
POST /sveda/session
JSON on every stack.
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.
PHP
Framework-agnostic PHP. Factory::factory() → embed()->createToken(). Your page only receives origin and token.
Laravel
The package wraps sveda-ai/client, mints Sanctum MCP tokens, and exposes StartSidecarSessionController.
Python
One client. Flask, Django, and FastAPI are route wrappers. start_host_session returns origin, token, expires_in, appearance.
Node
Native fetch. startHostSession talks to the sidecar. The page still opens chat with data-sveda-open buttons.
Ruby
The gem mints embed tokens with Bearer host auth. Rails is a controller and a layout. Plain Ruby is the same HTTP call.
Go
No framework required. net/http plus the module is the host. Templates only render chat buttons when the origin is set.
Java
HttpClient transport. Spring Boot is a controller and Thymeleaf. The SDK does not need Spring.
.NET
net8.0 Sveda.Client. ASP.NET is MapPost plus a layout. The library is usable from any HttpClient host.
Send the first turn.
Install @sveda-ai/core. Run sveda-server on 0.0.0.0:8787. Mint a token. Call session.send.