SDK families
Two SDK families exist. Choose based on what you are building:Studio SDK
The Studio SDK is auto-generated from the Studio OpenAPI spec by Speakeasy and maintained in the official Livepeer repositories. It is the recommended choice for production applications.TypeScript / JavaScript
- npm: https://www.npmjs.com/package/livepeer
- GitHub: https://github.com/livepeer/livepeer-js
- Version: 3.5.0
Python
Go
React UI Kit
- npm: https://www.npmjs.com/package/@livepeer/react
- GitHub: https://github.com/livepeer/ui-kit
- Version: 4.3.2
Player— HLS and WebRTC playback with automatic protocol selection, keyboard shortcuts, and PictureInPictureBroadcast— In-browser RTMP/WebRTC broadcastingControls— Play, volume, fullscreen, and quality controls
AI SDK (alpha)
The AI SDK is generated separately from the AI gateway OpenAPI spec. Use the Studio SDK for production applications; use the AI SDK for AI-inference-only projects or when you want a smaller dependency footprint.TypeScript
- npm: https://www.npmjs.com/package/@livepeer/ai
- GitHub: https://github.com/livepeer/livepeer-ai-js
- Default gateway:
https://dream-gateway.livepeer.cloud(public, non-production)
Python
Go
Deprecated SDKs
Do not use these packages in new projects:| Package | Status | Migration path |
|---|---|---|
@livepeer/webrtmp-sdk | Deprecated | Use @livepeer/react Broadcast component |
@livepeer/react-native | Deprecated | Use react-native-video (HLS) + react-native-webrtc (WebRTC) |
Old livepeer.js monorepo | Archived | Migrate to livepeer npm v3.5.0 |
Related pages
SDK Integration Guide
Full code examples, error handling, and retry configuration for all SDKs.
APIs
REST API reference, OpenAPI spec, and endpoint list.