FIX ME - should just show pricing config & link to About/Economics & a guide on it
Gateway Pricing and Fee Structure
Gateways in Livepeer set prices and pay fees through a multi-layered system that includes price limits, per-gateway pricing, and payment processing for both video transcoding and AI workloads. Gateways use a probabilistic micropayment system where they generate payment tickets for work done. The system supports both traditional video transcoding (per segment) and AI processing (per pixel) with different pricing models but unified payment infrastructure rpc.go:61-64.Gateway Economics
Looking for information on how gateways earn fees for services?
Gateway Configuration
Configurations a Gateway can set for pricing.Setting Price Limits For Work Performed by Orchestrators
Gateways set maximum prices they’re willing to pay through configuration flags in thetranscodingConfig.json or directly in the CLI.
Price Configuration Flags
Maximum price per pixelsPerUnit (in wei
integer or a custom currency format like 0.50USD or 0.02USD) for transcoding work livepeer.go:137JSON list (or path to JSON congif file) of maximum prices per AI capability/model livepeer.go:138
Allows exceeding max price if no orchestrator meets requirements livepeer.go:139
Go to Funding Your Gateway
How to fund your gateway and pay for Orchestrator workloads.
Orchestrator Configuration & Price Information
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:915-926
Price Calculation
The actual price calculation happens in the orchestrator’spriceInfo function orchestrator.go:357-431
- 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
Fee Payment 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:237-271
- Fee calculation: Based on pixels processed × price per pixel segment_rpc.go:645-653
- Per-pixel payments: Calculated as width × height × outputs live_payment.go:162-165
- Live video: Uses interval-based payments during streaming ai_http.go:181-211
- Gateway sends payment with segment/request to orchestrator live_payment.go:96-114
- Orchestrator validates payment and updates balance segment_rpc.go:257-261
- Fees are debited from gateway’s balance account ai_http.go:568