Web / TypeScript
Modern browsers (ES2020+). @twai/core + @twai/player + @twai/react.
Quickstart →
SDKs
The 2wai Avatar Toolkit is a polyglot developer offering — pick the language your app is already in. Every SDK speaks the same wire (Transport 0 over LiveKit), consumes the same api.2wai.ai gateway, and enforces the same mint-proxy pattern (sk_ server-side only).
Web Component
<twai-avatar> — one HTML tag, no framework, two attributes. For sites
that just need to drop an avatar into a page. Quickstart →
Flutter
One codebase, every platform: iOS, Android, Web, Windows, macOS, Linux.
twai_avatar_sdk + twai_avatar_sdk_livekit. Quickstart →
iOS native (Swift)
SwiftUI-first, Swift Package Manager, iOS 15+. Shipped and verified on device (greeting, audio, Q&A, idle). Quickstart →
REST + Postman
Any language. OpenAPI spec + Postman collection + mint-proxy templates (Node / Python / Cloudflare Worker). See Quickstart for the raw path.
Android native (Kotlin)
Upon request. Flutter already ships to Android from one codebase; a dedicated Kotlin/Compose SDK is roadmap-conditional. Ping your 2wai contact if you need it.
Capability matrix
Section titled “Capability matrix”| Web (TS) | Web Component | Flutter | iOS native | REST | Android native | |
|---|---|---|---|---|---|---|
| Status | Shipped | Shipped | Shipped | Shipped (device-verified) | Always | Upon request |
| Repo | twai-web-sdk | twai-web-sdk | 2wai-toolkit | 2wai-toolkit/ios-native | OpenAPI | — |
| Platforms | Modern browsers | Any Custom-Element browser | iOS · Android · Web · desktop | iOS 15+ | Any language | — |
| Transport | LiveKit (T0) | LiveKit (T0) | LiveKit (T0) | LiveKit (T0) | LiveKit (T0) | — |
| Mint-proxy | Required | Required | Required | Required | Required | — |
| BYO brain | Yes | No (server-side concern) | Yes | Yes (v0.2) | Yes | — |
| BYO TTS | Yes | No | Yes | Yes (v0.2) | Yes | — |
| Catalog hydrate | Planned | Planned | Yes (getAvatar(owner, name)) | Yes | Yes (raw REST) | — |
| Mic input | Yes (@twai/mic) | stt-url attr | Yes (TwaiMicButton) | v0.2 | Client-side | — |
No SDK? Use REST
Section titled “No SDK? Use REST”If no SDK targets your language yet, the gateway is a plain REST + LiveKit integration — every SDK is a thin wrapper. See the Quickstart for the raw path (Node mint proxy + livekit-client on the client).
OpenAPI spec Canonical API spec. Point your OpenAPI code generator at it.
Postman collection Pre-wired requests for every endpoint.
Mint proxy templates Node, Python, Cloudflare Worker starters for the server-side piece.
The shared contract: twai-protocol
Section titled “The shared contract: twai-protocol”Every SDK conforms to 2waiorg/twai-protocol — JSON Schemas + golden test vectors + the single-source codec constant. This is why a bug fixed in one SDK’s engine can be lifted verbatim into another’s: same wire, same shapes, same conformance test.