Livepeer exposes multiple access interfaces for developers, creators, and infrastructure operators to interact with the protocol and network. These include SDKs, REST and gRPC APIs, the CLI, GraphQL endpoints, and playback tooling for on-chain and off-chain applications. This page breaks down each interface by use case, target user, and sample integration paths.Documentation Index
Fetch the complete documentation index at: https://na-36-docs-v2.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Interface categories
REST API (Livepeer Studio)
Available at:https://livepeer.studio/api
Common endpoints:
POST /stream- Create video stream ingest sessionPOST /transcode- On-demand file transcodePOST /ai/infer- Submit AI job (e.g. Image enhancement)GET /session/:id- Fetch session status
gRPC API (Gateway nodes)
gRPC allows high-throughput, low-latency Orchestrator routing. Methods (examples):ReserveSession, Heartbeat, ReportJobComplete, OrchestratorList
Used by: Studio Gateway, Daydream Gateway, Cascade.
Proto: gateway.proto
GraphQL Explorer API
Access detailed Livepeer on-chain and network state. Endpoint:https://explorer.livepeer.org/graphql
Example query:
JS SDK
GitHub: @livepeer/sdk Install:CLI
Install via Go build or Docker:stake, unbond, withdraw, reward, claim, transcode, broadcast, query
Ideal for Orchestrator testing and protocol analysis.
Smart contract interfaces
Interact directly with the protocol (Arbitrum) via RPC and ABIs.Current Arbitrum contract addresses and ABIs are listed in Blockchain contracts. Use
ethers.js, viem, hardhat, or JSON-RPC to call contracts.Workflow examples
Transcode from web app:See also
- Technical architecture - Stack overview, Orchestrator, Gateway, workers
- Marketplace - Routing and pricing
- Job lifecycle - Session flow and settlement
- Blockchain contracts - Contract addresses and ABIs
- Livepeer Protocol repo