Pricing Concepts
Payment Currency
All payments are made in ETH(wei) - not Livepeer tokens (LPT).Pricing Models
- Video Transcoding: Per video segment processed
- Unit: Pixels processed (width x height)
- Calculation: pixels processed × price per pixel
- AI Processing: Priced per capability / model.
- Unit: Price per capability/model
- Calculation:
- Per-pixel payments: Calculated as width × height × outputs
- Per-request payments: Single payment per AI request
- Live video payments: Interval-based payments during streaming (configurable)
Pricing Configuration Flags
Video Transcoding Core Flags
Video
int
default:"0 (wei)"
Maximum price per pixelsPerUnit (in wei
integer or a custom currency
format like 0.50USD or 0.02USD) for transcoding workAll pricing is in
wei unless currency conversion is configuredint
default:"1"
Number of pixels per pricing unit
boolean
default:"false"
Allow exceeding max price if no suitable Orchestrator exists
AI Processing Core Flags
Fee Payment Calculation & Process
Gateways pay fees through different mechanisms depending on workload type: Video Transcoding- Per-segment payments: Each video segment generates a payment ticket -> segment_rpc.go:
- Fee calculation: Based on pixels processed × price per pixel -> segment_rpc.go
- Per-pixel payments: Calculated as width × height × outputs live_payment.go
- Live video: Uses interval-based payments during streaming ai_http.go
- Gateway sends payment with segment/request to Orchestrator live_payment.go
- Orchestrator validates payment and updates balance segment_rpc.go
- Fees are debited from Gateway’s balance account ai_http.go
Configuration Methods
Gateways set maximum prices they’re willing to pay through configuration flags in thetranscodingConfig.json or directly in the CLI.
- Command-line flags
- JSON Configuration file (plain text key value format)
- HTTP API - can be used at runtime to make adjustments without restart
- /setBroadcastConfig: Set general pricing
- /setMaxPriceForCapability: Set AI model pricing
- CLI Tool
Orchestrator Configuration & Price Information (Gateway Reference)
A reference for Gateway Operators on how Orchestrators configure pricing and fees for services.Per-Gateway Pricing (can be set by Orchestrators)
Orchestrators can set specific prices for individual Gateways using-pricePerGateway starter.go
Price Calculation
The actual price calculation happens in the Orchestrator’spriceInfo function Orchestrator.go
- Checks for fixed prices per manifest ID
- Gets base price from Orchestrator configuration
- For AI workloads, sums prices of individual capability/model pairs
- Applies auto-adjustment based on transaction costs if enabled
Dynamic Price Adjustment
Orchestrators can enable automatic price adjustments based on transaction costs - which is why it’s important to set maxPricing flags -> Orchestrator.goFull List of Gateway Pricing Configuration Flags
Video Transcoding Pricing Flags
AI Processing Pricing Flags
Payment Ticket Flags
Gas & Transaction Flags (Affect Pricing)
Orchestrator-Specific Pricing (For Reference)
Notes
- Gateway flags control what you pay (max prices)
- Orchestrator flags control what you charge (actual prices)
- AI pricing uses the
maxPricePerCapabilityJSON structure for per-model pricing - All prices can be specified in wei or with currency suffix (e.g., “0.50USD”)
- Default “0” values mean accept any price or use system defaults
Related Pages
Gateway Economics
How Gateways earn fees for services
Funding Your Gateway
How to fund your Gateway.