@voice-session/web 0.1.0 → 0.2.0

package/README.md

@@ -2,7 +2,7 @@
 
 Browser SDK for starting a realtime voice session with an AI assistant.
 
-The package talks to **your API host**. Pass `baseUrl` yourself. There is no default host.
+Mint `{ url, token }` on **your server**. Pass those values into the SDK. Never put the API key in frontend code.
 
 ## Install
 
@@ -12,8 +12,6 @@ npm i @voice-session/web
 
 ## Server
 
-Your backend mints a short-lived `client_token` with your API key, then the browser SDK exchanges it. Never put the API key in frontend code.
-
 ```bash
 curl -X POST "$API_HOST/api/user/realtime/session" \
   -H "Authorization: Bearer $API_KEY" \
@@ -26,21 +24,20 @@ Response:
 ```json
 {
   "id": "session-uuid",
-  "client_token": "opaque-token"
+  "url": "wss://example.invalid",
+  "token": "short-lived-token",
+  "expires_in": 900
 }
 ```
 
-Tokens expire in 15 minutes. Pass `baseUrl` as the same API host (scheme + host, no trailing path).
+Tokens expire in 15 minutes. Start the browser session before they expire.
 
 ## Browser
 
 ```ts
 import { RealtimeSession } from "@voice-session/web";
 
-const session = new RealtimeSession({
-  baseUrl: "https://api.example.com",
-  clientToken,
-});
+const session = new RealtimeSession({ url, token });
 
 session.on("agent_state", (state) => {
   console.log(state);
@@ -70,14 +67,6 @@ await session.end();
 | `ended` | none |
 | `error` | `Error` |
 
-### Direct credentials
-
-If your backend already exchanged the session and you have `{ url, token }`, you can skip the client-token hop:
-
-```ts
-const session = new RealtimeSession({ url, token });
-```
-
 ## License
 
 MIT. See `licenses/` for notices covering bundled third-party code.