Sorry About That."
+ }
+ },
+ "redirects": [
+ {
+ "source": "/v2/pages/07_resources/redirect",
+ "destination": "/v2/pages/07_resources/resources_hub"
+ },
+ {
+ "source": "/v2/pages/08_help/redirect",
+ "destination": "/v2/pages/08_help/README"
+ },
+ {
+ "source": "/v1/guides/developing/quickstart",
+ "destination": "/v1/developers/quick-start"
+ },
+ {
+ "source": "/v1/guides/overview",
+ "destination": "/v1/developers/guides/overview"
+ },
+ {
+ "source": "/v1/guides/developing/player",
+ "destination": "/v1/developers/guides/playback-an-asset"
+ },
+ {
+ "source": "/v1/guides/developing/create-a-livestream",
+ "destination": "/v1/developers/guides/create-livestream"
+ },
+ {
+ "source": "/v1/guides/developing/stream-via-obs",
+ "destination": "/v1/developers/guides/stream-via-obs"
+ },
+ {
+ "source": "/v1/developing/stream-via-browser",
+ "destination": "/v1/developers/guides/livestream-from-browser"
+ },
+ {
+ "source": "/v1/guides/developing/upload-a-video-asset",
+ "destination": "/v1/developers/guides/upload-video-asset"
+ },
+ {
+ "source": "/v1/guides/developing/mint-a-video-nft",
+ "destination": "/v1/developers/guides/mint-video-nft"
+ },
+ {
+ "source": "/v1/guides/developing/dstorage-playback",
+ "destination": "/v1/developers/guides/dstorage-playback"
+ },
+ {
+ "source": "/v1/developers/guides/dstorage-playback",
+ "destination": "/v1/developers/guides/upload-video-asset"
+ },
+ {
+ "source": "/v1/guides/developing/access-control",
+ "destination": "/v1/developers/guides/access-control-webhooks"
+ },
+ {
+ "source": "/v1/guides/developing/access-control-vod",
+ "destination": "/v1/developers/guides/access-control-webhooks"
+ },
+ {
+ "source": "/v1/guides/developing/encrypted-vod",
+ "destination": "/v1/developers/guides/encrypted-asset"
+ },
+ {
+ "source": "/v1/guides/developing/listen-for-webhooks",
+ "destination": "/v1/developers/guides/setup-and-listen-to-webhooks"
+ },
+ {
+ "source": "/v1/guides/developing/multistream",
+ "destination": "/v1/developers/guides/multistream"
+ },
+ {
+ "source": "/v1/guides/developing/monitor-stream-health",
+ "destination": "/v1/developers/guides/monitor-stream-health"
+ },
+ {
+ "source": "/v1/guides/developing/viewer-engagement",
+ "destination": "/v1/developers/guides/get-engagement-analytics-via-api"
+ },
+ {
+ "source": "/v1/guides/developing/transcode-video-storj",
+ "destination": "/v1/developers/guides/transcode-video-storj"
+ },
+ {
+ "source": "/v1/guides/developing/transcode-video-w3s",
+ "destination": "/v1/developers/guides/transcode-video-w3s"
+ },
+ {
+ "source": "/v1/tutorials/developing/optimize-latency",
+ "destination": "/v1/developers/guides/optimize-latency-of-a-livestream"
+ },
+ {
+ "source": "/v1/tutorials/developing/analyze-engagement-timeplus",
+ "destination": "/v1/developers/guides/get-engagement-analytics-via-timeplus"
+ },
+ {
+ "source": "/v1/tutorials/developing/visualize-engagement-metrics-grafana",
+ "destination": "/v1/developers/guides/get-engagement-analytics-via-grafana"
+ },
+ {
+ "source": "/v1/tutorials/developing/token-gate-videos-using-guildxyz",
+ "destination": "/v1/developers/tutorials/token-gate-videos-with-lit"
+ },
+ {
+ "source": "/v1/tutorials/developing/token-gate-videos-using-lit",
+ "destination": "/v1/developers/tutorials/token-gate-videos-with-lit"
+ },
+ {
+ "source": "/v1/tutorials/developing/build-decentralized-video-app-with-fvm",
+ "destination": "/v1/developers/tutorials/decentralized-app-with-fvm"
+ },
+ {
+ "source": "/v1/tutorials/developing/upload-playback-videos-on-ipfs-4everland",
+ "destination": "/v1/developers/tutorials/upload-playback-videos-4everland"
+ },
+ {
+ "source": "/v1/tutorials/developing/upload-playback-videos-on-ipfs",
+ "destination": "/v1/developers/tutorials/upload-playback-videos-on-ipfs"
+ },
+ {
+ "source": "/v1/tutorials/developing/upload-playback-videos-on-arweave",
+ "destination": "/v1/developers/tutorials/upload-playback-videos-on-arweave"
+ },
+ {
+ "source": "/v1/reference/api",
+ "destination": "/v1/api-reference/overview/introduction"
+ },
+ {
+ "source": "/v1/reference/deployed-contract-addresses",
+ "destination": "/v1/references/contract-addresses"
+ },
+ {
+ "source": "/v1/reference/example-applications",
+ "destination": "/v1/references/example-applications"
+ },
+ {
+ "source": "/v1/reference/api-support-matrix",
+ "destination": "/v1/references/api-support-matrix"
+ },
+ {
+ "source": "/v1/reference/go-livepeer",
+ "destination": "/v1/references/go-livepeer/bandwidth-requirements"
+ },
+ {
+ "source": "/v1/reference/go-livepeer/cli-reference",
+ "destination": "/v1/references/go-livepeer/cli-reference"
+ },
+ {
+ "source": "/v1/reference/go-livepeer/gpu-support",
+ "destination": "/v1/references/go-livepeer/gpu-support"
+ },
+ {
+ "source": "/v1/reference/go-livepeer/hardware-requirements",
+ "destination": "/v1/references/go-livepeer/hardware-requirements"
+ },
+ {
+ "source": "/v1/reference/go-livepeer/bandwidth-requirements",
+ "destination": "/v1/references/go-livepeer/bandwidth-requirements"
+ },
+ {
+ "source": "/v1/reference/go-livepeer/prometheus-metrics",
+ "destination": "/v1/references/go-livepeer/prometheus-metrics"
+ },
+ {
+ "source": "/v1/guides/delegating/bridge-lpt-to-arbitrum",
+ "destination": "/v1/delegators/guides/bridge-lpt-to-arbitrum"
+ },
+ {
+ "source": "/v1/guides/delegating/migrate-stake-to-arbitrum",
+ "destination": "/v1/delegators/guides/migrate-stake-to-arbitrum"
+ },
+ {
+ "source": "/v1/delegators/reference/yield-calculation",
+ "destination": "/v1/delegators/guides/yield-calculation"
+ },
+ {
+ "source": "/v1/guides/orchestrating/get-started",
+ "destination": "/v1/orchestrators/guides/get-started"
+ },
+ {
+ "source": "/v1/guides/orchestrating/install-go-livepeer",
+ "destination": "/v1/orchestrators/guides/install-go-livepeer"
+ },
+ {
+ "source": "/v1/guides/orchestrating/connect-to-arbitrum",
+ "destination": "/v1/orchestrators/guides/connect-to-arbitrum"
+ },
+ {
+ "source": "/v1/guides/orchestrating/configure-reward-calling",
+ "destination": "/v1/orchestrators/guides/configure-reward-calling"
+ },
+ {
+ "source": "/v1/guides/orchestrating/set-session-limits",
+ "destination": "/v1/orchestrators/guides/set-session-limits"
+ },
+ {
+ "source": "/v1/guides/orchestrating/set-pricing",
+ "destination": "/v1/orchestrators/guides/set-pricing"
+ },
+ {
+ "source": "/v1/guides/orchestrating/benchmark-transcoding",
+ "destination": "/v1/orchestrators/guides/benchmark-transcoding"
+ },
+ {
+ "source": "/v1/guides/orchestrating/assess-capabilities",
+ "destination": "/v1/orchestrators/guides/assess-capabilities"
+ },
+ {
+ "source": "/v1/guides/orchestrating/monitor-metrics",
+ "destination": "/v1/orchestrators/guides/monitor-metrics"
+ },
+ {
+ "source": "/v1/guides/orchestrating/vote",
+ "destination": "/v1/orchestrators/guides/vote"
+ },
+ {
+ "source": "/v1/guides/orchestrating/dual-mine",
+ "destination": "/v1/orchestrators/guides/dual-mine"
+ },
+ {
+ "source": "/v1/guides/orchestrating/o-t-split",
+ "destination": "/v1/orchestrators/guides/o-t-split"
+ },
+ {
+ "source": "/v1/guides/orchestrating/migrate-to-arbitrum",
+ "destination": "/v1/orchestrators/guides/migrate-to-arbitrum"
+ },
+ {
+ "source": "/v1/guides/orchestrating/migrate-from-contract-wallet",
+ "destination": "/v1/orchestrators/guides/migrate-from-contract-wallet"
+ },
+ {
+ "source": "/v1/guides/orchestrating/gateway-introspection",
+ "destination": "/v1/orchestrators/guides/gateway-introspection"
+ },
+ {
+ "source": "/v1/guides/orchestrating/troubleshoot",
+ "destination": "/v1/orchestrators/guides/troubleshoot"
+ },
+ {
+ "source": "/v1/reference/react",
+ "destination": "/v1/react/getting-started"
+ },
+ {
+ "source": "/v1/reference/react/getting-started",
+ "destination": "/v1/react/getting-started"
+ },
+ {
+ "source": "/v1/reference/react/client",
+ "destination": "/v1/react/getting-started"
+ },
+ {
+ "source": "/v1/reference/react/LivepeerConfig",
+ "destination": "/v1/sdks/react/migration/3.x/LivepeerConfig"
+ },
+ {
+ "source": "/v1/reference/react/Player",
+ "destination": "/v1/react/player/Root"
+ },
+ {
+ "source": "/v1/reference/react/Broadcast",
+ "destination": "/v1/react/broadcast/Root"
+ },
+ {
+ "source": "/v1/reference/react/providers/studio",
+ "destination": "/v1/sdks/react/migration/3.x/providers/studio"
+ },
+ {
+ "source": "/v1/reference/react/asset/useAsset",
+ "destination": "/v1/sdks/react/migration/3.x/asset/useAsset"
+ },
+ {
+ "source": "/v1/reference/react/asset/useCreateAsset",
+ "destination": "/v1/sdks/react/migration/3.x/asset/useCreateAsset"
+ },
+ {
+ "source": "/v1/reference/react/asset/useAssetMetrics",
+ "destination": "/v1/sdks/react/migration/3.x/asset/useAssetMetrics"
+ },
+ {
+ "source": "/v1/reference/react/asset/useUpdateAsset",
+ "destination": "/v1/sdks/react/migration/3.x/asset/useUpdateAsset"
+ },
+ {
+ "source": "/v1/reference/react/stream/useStream",
+ "destination": "/v1/sdks/react/migration/3.x/stream/useStream"
+ },
+ {
+ "source": "/v1/reference/react/stream/useStreamSession",
+ "destination": "/v1/sdks/react/migration/3.x/stream/useStreamSession"
+ },
+ {
+ "source": "/v1/reference/react/stream/useStreamSessions",
+ "destination": "/v1/sdks/react/migration/3.x/stream/useStreamSessions"
+ },
+ {
+ "source": "/v1/reference/react/stream/useCreateStream",
+ "destination": "/v1/sdks/react/migration/3.x/stream/useCreateStream"
+ },
+ {
+ "source": "/v1/reference/react/stream/useUpdateStream",
+ "destination": "/v1/sdks/react/migration/3.x/stream/useUpdateStream"
+ },
+ {
+ "source": "/v1/reference/react/playback/usePlaybackInfo",
+ "destination": "/v1/sdks/react/migration/3.x/playback/usePlaybackInfo"
+ },
+ {
+ "source": "/v1/reference/react/constants/abis",
+ "destination": "/v1/sdks/react/migration/3.x/constants/abis"
+ },
+ {
+ "source": "/v1/reference/react/constants/contract-addresses",
+ "destination": "/v1/sdks/react/migration/3.x/constants/contract-addresses"
+ }
+ ]
+}
diff --git a/llms.txt.information.md b/llms.txt.information.md
new file mode 100644
index 00000000..21254206
--- /dev/null
+++ b/llms.txt.information.md
@@ -0,0 +1,30 @@
+This page is deliberately named incorrectly so as not to override the default
+llms.txt file.
+
+https://www.mintlify.com/docs/ai/llmstxt
+
+An llms.txt file is a plain Markdown file that contains: Site title as an H1
+heading. Structured content sections with links and a description of each page
+in your documentation.
+
+**Ensure all pages have a description for LLMs.txt to be useful.**
+
+Each page’s description comes from the description field in its frontmatter.
+Pages without a description field appear in the llms.txt file without a
+description.
+
+Example
+
+```
+# Site title
+
+## Docs
+
+- [API](https://example.com/docs/api): Endpoint list and usage
+- [Install](https://example.com/docs/install): Setup steps
+- [Getting started](https://example.com/docs/start): Intro guide
+```
+
+This structured approach allows LLMs to efficiently process your documentation
+at a high level and locate relevant content for user queries, improving the
+accuracy and speed of AI-assisted documentation searches.
diff --git a/mint.json b/mintOld.json
similarity index 97%
rename from mint.json
rename to mintOld.json
index b70dc247..ab684bf8 100644
--- a/mint.json
+++ b/mintOld.json
@@ -336,12 +336,7 @@
"url": "https://discord.gg/livepeer"
}
],
- "versions": [
- "Developers",
- "Delegators",
- "Orchestrators",
- "Gateways"
- ],
+ "versions": ["Developers", "Delegators", "Orchestrators", "Gateways"],
"topbarCtaButton": {
"name": "Dashboard",
"url": "https://livepeer.studio"
@@ -430,9 +425,7 @@
{
"group": "Webhooks",
"icon": "bell",
- "pages": [
- "developers/guides/setup-and-listen-to-webhooks"
- ]
+ "pages": ["developers/guides/setup-and-listen-to-webhooks"]
},
{
"group": "Transcode API",
@@ -454,9 +447,7 @@
{
"group": "Projects",
"icon": "folder-open",
- "pages": [
- "developers/guides/managing-projects"
- ]
+ "pages": ["developers/guides/managing-projects"]
},
{
"group": "Integrations",
@@ -582,9 +573,7 @@
"group": "How to Contribute",
"icon": "heart",
"iconType": "solid",
- "pages": [
- "ai/contributors/coming-soon"
- ]
+ "pages": ["ai/contributors/coming-soon"]
},
{
"group": "SDKs",
@@ -645,17 +634,11 @@
},
{
"group": "Overview",
- "pages": [
- "sdks/introduction"
- ]
+ "pages": ["sdks/introduction"]
},
{
"group": "Server-side SDKs",
- "pages": [
- "sdks/javascript",
- "sdks/go",
- "sdks/python"
- ]
+ "pages": ["sdks/javascript", "sdks/go", "sdks/python"]
},
{
"group": "React Components",
@@ -734,10 +717,7 @@
{
"group": "Examples",
"icon": "clipboard",
- "pages": [
- "sdks/react/Player",
- "sdks/react/Broadcast"
- ]
+ "pages": ["sdks/react/Player", "sdks/react/Broadcast"]
},
{
"group": "Migration",
@@ -773,9 +753,7 @@
},
{
"group": "Playback",
- "pages": [
- "sdks/react/migration/3.x/playback/usePlaybackInfo"
- ]
+ "pages": ["sdks/react/migration/3.x/playback/usePlaybackInfo"]
},
{
"group": "Constants",
diff --git a/openapi.yaml b/openapi.yaml
index d1674c23..220a7f78 100644
--- a/openapi.yaml
+++ b/openapi.yaml
@@ -84,7 +84,10 @@ components:
quality:
type: integer
description: >
- Restricts the size of the output video using the constant quality feature. Increasing this value will result in a lower quality video. Note that this parameter might not work if the transcoder lacks support for it.
+ Restricts the size of the output video using the constant quality
+ feature. Increasing this value will result in a lower quality video.
+ Note that this parameter might not work if the transcoder lacks
+ support for it.
minimum: 0
maximum: 44
@@ -131,7 +134,10 @@ components:
quality:
type: integer
description: >
- Restricts the size of the output video using the constant quality feature. Increasing this value will result in a lower quality video. Note that this parameter might not work if the transcoder lacks support for it.
+ Restricts the size of the output video using the constant quality
+ feature. Increasing this value will result in a lower quality video.
+ Note that this parameter might not work if the transcoder lacks
+ support for it.
minimum: 0
maximum: 44
@@ -193,7 +199,8 @@ components:
createdAt:
type: number
readOnly: true
- description: Timestamp (in milliseconds) at which stream object was created
+ description:
+ Timestamp (in milliseconds) at which stream object was created
example: 1587667174725
events:
type: array
@@ -251,7 +258,8 @@ components:
type: number
readOnly: true
example: 1587667174725
- description: Timestamp (in milliseconds) at which the webhook last failed
+ description:
+ Timestamp (in milliseconds) at which the webhook last failed
error:
readOnly: true
type: string
@@ -354,17 +362,24 @@ components:
playbackId:
type: string
description: >-
- The playback ID of the stream or stream recording to clip. Asset playback IDs are not supported yet.
+ The playback ID of the stream or stream recording to clip. Asset
+ playback IDs are not supported yet.
example: eaw4nk06ts2d0mzb
startTime:
type: number
description: >-
- The start timestamp of the clip in Unix milliseconds. _See the ClipTrigger in the UI Kit for an example of how this is calculated (for HLS, it uses `Program Date-Time` tags, and for WebRTC, it uses the latency from server to client at stream startup)._
+ The start timestamp of the clip in Unix milliseconds. _See the
+ ClipTrigger in the UI Kit for an example of how this is calculated
+ (for HLS, it uses `Program Date-Time` tags, and for WebRTC, it uses
+ the latency from server to client at stream startup)._
example: 1587667174725
endTime:
type: number
description: >-
- The end timestamp of the clip in Unix milliseconds. _See the ClipTrigger in the UI Kit for an example of how this is calculated (for HLS, it uses `Program Date-Time` tags, and for WebRTC, it uses the latency from server to client at stream startup)._
+ The end timestamp of the clip in Unix milliseconds. _See the
+ ClipTrigger in the UI Kit for an example of how this is calculated
+ (for HLS, it uses `Program Date-Time` tags, and for WebRTC, it uses
+ the latency from server to client at stream startup)._
example: 1587667174725
name:
type: string
@@ -373,7 +388,9 @@ components:
sessionId:
type: string
description: >-
- The optional session ID of the stream to clip. This can be used to clip _recordings_ - if it is not specified, it will clip the ongoing livestream.
+ The optional session ID of the stream to clip. This can be used to
+ clip _recordings_ - if it is not specified, it will clip the ongoing
+ livestream.
example: de7818e7-610a-4057-8f6f-b785dc1e6f88
target:
type: object
@@ -432,7 +449,8 @@ components:
createdAt:
type: number
readOnly: true
- description: Timestamp (in milliseconds) at which stream object was created
+ description:
+ Timestamp (in milliseconds) at which stream object was created
example: 1587667174725
stream:
type: object
@@ -512,7 +530,8 @@ components:
createdAt:
type: number
readOnly: true
- description: Timestamp (in milliseconds) at which stream object was created
+ description:
+ Timestamp (in milliseconds) at which stream object was created
example: 1587667174725
parentId:
type: string
@@ -585,7 +604,9 @@ components:
playbackId:
type: string
example: eaw4nk06ts2d0mzb
- description: The playback ID to use with the Playback Info endpoint to retrieve playback URLs.
+ description:
+ The playback ID to use with the Playback Info endpoint to retrieve
+ playback URLs.
playbackPolicy:
$ref: "#/components/schemas/playback-policy"
profiles:
@@ -664,7 +685,8 @@ components:
- number
- "null"
example: 1713281212993
- description: Timestamp (in milliseconds) when the stream was last terminated
+ description:
+ Timestamp (in milliseconds) when the stream was last terminated
userId:
type: string
readOnly: true
@@ -789,7 +811,9 @@ components:
- type: "array"
items:
type: "string"
- description: "A string array of human-readable errors describing issues affecting the stream, if any."
+ description:
+ "A string array of human-readable errors describing issues affecting
+ the stream, if any."
tracks:
type: object
description: |
@@ -806,7 +830,8 @@ components:
description: "The bitrate of the track, in kilobits per second."
keys:
type: object
- description: An object containing additional track-specific metrics.
+ description:
+ An object containing additional track-specific metrics.
additionalProperties:
type: number
fpks:
@@ -890,7 +915,8 @@ components:
createdAt:
readOnly: true
type: number
- description: Timestamp (in milliseconds) at which stream object was created
+ description:
+ Timestamp (in milliseconds) at which stream object was created
example: 1587667174725
parentId:
type: string
@@ -902,14 +928,16 @@ components:
example: aac12556-4d65-4d34-9fb6-d1f0985eb0a9
record:
description: >
- Whether the stream should be recorded. Uses default settings. For more customization, create and configure an object store.
+ Whether the stream should be recorded. Uses default settings. For
+ more customization, create and configure an object store.
type: boolean
example: false
recordingStatus:
readOnly: true
type: string
- description: The status of the recording process of this stream session.
+ description:
+ The status of the recording process of this stream session.
enum:
- waiting
- ready
@@ -923,12 +951,14 @@ components:
mp4Url:
type: string
readOnly: true
- description: The URL for the stream session recording packaged in an MP4.
+ description:
+ The URL for the stream session recording packaged in an MP4.
playbackId:
type: string
example: eaw4nk06ts2d0mzb
description: >-
- The playback ID to use with the Playback Info endpoint to retrieve playback URLs.
+ The playback ID to use with the Playback Info endpoint to retrieve
+ playback URLs.
profiles:
$ref: "#/components/schemas/stream/properties/profiles"
recordingSpec:
@@ -964,7 +994,8 @@ components:
url:
type: string
writeOnly: true
- description: Livepeer-compatible multistream target URL (RTMP(S) or SRT)
+ description:
+ Livepeer-compatible multistream target URL (RTMP(S) or SRT)
example: "rtmps://live.my-service.tv/channel/secretKey"
format: uri
pattern: "^(srt|rtmps?)://"
@@ -1003,7 +1034,8 @@ components:
type: string
example: eaw4nk06ts2d0mzb
description: >-
- The playback ID to use with the Playback Info endpoint to retrieve playback URLs.
+ The playback ID to use with the Playback Info endpoint to retrieve
+ playback URLs.
userId:
type: string
readOnly: true
@@ -1019,13 +1051,18 @@ components:
example: >-
https://livepeercdn.com/asset/ea03f37e-f861-4cdd-b495-0e60b6d753ad/index.m3u8
description: >-
- URL for HLS playback. **It is recommended to not use this URL**, and instead use playback IDs with the Playback Info endpoint to retrieve the playback URLs - this URL format is subject to change (e.g. https://livepeercdn.com/asset/ea03f37e-f861-4cdd-b495-0e60b6d753ad/index.m3u8).
+ URL for HLS playback. **It is recommended to not use this URL**, and
+ instead use playback IDs with the Playback Info endpoint to retrieve
+ the playback URLs - this URL format is subject to change (e.g.
+ https://livepeercdn.com/asset/ea03f37e-f861-4cdd-b495-0e60b6d753ad/index.m3u8).
downloadUrl:
readOnly: true
type: string
example: "https://livepeercdn.com/asset/eaw4nk06ts2d0mzb/video/download.mp4"
description: >-
- The URL to directly download the asset, e.g. `https://livepeercdn.com/asset/eawrrk06ts2d0mzb/video`. It is not recommended to use this for playback.
+ The URL to directly download the asset, e.g.
+ `https://livepeercdn.com/asset/eawrrk06ts2d0mzb/video`. It is not
+ recommended to use this for playback.
playbackPolicy:
$ref: "#/components/schemas/playback-policy"
source:
@@ -1045,7 +1082,8 @@ components:
gatewayUrl:
type: string
description: >-
- Gateway URL from asset if parsed from provided URL on upload.
+ Gateway URL from asset if parsed from provided URL on
+ upload.
encryption:
$ref: "#/components/schemas/new-asset-payload/properties/encryption"
- additionalProperties: false
@@ -1059,7 +1097,8 @@ components:
- recording
sessionId:
type: string
- description: ID of the session from which this asset was created
+ description:
+ ID of the session from which this asset was created
- additionalProperties: false
required:
- type
@@ -1073,20 +1112,25 @@ components:
$ref: "#/components/schemas/new-asset-payload/properties/encryption"
sourceId:
type: string
- description: ID of the asset or stream from which this asset was created.
+ description:
+ ID of the asset or stream from which this asset was created.
sessionId:
type: string
- description: ID of the session from which this asset was created.
+ description:
+ ID of the session from which this asset was created.
playbackId:
type: string
description: >-
- Playback ID of the asset or stream from which this asset was created.
+ Playback ID of the asset or stream from which this asset was
+ created.
requesterId:
type: string
- description: ID of the requester from which this asset was created.
+ description:
+ ID of the requester from which this asset was created.
assetId:
type: string
- description: ID of the asset from which this asset was created.
+ description:
+ ID of the asset from which this asset was created.
creatorId:
$ref: "#/components/schemas/creator-id"
profiles:
@@ -1162,7 +1206,8 @@ components:
- deleted
updatedAt:
type: number
- description: Timestamp (in milliseconds) at which the asset was last updated
+ description:
+ Timestamp (in milliseconds) at which the asset was last updated
example: 1587667174725
progress:
type: number
@@ -1173,7 +1218,8 @@ components:
name:
type: string
description: >
- The name of the asset. This is not necessarily the filename - it can be a custom name or title.
+ The name of the asset. This is not necessarily the filename - it can
+ be a custom name or title.
example: filename.mp4
projectId:
@@ -1275,7 +1321,8 @@ components:
example: 1080
pixelFormat:
type: string
- description: Pixel format of the track - only for video tracks
+ description:
+ Pixel format of the track - only for video tracks
example: yuv420p
fps:
type: number
@@ -1329,7 +1376,8 @@ components:
name:
type: string
description: >
- The name of the asset. This is not necessarily the filename - it can be a custom name or title.
+ The name of the asset. This is not necessarily the filename - it can
+ be a custom name or title.
example: filename.mp4
staticMp4:
@@ -1370,7 +1418,8 @@ components:
type: string
writeOnly: true
description: >-
- Encryption key used to encrypt the asset. Only writable in the upload asset endpoints and cannot be retrieved back.
+ Encryption key used to encrypt the asset. Only writable in the
+ upload asset endpoints and cannot be retrieved back.
c2pa:
type: boolean
description: Decides if the output video should include C2PA signature
@@ -1382,7 +1431,8 @@ components:
$ref: "#/components/schemas/transcode-profile"
targetSegmentSizeSecs:
type: number
- description: How many seconds the duration of each output segment should be
+ description:
+ How many seconds the duration of each output segment should be
room-user-payload:
type: object
required:
@@ -1399,7 +1449,8 @@ components:
example: true
canPublishData:
type: boolean
- description: Whether a user is allowed to publish data messages to the room
+ description:
+ Whether a user is allowed to publish data messages to the room
example: true
metadata:
type: string
@@ -1421,12 +1472,14 @@ components:
joinUrl:
type: string
description: >-
- Joining URL - use this for Livepeer's default meeting app (see the multiparticipant streaming guide for more info).
+ Joining URL - use this for Livepeer's default meeting app (see the
+ multiparticipant streaming guide for more info).
example: "https://meet.livepeer.chat"
token:
type: string
description: >-
- Joining JWT - this can be used if you have a custom meeting app (see the multiparticipant streaming guide for more info).
+ Joining JWT - this can be used if you have a custom meeting app (see
+ the multiparticipant streaming guide for more info).
example: token
get-room-user-response:
type: object
@@ -1470,12 +1523,14 @@ components:
canPublish:
type: boolean
description: >-
- Whether a user is allowed to publish audio/video tracks (i.e. their microphone and webcam)
+ Whether a user is allowed to publish audio/video tracks (i.e. their
+ microphone and webcam)
example: true
default: true
canPublishData:
type: boolean
- description: Whether a user is allowed to publish data messages to the room
+ description:
+ Whether a user is allowed to publish data messages to the room
example: true
default: true
metadata:
@@ -1566,7 +1621,10 @@ components:
format: uri
pattern: "^http(s)?://"
description: >-
- Service endpoint URL (AWS S3 endpoint list: https://docs.aws.amazon.com/general/latest/gr/s3.html, GCP S3 endpoint: https://storage.googleapis.com, Storj: https://gateway.storjshare.io)
+ Service endpoint URL (AWS S3 endpoint list:
+ https://docs.aws.amazon.com/general/latest/gr/s3.html, GCP
+ S3 endpoint: https://storage.googleapis.com, Storj:
+ https://gateway.storjshare.io)
example: "https://gateway.storjshare.io"
bucket:
type: string
@@ -1613,7 +1671,10 @@ components:
format: uri
pattern: "^http(s)?://"
description: >-
- Service endpoint URL (AWS S3 endpoint list: https://docs.aws.amazon.com/general/latest/gr/s3.html, GCP S3 endpoint: https://storage.googleapis.com, Storj: https://gateway.storjshare.io)
+ Service endpoint URL (AWS S3 endpoint list:
+ https://docs.aws.amazon.com/general/latest/gr/s3.html, GCP
+ S3 endpoint: https://storage.googleapis.com, Storj:
+ https://gateway.storjshare.io)
example: "https://gateway.storjshare.io"
bucket:
type: string
@@ -1705,7 +1766,8 @@ components:
$ref: "#/components/schemas/transcode-profile"
targetSegmentSizeSecs:
type: number
- description: How many seconds the duration of each output segment should be
+ description:
+ How many seconds the duration of each output segment should be
creatorId:
$ref: "#/components/schemas/input-creator-id"
c2pa:
@@ -1776,7 +1838,8 @@ components:
$ref: "#/components/schemas/new-asset-payload/properties/encryption"
c2pa:
type: boolean
- description: Decides if the output video should include C2PA signature
+ description:
+ Decides if the output video should include C2PA signature
example: true
profiles:
type: array
@@ -1785,7 +1848,8 @@ components:
targetSegmentSizeSecs:
type: number
description: >-
- How many seconds the duration of each output segment should be
+ How many seconds the duration of each output segment should
+ be
example: 6
export:
$ref: "#/components/schemas/export-task-params"
@@ -1875,7 +1939,8 @@ components:
$ref: "#/components/schemas/input-creator-id"
c2pa:
type: boolean
- description: Decides if the output video should include C2PA signature
+ description:
+ Decides if the output video should include C2PA signature
example: false
clip:
properties:
@@ -1887,7 +1952,10 @@ components:
clipStrategy:
type: object
description: >-
- Strategy to use for clipping the asset. If not specified, the default strategy that Catalyst is configured for will be used. This field only available for admin users, and is only used for E2E testing.
+ Strategy to use for clipping the asset. If not specified,
+ the default strategy that Catalyst is configured for will be
+ used. This field only available for admin users, and is only
+ used for E2E testing.
additionalProperties: false
properties:
startTime:
@@ -1899,7 +1967,10 @@ components:
catalystPipelineStrategy:
type: string
description: >-
- Force to use a specific strategy in the Catalyst pipeline. If not specified, the default strategy that Catalyst is configured for will be used. This field only available for admin users, and is only used for E2E testing.
+ Force to use a specific strategy in the Catalyst pipeline.
+ If not specified, the default strategy that Catalyst is
+ configured for will be used. This field only available for
+ admin users, and is only used for E2E testing.
enum:
- catalyst
- catalyst_ffmpeg
@@ -2000,16 +2071,19 @@ components:
videoFileGatewayUrl:
readOnly: true
type: string
- description: URL to access file via HTTP through an IPFS gateway
+ description:
+ URL to access file via HTTP through an IPFS gateway
example: "https://gateway.ipfs.io/ipfs/Qmabc123xyz341"
nftMetadataCid:
type: string
- description: IPFS CID of the default metadata exported for the video
+ description:
+ IPFS CID of the default metadata exported for the video
example: Qmabc123xyz341
nftMetadataUrl:
readOnly: true
type: string
- description: URL for the metadata file with the IPFS protocol
+ description:
+ URL for the metadata file with the IPFS protocol
example: "ipfs://Qmabc123xyz341"
nftMetadataGatewayUrl:
readOnly: true
@@ -2049,7 +2123,8 @@ components:
type: string
- type: string
description: >-
- Helper syntax to specify an unverified creator ID, fully managed by the developer.
+ Helper syntax to specify an unverified creator ID, fully managed by
+ the developer.
creator-id:
oneOf:
- type: object
@@ -2065,7 +2140,8 @@ components:
example: "unverified"
value:
type: string
- description: Developer-managed ID of the user who created the resource.
+ description:
+ Developer-managed ID of the user who created the resource.
example: "user123"
export-task-params:
description: Parameters for the export task
@@ -2128,12 +2204,14 @@ components:
createdAt:
readOnly: true
type: number
- description: Timestamp (in milliseconds) at which the signing-key was created
+ description:
+ Timestamp (in milliseconds) at which the signing-key was created
example: 1587667174725
lastSeen:
readOnly: true
type: number
- description: Timestamp (in milliseconds) at which the signing-key was last used
+ description:
+ Timestamp (in milliseconds) at which the signing-key was last used
example: 1587667174725
publicKey:
type: string
@@ -2201,15 +2279,18 @@ components:
example: 1234
createdAt:
type: number
- description: Timestamp (in milliseconds) at which user object was created
+ description:
+ Timestamp (in milliseconds) at which user object was created
example: 1587667174725
verifiedAt:
type: number
- description: Timestamp (in milliseconds) at which user object was verified
+ description:
+ Timestamp (in milliseconds) at which user object was verified
example: 1587667174725
planChangedAt:
type: number
- description: Timestamp (in milliseconds) at which user object was verified
+ description:
+ Timestamp (in milliseconds) at which user object was verified
example: 1587667174725
lastStreamedAt:
type: number
@@ -2219,7 +2300,8 @@ components:
example: 1587667174725
lastSeen:
type: number
- description: Timestamp (in milliseconds) at which user's password was used
+ description:
+ Timestamp (in milliseconds) at which user's password was used
example: 1587667174725
usage:
type: object
@@ -2252,7 +2334,8 @@ components:
type:
- object
- "null"
- description: Whether the playback policy for an asset or stream is public or signed
+ description:
+ Whether the playback policy for an asset or stream is public or signed
additionalProperties: false
required:
- type
@@ -2272,7 +2355,7 @@ components:
type: object
description: User-defined webhook context
additionalProperties: true
- example: {"streamerId": "my-custom-id"}
+ example: { "streamerId": "my-custom-id" }
refreshInterval:
type: number
description: |
@@ -2281,7 +2364,9 @@ components:
example: 600
allowedOrigins:
type: array
- description: List of allowed origins for CORS playback (://:, ://)
+ description:
+ List of allowed origins for CORS playback
+ (://:, ://)
items:
type: string
usage-metric:
@@ -2417,7 +2502,8 @@ components:
example: America/Los_Angeles
geohash:
type: string
- description: Geographic encoding of the viewers location. Accurate to 3 digits.
+ description:
+ Geographic encoding of the viewers location. Accurate to 3 digits.
example: 123
viewCount:
type: integer
@@ -2624,7 +2710,8 @@ components:
createdAt:
type: number
readOnly: true
- description: Timestamp (in milliseconds) at which the object was created
+ description:
+ Timestamp (in milliseconds) at which the object was created
example: 1587667174725
signatureType:
type: string
@@ -2644,7 +2731,8 @@ components:
readOnly: true
type: number
description: >
- Timestamp (in milliseconds) at which IPFS export task was updated
+ Timestamp (in milliseconds) at which IPFS export task was
+ updated
example: 1587667174725
status:
@@ -2685,7 +2773,8 @@ components:
apiSecret:
type: string
writeOnly: true
- description: Will be added to the pinata_secret_api_key header.
+ description:
+ Will be added to the pinata_secret_api_key header.
example: 1234567890abcdef
storage-status:
readOnly: true
@@ -2753,9 +2842,11 @@ components:
format: uri
pattern: "^(https?|ipfs|ar)://"
description: >
- URL where the asset contents can be retrieved, e.g. `https://s3.amazonaws.com/my-bucket/path/filename.mp4`.
+ URL where the asset contents can be retrieved, e.g.
+ `https://s3.amazonaws.com/my-bucket/path/filename.mp4`.
- For an IPFS source, this should be similar to: `ipfs://{CID}`. For an Arweave
+ For an IPFS source, this should be similar to: `ipfs://{CID}`. For
+ an Arweave
source: `ar://{CID}`.
@@ -2796,8 +2887,11 @@ components:
type: string
title: Return Timestamps
description: >-
- Return timestamps for the transcribed text. Supported values: 'sentence', 'word', or a string boolean ('true' or 'false'). Default is 'true' ('sentence'). 'false' means no timestamps. 'word' means word-based timestamps.
- default: 'true'
+ Return timestamps for the transcribed text. Supported values:
+ 'sentence', 'word', or a string boolean ('true' or 'false'). Default
+ is 'true' ('sentence'). 'false' means no timestamps. 'word' means
+ word-based timestamps.
+ default: "true"
type: object
required:
- audio
@@ -2823,36 +2917,43 @@ components:
type: string
title: Loras
description: >-
- A LoRA (Low-Rank Adaptation) model and its corresponding weight for image generation. Example: { "latent-consistency/lcm-lora-sdxl": 1.0, "nerijs/pixel-art-xl": 1.2}.
- default: ''
+ A LoRA (Low-Rank Adaptation) model and its corresponding weight for
+ image generation. Example: { "latent-consistency/lcm-lora-sdxl":
+ 1.0, "nerijs/pixel-art-xl": 1.2}.
+ default: ""
strength:
type: number
title: Strength
- description: Degree of transformation applied to the reference image (0 to 1).
+ description:
+ Degree of transformation applied to the reference image (0 to 1).
default: 0.8
guidance_scale:
type: number
title: Guidance Scale
description: >-
- Encourages model to generate images closely linked to the text prompt (higher values may reduce image quality).
+ Encourages model to generate images closely linked to the text
+ prompt (higher values may reduce image quality).
default: 7.5
image_guidance_scale:
type: number
title: Image Guidance Scale
description: >-
- Degree to which the generated image is pushed towards the initial image.
+ Degree to which the generated image is pushed towards the initial
+ image.
default: 1.5
negative_prompt:
type: string
title: Negative Prompt
description: >-
- Text prompt(s) to guide what to exclude from image generation. Ignored if guidance_scale < 1.
- default: ''
+ Text prompt(s) to guide what to exclude from image generation.
+ Ignored if guidance_scale < 1.
+ default: ""
safety_check:
type: boolean
title: Safety Check
description: >-
- Perform a safety check to estimate if generated images could be offensive or harmful.
+ Perform a safety check to estimate if generated images could be
+ offensive or harmful.
default: true
seed:
type: integer
@@ -2862,7 +2963,8 @@ components:
type: integer
title: Num Inference Steps
description: >-
- Number of denoising steps. More steps usually lead to higher quality images but slower inference. Modulated by strength.
+ Number of denoising steps. More steps usually lead to higher quality
+ images but slower inference. Modulated by strength.
default: 100
num_images_per_prompt:
type: integer
@@ -2906,19 +3008,22 @@ components:
type: integer
title: Motion Bucket Id
description: >-
- Used for conditioning the amount of motion for the generation. The higher the number the more motion will be in the video.
+ Used for conditioning the amount of motion for the generation. The
+ higher the number the more motion will be in the video.
default: 127
noise_aug_strength:
type: number
title: Noise Aug Strength
description: >-
- Amount of noise added to the conditioning image. Higher values reduce resemblance to the conditioning image and increase motion.
+ Amount of noise added to the conditioning image. Higher values
+ reduce resemblance to the conditioning image and increase motion.
default: 0.02
safety_check:
type: boolean
title: Safety Check
description: >-
- Perform a safety check to estimate if generated images could be offensive or harmful.
+ Perform a safety check to estimate if generated images could be
+ offensive or harmful.
default: true
seed:
type: integer
@@ -2928,7 +3033,8 @@ components:
type: integer
title: Num Inference Steps
description: >-
- Number of denoising steps. More steps usually lead to higher quality images but slower inference. Modulated by strength.
+ Number of denoising steps. More steps usually lead to higher quality
+ images but slower inference. Modulated by strength.
default: 25
type: object
required:
@@ -2947,7 +3053,7 @@ components:
system_msg:
type: string
title: System Msg
- default: ''
+ default: ""
temperature:
type: number
title: Temperature
@@ -2959,7 +3065,7 @@ components:
history:
type: string
title: History
- default: '[]'
+ default: "[]"
stream:
type: boolean
title: Stream
@@ -2985,38 +3091,47 @@ components:
type: string
title: Point Coords
description: >-
- Nx2 array of point prompts to the model, where each point is in (X,Y) in pixels.
+ Nx2 array of point prompts to the model, where each point is in
+ (X,Y) in pixels.
point_labels:
type: string
title: Point Labels
description: >-
- Labels for the point prompts, where 1 indicates a foreground point and 0 indicates a background point.
+ Labels for the point prompts, where 1 indicates a foreground point
+ and 0 indicates a background point.
box:
type: string
title: Box
- description: 'A length 4 array given as a box prompt to the model, in XYXY format.'
+ description:
+ "A length 4 array given as a box prompt to the model, in XYXY
+ format."
mask_input:
type: string
title: Mask Input
description: >-
- A low-resolution mask input to the model, typically from a previous prediction iteration, with the form 1xHxW (H=W=256 for SAM).
+ A low-resolution mask input to the model, typically from a previous
+ prediction iteration, with the form 1xHxW (H=W=256 for SAM).
multimask_output:
type: boolean
title: Multimask Output
description: >-
- If true, the model will return three masks for ambiguous input prompts, often producing better masks than a single prediction.
+ If true, the model will return three masks for ambiguous input
+ prompts, often producing better masks than a single prediction.
default: true
return_logits:
type: boolean
title: Return Logits
description: >-
- If true, returns un-thresholded mask logits instead of a binary mask.
+ If true, returns un-thresholded mask logits instead of a binary
+ mask.
default: true
normalize_coords:
type: boolean
title: Normalize Coords
description: >-
- If true, the point coordinates will be normalized to the range [0,1], with point_coords expected to be with respect to image dimensions.
+ If true, the point coordinates will be normalized to the range
+ [0,1], with point_coords expected to be with respect to image
+ dimensions.
default: true
type: object
required:
@@ -3043,7 +3158,8 @@ components:
type: boolean
title: Safety Check
description: >-
- Perform a safety check to estimate if generated images could be offensive or harmful.
+ Perform a safety check to estimate if generated images could be
+ offensive or harmful.
default: true
seed:
type: integer
@@ -3053,7 +3169,8 @@ components:
type: integer
title: Num Inference Steps
description: >-
- Number of denoising steps. More steps usually lead to higher quality images but slower inference. Modulated by strength.
+ Number of denoising steps. More steps usually lead to higher quality
+ images but slower inference. Modulated by strength.
default: 75
type: object
required:
@@ -3082,7 +3199,7 @@ components:
properties:
detail:
allOf:
- - $ref: '#/components/schemas/APIError'
+ - $ref: "#/components/schemas/APIError"
description: Detailed error information.
type: object
required:
@@ -3093,7 +3210,7 @@ components:
properties:
detail:
items:
- $ref: '#/components/schemas/ValidationError'
+ $ref: "#/components/schemas/ValidationError"
type: array
title: Detail
type: object
@@ -3102,7 +3219,7 @@ components:
properties:
images:
items:
- $ref: '#/components/schemas/Media'
+ $ref: "#/components/schemas/Media"
type: array
title: Images
description: The generated images.
@@ -3137,7 +3254,8 @@ components:
logits:
type: string
title: Logits
- description: 'The raw, unnormalized predictions (logits) for the masks.'
+ description:
+ "The raw, unnormalized predictions (logits) for the masks."
type: object
required:
- masks
@@ -3165,7 +3283,8 @@ components:
- seed
- nsfw
title: Media
- description: A media object containing information about the generated media.
+ description:
+ A media object containing information about the generated media.
TextResponse:
properties:
text:
@@ -3174,7 +3293,7 @@ components:
description: The generated text.
chunks:
items:
- $ref: '#/components/schemas/Chunk'
+ $ref: "#/components/schemas/Chunk"
type: array
title: Chunks
description: The generated text chunks.
@@ -3195,13 +3314,16 @@ components:
type: string
title: Loras
description: >-
- A LoRA (Low-Rank Adaptation) model and its corresponding weight for image generation. Example: { "latent-consistency/lcm-lora-sdxl": 1.0, "nerijs/pixel-art-xl": 1.2}.
- default: ''
+ A LoRA (Low-Rank Adaptation) model and its corresponding weight for
+ image generation. Example: { "latent-consistency/lcm-lora-sdxl":
+ 1.0, "nerijs/pixel-art-xl": 1.2}.
+ default: ""
prompt:
type: string
title: Prompt
description: >-
- Text prompt(s) to guide image generation. Separate multiple prompts with '|' if supported by the model.
+ Text prompt(s) to guide image generation. Separate multiple prompts
+ with '|' if supported by the model.
height:
type: integer
title: Height
@@ -3216,19 +3338,22 @@ components:
type: number
title: Guidance Scale
description: >-
- Encourages model to generate images closely linked to the text prompt (higher values may reduce image quality).
+ Encourages model to generate images closely linked to the text
+ prompt (higher values may reduce image quality).
default: 7.5
negative_prompt:
type: string
title: Negative Prompt
description: >-
- Text prompt(s) to guide what to exclude from image generation. Ignored if guidance_scale < 1.
- default: ''
+ Text prompt(s) to guide what to exclude from image generation.
+ Ignored if guidance_scale < 1.
+ default: ""
safety_check:
type: boolean
title: Safety Check
description: >-
- Perform a safety check to estimate if generated images could be offensive or harmful.
+ Perform a safety check to estimate if generated images could be
+ offensive or harmful.
default: true
seed:
type: integer
@@ -3238,7 +3363,8 @@ components:
type: integer
title: Num Inference Steps
description: >-
- Number of denoising steps. More steps usually lead to higher quality images but slower inference. Modulated by strength.
+ Number of denoising steps. More steps usually lead to higher quality
+ images but slower inference. Modulated by strength.
default: 50
num_images_per_prompt:
type: integer
@@ -3275,7 +3401,7 @@ components:
properties:
images:
items:
- $ref: '#/components/schemas/Media'
+ $ref: "#/components/schemas/Media"
type: array
title: Images
description: The generated images.
@@ -4800,7 +4926,9 @@ paths:
tags:
- webhook
description: >
- To create a new webhook, you need to make an API call with the events you want to listen for and the URL that will be called when those events occur.
+ To create a new webhook, you need to make an API call with the events
+ you want to listen for and the URL that will be called when those events
+ occur.
requestBody:
required: true
@@ -5657,13 +5785,19 @@ paths:
url:
type: string
description: >-
- The direct upload endpoint for which supports PUT requests. **It is recommended to use the Tus endpoint for a better upload experience.**
+ The direct upload endpoint for which supports PUT
+ requests. **It is recommended to use the Tus endpoint for
+ a better upload experience.**
example: >-
https://origin.livepeer.com/api/asset/upload/direct?token=eyJhbGciOiJIUzI1NiJ9.eyJtc2ciOiJoZWxsbyBoYWNrZXIsIHRoZXJlJ3Mgbm90aGluZyBmb3IgeW91IGhlcmUg8J-YhiJ9.1YDjmXsqLcgNyMSzT4kXl_kIni46_EuGX_xfqmC7e0Q
tusEndpoint:
type: string
description: >-
- The [Tus-compatible](https://tus.io/) endpoint for resumable uploads. **This is the recommended way to upload assets.** See the [Tus-js](https://github.com/tus/tus-js-client) client for more information.
+ The [Tus-compatible](https://tus.io/) endpoint for
+ resumable uploads. **This is the recommended way to upload
+ assets.** See the
+ [Tus-js](https://github.com/tus/tus-js-client) client for
+ more information.
example: >-
https://origin.livepeer.com/api/asset/upload/tus?token=eyJhbGciOiJIUzI1NiJ9.eyJtc2ciOiJoZWxsbyBoYWNrZXIsIHRoZXJlJ3Mgbm90aGluZyBmb3IgeW91IGhlcmUg8J-YhiJ9.1YDjmXsqLcgNyMSzT4kXl_kIni46_EuGX_xfqmC7e0Q
asset:
@@ -7020,7 +7154,8 @@ paths:
description: >
Create a livestream for your room.
- This allows you to leverage livestreaming features like recording and HLS output.
+ This allows you to leverage livestreaming features like recording and
+ HLS output.
responses:
default:
@@ -7159,9 +7294,11 @@ paths:
type: string
summary: Create a room user
description: >
- Call this endpoint to add a user to a room, specifying a display name at a minimum.
+ Call this endpoint to add a user to a room, specifying a display name at
+ a minimum.
- The response will contain a joining URL for Livepeer's default meeting app.
+ The response will contain a joining URL for Livepeer's default meeting
+ app.
Alternatively the joining token can be used with a custom app.
@@ -7725,7 +7862,9 @@ paths:
tags:
- metrics
description: >
- Requires a proof of ownership to be sent in the request, which for now is just the assetId or streamId parameters (1 of those must be in the query-string).
+ Requires a proof of ownership to be sent in the request, which for now
+ is just the assetId or streamId parameters (1 of those must be in the
+ query-string).
parameters:
- name: from
@@ -7894,7 +8033,8 @@ paths:
schema:
$ref: "#/components/schemas/error"
"200":
- description: A single Metric object with the viewCount and playtimeMins metrics.
+ description:
+ A single Metric object with the viewCount and playtimeMins metrics.
content:
application/json:
schema:
@@ -8363,9 +8503,14 @@ paths:
tags:
- accessControl
description: >
- The publicKey is a representation of the public key, encoded as base 64 and is passed as a string, and the privateKey is displayed only on creation. This is the only moment where the client can save the private key, otherwise it will be lost. Remember to decode your string when signing JWTs.
+ The publicKey is a representation of the public key, encoded as base 64
+ and is passed as a string, and the privateKey is displayed only on
+ creation. This is the only moment where the client can save the private
+ key, otherwise it will be lost. Remember to decode your string when
+ signing JWTs.
- Up to 10 signing keys can be generated, after that you must delete at least one signing key to create a new one.
+ Up to 10 signing keys can be generated, after that you must delete at
+ least one signing key to create a new one.
responses:
default:
@@ -9276,7 +9421,8 @@ paths:
schema:
type: string
description: >-
- The playback ID from the asset or livestream, e.g. `eaw4nk06ts2d0mzb`.
+ The playback ID from the asset or livestream, e.g.
+ `eaw4nk06ts2d0mzb`.
responses:
default:
description: Error
@@ -9365,7 +9511,7 @@ paths:
content:
application/json:
schema:
- $ref: '#/components/schemas/TextToImageParams'
+ $ref: "#/components/schemas/TextToImageParams"
required: true
responses:
default:
@@ -9373,46 +9519,46 @@ paths:
content:
application/json:
schema:
- $ref: '#/components/schemas/studio-api-error'
- '200':
+ $ref: "#/components/schemas/studio-api-error"
+ "200":
description: Successful Response
content:
application/json:
schema:
- $ref: '#/components/schemas/ImageResponse'
+ $ref: "#/components/schemas/ImageResponse"
x-speakeasy-name-override: data
- '400':
+ "400":
description: Bad Request
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
- '401':
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "401":
description: Unauthorized
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
- '422':
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "422":
description: Validation Error
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPValidationError'
- - $ref: '#/components/schemas/studio-api-error'
- '500':
+ - $ref: "#/components/schemas/HTTPValidationError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "500":
description: Internal Server Error
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
x-speakeasy-name-override: textToImage
x-codeSamples:
- lang: typescript
@@ -9445,7 +9591,7 @@ paths:
content:
multipart/form-data:
schema:
- $ref: '#/components/schemas/Body_genImageToImage'
+ $ref: "#/components/schemas/Body_genImageToImage"
required: true
responses:
default:
@@ -9453,46 +9599,46 @@ paths:
content:
application/json:
schema:
- $ref: '#/components/schemas/studio-api-error'
- '200':
+ $ref: "#/components/schemas/studio-api-error"
+ "200":
description: Successful Response
content:
application/json:
schema:
- $ref: '#/components/schemas/ImageResponse'
+ $ref: "#/components/schemas/ImageResponse"
x-speakeasy-name-override: data
- '400':
+ "400":
description: Bad Request
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
- '401':
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "401":
description: Unauthorized
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
- '422':
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "422":
description: Validation Error
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPValidationError'
- - $ref: '#/components/schemas/studio-api-error'
- '500':
+ - $ref: "#/components/schemas/HTTPValidationError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "500":
description: Internal Server Error
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
x-speakeasy-name-override: imageToImage
x-codeSamples:
- lang: typescript
@@ -9527,7 +9673,7 @@ paths:
content:
multipart/form-data:
schema:
- $ref: '#/components/schemas/Body_genImageToVideo'
+ $ref: "#/components/schemas/Body_genImageToVideo"
required: true
responses:
default:
@@ -9535,46 +9681,46 @@ paths:
content:
application/json:
schema:
- $ref: '#/components/schemas/studio-api-error'
- '200':
+ $ref: "#/components/schemas/studio-api-error"
+ "200":
description: Successful Response
content:
application/json:
schema:
- $ref: '#/components/schemas/VideoResponse'
+ $ref: "#/components/schemas/VideoResponse"
x-speakeasy-name-override: data
- '400':
+ "400":
description: Bad Request
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
- '401':
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "401":
description: Unauthorized
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
- '422':
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "422":
description: Validation Error
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPValidationError'
- - $ref: '#/components/schemas/studio-api-error'
- '500':
+ - $ref: "#/components/schemas/HTTPValidationError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "500":
description: Internal Server Error
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
x-speakeasy-name-override: imageToVideo
x-codeSamples:
- lang: typescript
@@ -9608,7 +9754,7 @@ paths:
content:
multipart/form-data:
schema:
- $ref: '#/components/schemas/Body_genUpscale'
+ $ref: "#/components/schemas/Body_genUpscale"
required: true
responses:
default:
@@ -9616,46 +9762,46 @@ paths:
content:
application/json:
schema:
- $ref: '#/components/schemas/studio-api-error'
- '200':
+ $ref: "#/components/schemas/studio-api-error"
+ "200":
description: Successful Response
content:
application/json:
schema:
- $ref: '#/components/schemas/ImageResponse'
+ $ref: "#/components/schemas/ImageResponse"
x-speakeasy-name-override: data
- '400':
+ "400":
description: Bad Request
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
- '401':
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "401":
description: Unauthorized
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
- '422':
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "422":
description: Validation Error
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPValidationError'
- - $ref: '#/components/schemas/studio-api-error'
- '500':
+ - $ref: "#/components/schemas/HTTPValidationError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "500":
description: Internal Server Error
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
x-speakeasy-name-override: upscale
x-codeSamples:
- lang: typescript
@@ -9690,7 +9836,7 @@ paths:
content:
multipart/form-data:
schema:
- $ref: '#/components/schemas/Body_genAudioToText'
+ $ref: "#/components/schemas/Body_genAudioToText"
required: true
responses:
default:
@@ -9698,62 +9844,62 @@ paths:
content:
application/json:
schema:
- $ref: '#/components/schemas/studio-api-error'
- '200':
+ $ref: "#/components/schemas/studio-api-error"
+ "200":
description: Successful Response
content:
application/json:
schema:
- $ref: '#/components/schemas/TextResponse'
+ $ref: "#/components/schemas/TextResponse"
x-speakeasy-name-override: data
- '400':
+ "400":
description: Bad Request
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
- '401':
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "401":
description: Unauthorized
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
- '413':
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "413":
description: Request Entity Too Large
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
- '415':
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "415":
description: Unsupported Media Type
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
- '422':
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "422":
description: Validation Error
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPValidationError'
- - $ref: '#/components/schemas/studio-api-error'
- '500':
+ - $ref: "#/components/schemas/HTTPValidationError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "500":
description: Internal Server Error
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
x-speakeasy-name-override: audioToText
x-codeSamples:
- lang: typescript
@@ -9787,7 +9933,7 @@ paths:
content:
multipart/form-data:
schema:
- $ref: '#/components/schemas/Body_genSegmentAnything2'
+ $ref: "#/components/schemas/Body_genSegmentAnything2"
required: true
responses:
default:
@@ -9795,46 +9941,46 @@ paths:
content:
application/json:
schema:
- $ref: '#/components/schemas/studio-api-error'
- '200':
+ $ref: "#/components/schemas/studio-api-error"
+ "200":
description: Successful Response
content:
application/json:
schema:
- $ref: '#/components/schemas/MasksResponse'
+ $ref: "#/components/schemas/MasksResponse"
x-speakeasy-name-override: data
- '400':
+ "400":
description: Bad Request
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
- '401':
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "401":
description: Unauthorized
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
- '422':
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "422":
description: Validation Error
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPValidationError'
- - $ref: '#/components/schemas/studio-api-error'
- '500':
+ - $ref: "#/components/schemas/HTTPValidationError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "500":
description: Internal Server Error
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
x-speakeasy-name-override: segmentAnything2
x-codeSamples:
- lang: typescript
@@ -9868,7 +10014,7 @@ paths:
content:
application/x-www-form-urlencoded:
schema:
- $ref: '#/components/schemas/Body_genLLM'
+ $ref: "#/components/schemas/Body_genLLM"
required: true
responses:
default:
@@ -9876,45 +10022,45 @@ paths:
content:
application/json:
schema:
- $ref: '#/components/schemas/studio-api-error'
- '200':
+ $ref: "#/components/schemas/studio-api-error"
+ "200":
description: Successful Response
content:
application/json:
schema:
- $ref: '#/components/schemas/LLMResponse'
- '400':
+ $ref: "#/components/schemas/LLMResponse"
+ "400":
description: Bad Request
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
- '401':
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "401":
description: Unauthorized
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
- '422':
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "422":
description: Validation Error
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPValidationError'
- - $ref: '#/components/schemas/studio-api-error'
- '500':
+ - $ref: "#/components/schemas/HTTPValidationError"
+ - $ref: "#/components/schemas/studio-api-error"
+ "500":
description: Internal Server Error
content:
application/json:
schema:
oneOf:
- - $ref: '#/components/schemas/HTTPError'
- - $ref: '#/components/schemas/studio-api-error'
+ - $ref: "#/components/schemas/HTTPError"
+ - $ref: "#/components/schemas/studio-api-error"
x-speakeasy-name-override: llm
x-codeSamples:
- lang: typescript
diff --git a/snippets/api-base-urls-table.mdx b/snippets/api-base-urls-table.mdx
new file mode 100644
index 00000000..34243cb4
--- /dev/null
+++ b/snippets/api-base-urls-table.mdx
@@ -0,0 +1,27 @@
+{/*
+ API Base URLs Table Snippet
+ Usage: Include this in API landing pages for styled base URL tables
+ Pass props: urls (array of {name, url} objects)
+*/}
+
+export const ApiBaseUrlsTable = ({ urls }) => (
+
For the past year, the Livepeer Ecosystem has been guided by the Cascade vision: a path to transition from a pure streaming and transcoding infrastructure, to an infrastructure that could succeed at providing compute for the future of real-time AI video. The latest Livepeer quarterly report from Messari highlights that this transition is paying off, with network fees up 3x from this time last year, and over 72% of the fees now driven via AI inference. This is exemplified by the growing inspirational examples emerging from Daydream powered real-time AI, and real-time Agent avatar generation through Embody and the Agent SPE.
This shift has been an ecosystem wide effort – ranging from branding and communications, to productization and go to market, to hardware upgrades for orchestrators. It has successfully shifted the project under an updated mission and direction, however it has still left ambiguity in terms of what the Livepeer network itself offers as killer value propositions to new builders outside of the existing ecosystem. Is it a GPU cloud? A transcoding infra? An API engine? Now that there are signs of validation and accelerated momentum around an exciting opportunity, it’s time to really hone in on a refined vision for the future of the Livepeer network as a product itself.
The market for video is set to massively expand
The concept of live video itself is expanding well beyond a simple single stream of video captured from a camera. Now entire worlds and scenes are generated or enhanced in real-time via AI assistance, leading to more immersive and interactive experiences than possible via old-school streaming alone. For a taste of the future, see the following examples:
The future of gaming will be AI generated video and worlds in real-time:
Video world models and real-time AI video are merging, as they both use AI to generate frame-by-frame video output with low latency on the fly, based on user input and AI inference. This requires a tremendous amount of GPU compute, and requires an amazing low latency video streaming and compute stack – two areas in which the Livepeer network and community thrive, and two areas to which the many other generic GPU inference providers in the market bring no unique skillset, experience, or software advantage.
The big opportunity for the Livepeer network is to be the leading AI Infrastructure For Real-Time Video. From interactive live streaming to generative world models, Livepeer’s open-access, low-latency network of GPUs will be the best compute solution for cutting edge AI video workflows.
World models are a game changing category, and Livepeer is well suited to offer a unique and differentiated product here, that serves a huge market of diverse and varying use cases. These range from creative entertainment, to gaming, to robotics, to data analysis, to monitoring and security, to synthetic data generation for AGI itself.
What does it mean to productize the Livepeer network to succeed as a valuable infrastructure in this category?
From a simplified viewpoint, it needs to deliver on the following:
1. Ability for users to deploy real-time AI workflows to the Livepeer network and request inference on them
2. Industry leading latency for providing inference on real-time AI and world model workflows.
3. Cost effective scalability – users can pay as they go to scale up and down capacity and the network automagically delivers the scale required.
Imagine a gaming platform is powering world-model generated games using their unique workflows that generate game levels or areas in a certain style by combining several real-time models, LLMs, and style transfer mechanisms. Each game its powering has users exploring and creating their own corners of the interactive worlds, based on prompts and gameplay inputs. Every gamer that joins a game represents a new stream of AI video compute, and the Livepeer network is the backing infrastructure that provides the compute for this video world generation, leveraging hundreds or thousands of GPUs concurrently.
For this to be possible the Livepeer network needs to enable that game platform to deploy their game generation workflow. It needs to offer low latency on the inference that runs this workflow, relative to the generic GPU compute clouds. The pricing needs to be competitive vs alternative options in the market for this GPU compute. And the network needs to allow this company to scale up and down the number of GPUs that are currently live ready to accept new real-time inference streams based on the number of users currently live on the games it is powering.
All of this is possible on the Livepeer network, and it isn’t far away from where we are now. If we work to build, test, and iterate on the Livepeer network itself towards supporting the latency and scale required for these types of workflows, we’ll be set up to power them. Now multiply this example gaming company by the high number of diverse industries and verticals that real-time AI and world models will touch. Each category can have one or multiple companies competing to leverage this scalable and cost effective infrastructure for unique go to markets targeting different segments. And they can all be powered by the Livepeer network’s unique value propositions.
Livepeer’s core network is strategically positioned
What are these value propositions that make the Livepeer network differentiated relative to alternative options in the market? I’d argue that there are three primary, table stakes, must-have value propositions if Livepeer is to succeed.
1. Industry standard low latency infrastructure specializing in real-time AI and world model workflows: First of all, the network needs to let its users deploy custom workflows. Inference alone on base models is not enough and does not represent scaled demand. Users want to take base models, chain them together with other models and pre/post processors, and create unique and specialized capabilities. When one of these capabilities is defined as a workflow, that is the unit that needs to be deployed as a job on the Livepeer network, and the network needs to be able to run inference on it. Secondly, for these real-time interactive use cases, latency matters a lot. Generic GPU clouds don’t offer the specialized low latency video stacks to ingest, process, and serve video with optimal latency, but Livepeer does. And Livepeer needs to benchmark itself to have lower or equal latency to alternative GPU clouds for these particular real-time and world model use cases.
2. Cost effective scalability: GPU provisioning, reservations, and competing for scarce supply procurement creates major challenges for AI companies – often overpaying for GPUs that sit idle most of the time in order to guarantee the capacity that they need. The Livepeer network’s value proposition is that users should be able to “automagically” scale up almost instantly and pay on demand for the compute that they use, rather than having to pre-pay for reservations and let capacity sit idle. This is enabled by Livepeer taking advantage of otherwise existing idle longtail compute through its open marketplace, and its supply side incentives. The Livepeer network needs to be more cost effective than alternative GPU clouds within this category - with impacts comparable to the 10x+ cost reduction already demonstrated in live video transcoding delivered by the network.
3. Community driven, open source, open access: The Livepeer project and software stack is open source. Users can control, update, and contribute to the software they are using. They also can be owners in the infrastructure itself through the Livepeer Token, and can benefit from the network’s improvements and adoption, creating a network effect. The community that cares about its success and pushes it forward collectively, can be a superpower, relative to the uncertain and shaky relationship between builders and centralized platform providers, who have a history of getting rugged based on limitations to access, changes in functionality, or discontinuity of the platforms. Anyone can build on the Livepeer network regardless of location, jurisdiction, use case, or central party control.
The above are primary value propositions that should appeal to nearly all users. And we must work to close the gaps to live up to those value props before we could successfully hope to go to market and attract new vertical-specific companies to build directly on top of the network. Luckily, in addition to all of Livepeer’s streaming users, we have a great realtime AI design partner in Daydream, which is already going to market around creative real-time AI, using the network, and contributing to its development to live up to these requirements. While building with this design partner, the ecosystem should be working to productize to live up to these promises in a more generic perspective – it should be setting up benchmarks, testing frameworks, and building mechanisms for scaling up supply ahead of demand, so that it can represent this power to the world alongside successful Daydream case studies.
Opportunities to push towards this vision
To truly live up to these value propositions, there are a number of opportunities for the community to focus on in order to close some key gaps. There are many details to come in more technical posts laying out roadmaps and execution frameworks, but at a high level, consider a series of milestones that take the network as a product from technically functional, to production usable, to extensible, to infinitely scalable:
Network MVP - Measure what matters: Establish key network performance SLAs, measure latency and performance benchmarks, and enhance the low latency client to support realtime AI workflows above industry grade standards.
Network as a Product - Self adaptability and scalability: Network delivers against these SLAs and core value props for supported realtime AI workflows. Selection algorithms, failovers and redundancy, and competitive market price discovery established for realtime AI.
Extensibility - Toolkit for community to deploy workflows and provision resources: Workflow deployment and signaling, LPT incentive updates to ensure compute supply for popular AI workflows exceeds demand.
Parallel Scalability: Manage clusters of resources on the network for parallel workflow execution, truly unlocking job types beyond single-GPU inference.
Many teams within the ecosystem, from the Foundation, to Livepeer Inc, to various SPEs have already started operationalizing around how they’ll be contributing to milestones 1 and 2 to upgrade the network to deliver against these key realtime AI value propositions.
Conclusion and Livepeer’s opportunity
The market for the opportunity to be the GPU infrastructure that powers real-time AI and world models is absolutely massive – the compute requirements are tremendous - 1000x that of AI text or images - and real-time interaction with media represents a new platform that will affect all of the above-mentioned industries. The Livepeer network can be the infrastructure that powers it. How we plan to close the needed gaps and achieve this will be the subject of an upcoming post. But when we do prove these value propositions, Livepeer will have a clear path to 100x the demand on the network.
The likely target market users for the network are those startups that are building out vertical specific businesses on top of real-time AI and world model workflows. The ecosystem should look to enable one (or multiple!) startups in each category going after building real-time AI platforms that serve gaming, that serve robotics, that serve synthetic data generation, that serve monitoring and analysis, and all the additional relevant categories. The network’s value propositions will hopefully speak for themselves, but in the early stages of this journey, it is likely the ecosystem will want to use incentives (like investment or credits) to bootstrap these businesses into existence. Each will represent a chance at success, and will bring more demand and proof.
Ultimately, many users of these platforms may choose to build direct on the network themselves. Similarly to how startups start to build on platforms like Heroku, Netlify, or Vercel, and then as they scale and need more control and cost savings they build direct on AWS, and then ultimately move to their own datacenters after reaching even more scale – users of Daydream or a real-time Agent platform built on Livepeer, may ultimately choose to run their own gateways to recognize the cost savings and control and full feature set that comes from doing so. This is a good thing! As it represents even more usage and scale for the network, more proof that as an infrastructure the Livepeer network has product market fit, and that it can absorb all workflows directly. The businesses built on top will provide their own vertical specific bundles of features and services that onboard that vertical specific capacity, but they’ll be complemented by and enabled by the Livepeer Network’s superpowers.
While there’s a lot of work ahead, the Livepeer community has already stepped up to cover tremendous ground on this mission. At the moment by already powering millions of minutes of real-time AI inference per week, by our orchestrators already upgrading their capacity and procurement mechanisms to provide real-time AI-capable compute, and by the Foundation groups already working to evaluate the networks incentives and cryptoeconomics to sustainably fund and reward those contributing to this effort, we’re set up well to capture this enormous opportunity!
`,
+ datePosted: `Nov 13, 2025`,
+ img: `https://blog.livepeer.org/content/images/2025/11/LP_Blog-Header_Nov25_01_moshed-1.png`,
+ excerpt: `For the past year, the Livepeer Ecosystem has been guided by the Cascade vision: a path to transition from a pure streaming and transcoding infrastructure, to an infrastructure that could succeed at providing compute for the future of real-time AI video. The latest Livepeer quarterly report from Messari highlights that this transition is paying off, with network fees up 3x from this time last year, and over 72% of the fees now driven via AI inference. This is exemplified by the growing inspirat`,
+ readingTime: 9,
+ },
+ {
+ title: `Livepeer Onchain Builders - Streamplace: Building the Video Backbone of Decentralized Social`,
+ href: `https://blog.livepeer.org/livepeer-onchain-builders-streamplace-building-the-video-backbone-of-decentralized-social/`,
+ author: `By Livepeer Team`,
+ content: `
Welcome to Livepeer Onchain Builders, a new content series spotlighting the Special Purpose Entities (SPEs) funded by the Livepeer onchain treasury. SPEs are working groups funded by the community treasury to work on specific tasks and are accountable to the community for their delivery. These deep dives will explore how each initiative is driving protocol usage, expanding infrastructure, and pushing the boundaries of what’s possible in decentralized video and AI.
Streamplace is an open-source video streaming platform designed to power decentralized social applications with real-time, creator-first infrastructure. It aims to make livestreaming and video hosting as seamless as TikTok or YouTube, but built on open protocols and self-sovereign identity.
What makes it ambitious? Streamplace is not only building full-stack video infra for federated social networks, it's doing so in a way that prioritizes interoperability, scalability, and public goods. From developer SDKs to end-user apps, Streamplace is building an entire ecosystem.
What is an SPE?
A Special Purpose Entity (SPE) is a focused, community-funded team contributing to the Livepeer ecosystem. SPEs are typically mission-driven groups that operate independently to build infrastructure, applications, or tooling that expand and improve the Livepeer protocol. These teams are funded through proposals to the onchain treasury and are accountable to the community.
SPEs are necessary for the ecosystem because no single team can build every part of a decentralized protocol. SPEs decentralize development, fund public goods, and allow the community to direct resources where they're most needed.
Why do they matter to delegators and stakeholders? Because SPEs grow in usage. More usage = more fees = more rewards. Delegators benefit when the protocol succeeds, and SPEs are among the most direct ways to make that happen.
From Aquareum to Streamplace
A clear goal drives the team behind Streamplace: to build the foundational video infrastructure for the next generation of decentralized social platforms. These platforms, such as Farcaster and the AT Protocol, promise user-owned identity and interoperability, but have thus far lacked robust support for live and on-demand video.
Streamplace solves this by providing a full-stack, developer-friendly video layer that anyone can plug into. It's a bold attempt to make decentralized video feel as native and easy as its Web2 counterparts.
Streamplace started as Aquareum, a project with the same mission and team. This evolution into Streamplace is a rebranding, not a restart, building on past momentum with a sharper focus.
Their vision is to give every user the ability to publish, stream, and remix content with the same ease as TikTok or YouTube, but backed by self-sovereign identity and decentralized networks.
Streamplace homepage
The first proposal delivered:
A unified Aquareum node: bundling the Livepeer stack with indexing and playback.
App releases on iOS, Android, and Web.
Native integrations with AT Protocol and Farcaster.
Support for C2PA metadata and content provenance.
Now, Streamplace continues that momentum with 100,000 LPT in treasury funding and a clear mandate to scale.
Streamplace Graphana dashboard
Why Streamplace Matters
Video is the heart of online social interaction. Yet decentralized social networks have lagged in providing seamless, user-friendly video experiences. Streamplace addresses this by:
Transcoding every livestream through Livepeer, providing decentralized, low-cost processing for global delivery.
Powering partner platforms like Skylight Social, a TikTok alternative backed by Mark Cuban, that recently hit #1 in entertainment on the App Store.
Making it dead-simple to stream or host video through single-binary nodes that anyone can deploy.
Championing public goods, 100% of their code is open source, with a commitment to infrastructure, not monetization lock-in.
Decentralized social, spanning protocols like Farcaster, AT Protocol, and Bluesky, represents a movement toward user-owned networks and open standards. These networks are gaining traction, but video remains a missing layer. That’s where Streamplace comes in.
Video is essential because it's the most engaging, expressive medium for creators and communities. And as these decentralized platforms scale, having real-time, composable video becomes non-negotiable.
Streamplace positions itself as the default video infra layer for this new social stack, and with every stream transcoded through Livepeer, it's also a major driver of protocol usage and visibility.
What Streamplace 2.0 Will Deliver
This new phase of work, funded by the Livepeer treasury, focuses on scale, performance, and ecosystem integration:
Infrastructure Enhancements
Expand server capacity to support growing user bases like Skylight.
Harden video nodes for reliability under real-world load.
Deliver high-quality performance on all platforms: Web, iOS, Android.
Protocol and Developer Growth
Deepen native integration with AT Protocol.
Build SDKs and NPM packages to embed Streamplace easily into other apps.
Ship VOD functionality and new moderation tools.
Community-First Ethos
Launch creator monetization models and stream incentive programs.
Empower streamers with self-hosted app capabilities ("Twitch, but it's your own app").
Maintain full transparency and livestream development.
The Livepeer Angle
Livepeer's decentralized video infrastructure powers every second of video on Streamplace. That means more work for orchestrators, more fees flowing through the protocol, and more incentive for high-quality node operation.
Streamplace strengthens the Livepeer ecosystem in three key ways:
Demand generation: Real-world usage at scale means more consistent transcoding work.
Protocol visibility: High-impact apps like Skylight drive awareness of Livepeer beyond its native circles.
Infrastructure robustness: Streamplace's nodes enhance the distributed capacity of the Livepeer network.
Without Livepeer, a decentralized video stack like Streamplace wouldn’t be possible. And without ambitious apps like Streamplace, Livepeer wouldn’t have the same opportunity to prove its value at scale.
Final Thoughts
Streamplace is a keystone piece of open video infrastructure and a cornerstone in the emerging world of decentralized social media. By fusing creator-first tooling with Livepeer’s scalable infrastructure, it offers a glimpse into what the open internet can become.
As decentralized protocols shift from vision to adoption, the need for native video is urgent. Streamplace, with the support of the Livepeer treasury and a relentless commitment to open-source infrastructure, is meeting that need head-on.
If you're a developer, creator, or community builder, now is the time to get involved.
Do you want to contribute to Streamplace's success? Explore the open roles here.
Interested in building or contributing to the Livepeer ecosystem? Learn more about current and past SPEs, open opportunities, and how to submit your own proposal here.
Follow along, fork the code, or join a stream — the future of social video is open.
Livepeer is a decentralized video infrastructure network for live and on-demand streaming. It has integrated AI Video Compute capabilities (Livepeer AI) by harnessing its massive GPU network and is not building the future of real-time AI video.
`,
+ datePosted: `Aug 14, 2025`,
+ img: `https://blog.livepeer.org/content/images/2025/08/Onchain-Builders-Streamplace.jpg`,
+ excerpt: `Welcome to Livepeer Onchain Builders, a new content series spotlighting the Special Purpose Entities (SPEs) funded by the Livepeer onchain treasury. SPEs are working groups funded by the community treasury to work on specific tasks and are accountable to the community for their delivery. These deep dives will explore how each initiative is driving protocol usage, expanding infrastructure, and pushing the boundaries of what’s possible in decentralized video and AI.
+
+Streamplace is an open-source `,
+ readingTime: 5,
+ },
+ {
+ title: `Builder Story: dotsimulate x Daydream`,
+ href: `https://blog.livepeer.org/builder-story-dotsimulate-x-daydream/`,
+ author: `By Livepeer Team`,
+ content: `
Building StreamDiffusionTD Operator - a Real-Time Generative Video Operator for TouchDesigner, Powered by the Daydream API
StreamDiffusionTD is a TouchDesigner operator that connects real-time inputs like audio, sensors, and camera feeds to StreamDiffusion, enabling live generative visuals controlled in real time. With the Daydream API, it adds remote inference capabilities on top of the existing local GPU inference and unlocks more flexibility for users.
Built by Lyell Hintz, a technical artist and TouchDesigner developer, the operator is used in live shows, installations, and experimental workflows.
Why It Was Built
Lyell began working on the operator a few hours after StreamDiffusion was released on GitHub. He wanted to use it in TouchDesigner - a powerful tool for real time interactive content creation.
“TouchDesigner is the only place this could be controlled from… it can hook into everything else.”
From the start, he avoided creating a “black box.” The operator exposes core parameters like prompt, seed, and ControlNet weights, allowing users to adjust values and see results immediately.
Key Features
Real-time video generation
Prompt and seed morphing
Dynamic ControlNet weighting
Live input support: audio, sensors, camera
Local GPU and Daydream backend options
Instant visual feedback in TouchDesigner
+
+
+
+
+
+
+
+
+
+ 0:00
+
+ /0:26
+
+
+
+
+
+
+
+
+
+
+
Daydream API Integration
StreamDiffusionTD works with the Daydream API, which allows the operator to run on a remote GPU backend. This eliminates the major barrier of requiring a high-end PC with an NVIDIA RTX 4090 to run StreamDiffusion at professional quality, unlocking the flexibility to run it from any location, on any device form factor.
Just drop in your API key and hit “Start Stream.” The backend handles orchestration, model hosting, and frame delivery, so builders can stay focused on their creative and technical workflows.
Setup takes less than 1 minute and once installed, the configuration is remembered for future use.Daydream’s API brings new features to StreamDiffusion:
Multi-controlnet: Mixing different controlnets for better artistic control
IPAdapter: Use images as powerful style guides
TensorRT: Better frame rate for smooth video output
Daydream is adding support for more real time video generation models, and developers can request features, suggest improvements, or build on top of the API itself. It aligns with the values of open tooling and community-led infrastructure.
How Artists can use StreamDiffusionTD in TouchDesigner
Audio-reactive visuals for concerts
Camera-driven generative visuals
Real-time visuals for LED walls and stages
TouchDesigner automation workflows
Because it's built inside TouchDesigner, the operator can be extended using Python, MIDI, OSC, or any other input TouchDesigner supports.
Current State
The operator is live and ready to use, with active development underway for new features and improved performance. It’s a great time to jump in, explore, and help shape what comes next.
`,
+ datePosted: `Aug 5, 2025`,
+ img: `https://blog.livepeer.org/content/images/2025/08/DD_Builder-Story_dotsimulate_01.png`,
+ excerpt: `Building StreamDiffusionTD Operator - a Real-Time Generative Video Operator for TouchDesigner, Powered by the Daydream API
+
+Creator: Lyell Hintz (@dotsimulate)
+Operator: StreamDiffusionTD
+Backends Supported: Local + Daydream (Livepeer)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+0:00
+
+/0:34
+
+
+1×
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Overview
+
+StreamDiffusionTD is a TouchDesigner operator that connects real-time inputs like audio, sensors, and camera feeds to StreamDiffusion, enabling live generative visuals controlled in real time. Wit`,
+ readingTime: 2,
+ },
+ {
+ title: `Livepeer Incorporated! (and realtime AI)`,
+ href: `https://blog.livepeer.org/livepeer-incorporated-and-realtime-ai/`,
+ author: `By Livepeer Team`,
+ content: `
Written by Doug Petkanics, Co-founder and CEO at Livepeer Inc
The past 18 months have been an energizing time to be in the Livepeer Ecosystem. An onchain treasury was introduced to fund public goods via community governance, the community has coalesced around Livepeer’s opportunity to be the leading infrastructure for realtime AI video, and fees and usage of the network have been steadily increasing due to this focus. The Livepeer Foundation has recently launched to steward the 10+ entities in the ecosystem that are core contributors to the project, and is unlocking even more funding around the opportunities recommended in the project’s strategic pillars.
With so much core development, marketing, and growth driven by the ecosystem at large, the company that I co-founded and operate, Livepeer Incorporated, has had the opportunity to shift its focus to what we deem to be the highest priority area of the project where we feel uniquely suited to make an outsized impact: executing a high conviction go to market motion in an attempt to dramatically grow demand on the Livepeer network. We, like many in the ecosystem, are fully bought in to the realtime AI video vision laid out in Livepeer Cascade, and are solely focused on productization to find product market fit for the Livepeer network as the leading infrastructure in the coming world of live video AI. Here is a bit about what Livepeer Inc is focused on, and almost equally as importantly, what we are not focused on in the coming 12 months.
Product Market Fit for Realtime AI Video
As mentioned, the number one priority is to prove that the Livepeer network has product market fit as an infrastructure that runs the latest and greatest in realtime AI video workflows for developers. To do this, we’ll focus on three core things:
Contribute to core network development to ensure Livepeer is an infrastructure that can run realtime AI video workflows.
Build the developer APIs to run these workflows that developers use to build them into applications. This is a natural extension of Livepeer Studio.
Cultivate the leading realtime AI video community. Researchers, builders, and creators interested in this coming category need a home. They will provide the moat that ensures that an open, community led infrastructure will always be more responsive, cost effective, and full featured than centralized alternatives.
We’re going to provide the full stack product, engineering, community, and go to market motion to validate product market fit for this opportunity. This will drive significant fees and growth into the Livepeer network. We’re aligned as large LPT token holders and want the network to succeed - which represents a far bigger opportunity for Livepeer Inc than any revenue related opportunity via SaaS services in the short term. Let’s grow those network fees!
What Livepeer Inc is Not Focused On
While there are many potential products and go to markets that can be executed upon under an ambitious vision of being the world’s open video infrastructure, a single company is more likely to succeed by focusing on only one opportunity at a time. Many alternative demand generating bets will be better served by other self-motivated actors in the ecosystem - especially as the open source software around Livepeer, and the broader ecosystem has matured to the point of providing reliable access points for different categories of use cases.Regarding Livepeer Inc’s learnings on some of these categories:
Transcoding alone has been proven out technically and economically, however the market hasn’t accepted the standalone infrastructure without significant productization, support, SLAs, and enterprise services around it.
Similarly, when bundled with end to end streaming, the offering isn’t significantly differentiated in a crowded and consolidating market.
Livepeer Studio will continue to support existing users at the enterprise level that pay for these surrounding services, while passing the transcoding jobs through to the Livepeer network, but due to the long sales cycle and slow growth, it will not be actively competing to grow this source of demand.
The ecosystem can support aspiring users of transcoding and streaming via projects like Streamplace, the Frameworks SPE, and their supporting teams. One of the core pillars of the Livepeer Foundation’s GTM recommendations is to tackle being the open video infrastructure for web3 social and decentralized streaming, so the ecosystem will prioritize support. This includes aspiring web3-centric streaming users, who culturally align with the values of the project community, but to date have not shown significant growth nor driven significant fees to the network. There’s an opportunity for these projects to crack this nut and help these users grow, if they deem it to be worth the effort!
There are also additional bets that the ecosystem is interested in around the realtime AI mission. These are laid out by the Livepeer Foundation’s GTM Strategy post. Visual avatars for live AI agents is one example. Realtime video analysis and understanding are others. These areas do overlap with the broad theme that Livepeer Inc is focused on - running realtime AI models on live video on the Livepeer network. However as Inc pursues creative AI use cases initially to inspire the broader world in what’s possible, we welcome others in the ecosystem building commercial entities to go after these opportunities. And we will certainly collaborate. If the ecosystem efforts make technical progress, but stop short of commercializing and going to market, these are areas for collaboration with Inc to consider productizing for commercial purposes.
A Simplified View: Foundation and Inc
While the above contains a lot of details about realtime AI and specific demand generating bets on the Livepeer network, there’s a simplified view:
The Livepeer Foundation will steward the Livepeer community, project marketing, and public goods funding to enable recommendations on the project roadmap.
Livepeer Inc will focus on driving demand to the network by building the realtime AI products, go to market services, and AI community - initially in the creative realtime AI video space.
If you’re interested in building within this ecosystem, there are lots of opportunities that both contribute to the core development and operations of the project in service of the realtime AI mission, but also to develop companies that service additional markets not currently being focused on. Hopefully the above post gives you a view into what some of those opportunities and gaps are. Then check out the Livepeer Foundation’s recent forum posts on tactical recommendations, and raise your hand to get involved in the ones of interest.
`,
+ datePosted: `Jul 31, 2025`,
+ img: `https://blog.livepeer.org/content/images/2025/07/e.png`,
+ excerpt: `Written by Doug Petkanics, Co-founder and CEO at Livepeer Inc
+
+The past 18 months have been an energizing time to be in the Livepeer Ecosystem. An onchain treasury was introduced to fund public goods via community governance, the community has coalesced around Livepeer’s opportunity to be the leading infrastructure for realtime AI video, and fees and usage of the network have been steadily increasing due to this focus. The Livepeer Foundation has recently launched to steward the 10+ entities in `,
+ readingTime: 5,
+ },
+]
diff --git a/snippets/automationData/forum/Hero_Livepeer_Forum.png b/snippets/automationData/forum/Hero_Livepeer_Forum.png
new file mode 100644
index 00000000..7805c1bd
Binary files /dev/null and b/snippets/automationData/forum/Hero_Livepeer_Forum.png differ
diff --git a/snippets/automationData/forum/forumData.jsx b/snippets/automationData/forum/forumData.jsx
new file mode 100644
index 00000000..c25d3756
--- /dev/null
+++ b/snippets/automationData/forum/forumData.jsx
@@ -0,0 +1,38 @@
+export const forumData = [
+ {
+ title: "It's time to ACT! Accumulation & the Treasury Ceiling",
+ href: 'https://forum.livepeer.org/t/3153',
+ author: 'By b3nnn (@b3nnn)',
+ content:
+ '
The onchain treasury was designed to provide sustainable public goods funding. It has supported many important and strategic contributions to the Livepeer Ecosystem. The AI SPE, Streamplace, Agent SPE and Cloud have all received funds and made important contributions. And through our onchain governance, the community have shown time and again their thoughtfulness and care for getting decisions right. Your desire to align decisions with long-term health has made us a shining example of simple but effective governance and how people can working together onchain.
The treasury is key to supporting strategic investments to improve UX for stakeholders, effectively manage protocol security, and fund other capital and resource needs for this exciting phase of the project.
As of now, the onchain treasury is currently not accumulating LPT. It was designed not to accept unlimited funding, hit the initial value set as the ceiling, and reset treasury contributions to 0% on or around 31st of March this year. There are a backlog of upcoming projects on highly strategic initiatives that will need treasury support, and we will all feel better about how to allocate funds if we have certainty that new funds are coming into the treasury.
I intend to post a LIP to turn on the treasury rewards again at their initial values:
treasuryRewardCutRate: 10%
treasuryBalanceCeiling: 750000 LPT
The rate of 750000 LPT is currently set as the ceiling so would not be updated in the formal proposal
For what it’s worth, my personal bias is to increase one of these values, but I’m happy to punt that discussion to another day. Having seen the exciting things in the background that will require treasury support in coming weeks, the most pressing item for us as a community is to start getting the treasury repopulated.
I’ll be on the watercooler next week to discuss and am happy to set up an office hours to discuss direct if there is support for that. I look forward to proposing this for a community vote . If you have any input on the contribution percentage that goes into my proposal, please also share your input here.
We propose to address known UX issues and ease and costs to participate by increasing DEX liquidity. Arrakis offers an optimal solution for our specific needs, and we are requesting 250,000 LPT for deployment to a Uniswap v4 pool which will significantly reduce slippage for ecosystem participants
Motivation
The Capital Markets Advisory board made improving onchain liquidity a tactical recommendation, specifically sighting:
Low liquidity levels on our DEX pools (primarily Uniswap on Arbitrum). This creates high slippage when trying to transact with any size, and might refrain larger stakeholders or participants from buying LPT
The much higher ratio of available liquidity on centralized exchanges compared to DEXs drives participants to rely on centralized platforms, exposing them to the inherent risks associated with centralized providers
Further, centralised exchanges often don’t support L2 withdrawals. This results in delayed bridging and withdrawal processing between L1 & L2, impairing overall UX and the efficiency of orchestrators as it relates to capital allocation
In short, improved L2 Dex liquidity is essential for both current and future participants in Livepeer.
Recommended Solution
How to address our challenges is relatively straightforward to describe:
Increase the amount of liquidity on targeted DEX pool/s
Ensure the solution is executing against this goal as agreed
Use funds wisely, ensuring a good balance between what we pay and what we receive
Any solution will require liquidity from the on-chain treasury to start bootstrapping an optimal asset mix. In addition to this liquidity requirement, using a traditional market maker is likely a major expense (in the range of $15-20K per month). While traditional market makers can do a good job in actively managing liquidity, especially on centralised exchanges, they often present new or additional challenges:
Market makers typically operate through asset loan agreements, using our capital to actively manage liquidity across venues. While this model provides flexibility and professional management, it can make visibility into how and where assets are deployed more challenging.
Compared to centralized venues, on-chain liquidity provision is often less economically attractive for market makers. As a result, they may prioritize other strategies or venues where returns are higher, which can limit incentives to deepen on-chain liquidity.
Ensuring that capital is being used effectively by traditional market makers remains challenging, as it requires clear visibility into capital deployment and a deep understanding of the alternative strategies they pursue.
While none of this is insurmountable, it requires significant thought, effort and time to ensure oversight and manage risk.
Arrakis pro is an ideal solution to addresses these challenges.
Arrakis specifically addresses each of these challenges because:
It is built specifically for managing onchain liquidity on DEXs
The assets are stored in a vault controlled by a multisig made up of Livpeer Foundation members. This means the treasury, via the Foundation, can withdraw and return the liquidity at any time
Because it is onchain, and through the features provided in Arrakis pro, we can check and confirm at any time where our assets are and what strategies are being applied.
It rebalances positions by setting up ranges / limit orders, no swaps involved. The solution algorithmically minimises price impact given the allocated capital and bootstraps base asset liquidity without causing negative selling pressure.
Arrakis leverages sophisticated algorithms to increase capital efficiency for the deployed capital and reduce slippage for traders on the DEX pools.
Arrakis vaults hold ~$170M TVL and the team actively manages the on-chain liquidity for over 100 protocols. Projects such as MakerDAO, Lido, Morpho, Gelato, Redstone, Wormhole, Across, Euler, Usual, Syrup, Venice.ai, Ether.fi, etc. are benefiting from the high capital efficiency and cost effectiveness for DEX liquidity optimization enabled by Arrakis PRO.
For more information regarding Arrakis and Arrakis Pro, feel free to have a look at their docs or join their community:
In addition, the team are present here and will address any questions directly - hello @Arrakis
The Ask
We want to significantly decrease slippage and costs for orchestrators and other participants to interact with the network through onchain liquidity.
We are asking for 250,000 LPT (approx. $1M in USD value) to be held in a multisig controlled by the Livepeer Foundation, to be deployed via an onchain vault with Arrakis as a concentrated pool on Uniswap v4.
Management of concentrated liquidity on Uniswap V4 allows for larger trades with minimal price impact, improving the overall trading experience. Savings to participants are substantial at approx. $1500 in slippage reduction on a $25,000 sale of LPT (estimate based on data below).
Comparison of current and estimated price impact (after successful ETH liquidity bootstrapping) for buying LPT and ETH across different amounts
Specification for Livepeer
The Arrakis team uses the existing LPT/ETH pool on the 0.3% fee tier for UniswapV4
Arrakis then deploys a dedicated vault managed by the Arrakis Pro smart contract for this LPT/ETH Uniswap pool.
The Livepeer Foundation team establish a ⅔ Multisig for custody of the funds. If the proposal passes, funds are transferred onchain to this multisig account
Through this Livepeer Foundation multisig, we deposit $1 million worth of $LPT into the Arrakis Pro vault. Transfers in and out of the vault are controlled by the multisig, meaning they cannot be deployed or moved by Arrakis elsewhere
Arrakis Pro will allocate the provided liquidity in a concentrated and fully active market making strategy to facilitate trading on UniswapV4.
The strategy initially operates to bootstrap ETH to establish a 50/50 inventory ratio over the first months. The primary objective is to create price stability by generating deep liquidity and reaching an even inventory over time.
For the services provided, Arrakis charges the following fees:
Arrakis Asset-under-Management (AUM) fee: 1% per year, waived for the first 6 months
Arrakis performance fee: 50% of trading fees the vault generates
FAQ
What are the risks of this model?
Deploying funds to DEX pools bears smart contract risk and general market risk (e.g. token exposure, impermanent loss). Arrakis smart contracts have been audited by leading security firms and currently secure +$150M TVL (https://docs.arrakis.finance/text/resources/audits.html)
What happens to the capital required?
The capital required is deployed by the Livepeer DAO, via a Foundation controlled multisig, to a self-custodial smart contract vault and can be withdrawn at any point in time. Arrakis does not hold custody, nor control the funds deployed outside of the mandate to manage DEX liquidity on Uniswap V4 for the respective trading pair.
Will this impact the current liquidity on CEXs?
Arrakis mandate is to gradually improve on-chain markets and provide deeper liquidity for the respective pair over time on DEX markets. CEX markets will not be affected.
How does the Arrakis model differ from standard AMMs (like Uniswap v3)?
Arrakis provides a sophisticated on-chain market making service, running dedicated algorithmic market making strategies.
Instead of manually deploying funds into the CLAMM pool, Arrakis algorithmically rebalances the position and runs active liquidity management strategies.
Will our liquidity still be actively managed, or will it be passively allocated in a vault?
Close to 100% of the liquidity deployed with an Arrakis vault is actively deployed to the Uniswap CLAMM pool and provides liquidity. Small shares of liquidity remain in the vault as token reserves for rebalancing purposes.
How is the strategy for the vault determined — who sets the parameters, and how often are they rebalanced?
Arrakis quant team fine tunes the strategies and engages in period review cycles along with 24h-365day monitoring and alerting.
Who controls or can modify the AMM strategy parameters?
Arrakis strategies are designed, deployed and maintained by professional quant traders. The Foundation can be involved in discussion in regular intervals as needed to further align on achieving the stated goals.
Will the community have visibility into performance and strategy updates?
The Foundation delegates will receive access to a custom real time analytics dashboard and can share periodic updates to the forum for the community.
What happens to the liquidity if the vault underperforms or becomes unbalanced?
Liquidity is actively rebalanced towards a 50:50 ratio by placing one sided limit maker orders. In adverse market scenarios strategies will adjust to certain market volatility settings.
How do fees compare to centralized market makers?
Centralized market makers work in two models: a) Loan & Option b) Retainer Fix Fee payment. Arrakis works on a profit sharing of trading fees earned (50% captured by the Livepeer DAO, 50% retained by Arrakis for the services provided)
How will LP performance be measured?
LP performance will be measured by market depth, price impact, slippage improvement, total volumes facilitated.
What happens after funds are returned?
It’s important to note that the liquidity in the vault can remain deployed indefinitely, but also returned to the onchain treasury or control by the voters at any time. As funds will now be held in both ETH and LPT, the community can be involved in discussions about how returned funds are stored or used.
This is a large proportion of the current treasury. What gives?
We recognise that this is a large ask relative to the current size and value of the treasury. The size and value of the treasury will be addressed in a separate proposal. As it relates to this proposal, consider that we will reduce slippage costs by approx 2-3X on every dex transaction. The ROI on this proposal will be quite substantial.
Release notes are a way to share work being completed by the Transformation SPE and it’s various contributors. Dive in and explore what has been happening and please reach out or reply with any questions and we will happily expand further.
Hello fellow video enthusiast and web3 supporters,
Thanks for your time in reading my post. (organic-node.eth) Node has been active for about 6 months and everyday has been a great learning experience. My node has been highly reliable with 4 Orchestrators across the globe with possibility to expand more depending on the demand. If you are looking to get in touch with me please reach out to me on discord Organic-Node#9009.
It gives me great pleasure when looking at lenstube videos, thinking that some of these vides may have been transcoded by my Orch. Stakes and delegators enjoy passive income with my low reward cuts and low fee cut and help support robust Orch for a fairer web3 platforms
Stake here: (organic-node.eth)
',
+ replyCount: 1,
+ datePosted: 'Dec 6, 2022',
+ },
+]
diff --git a/snippets/automationData/globals/README.md b/snippets/automationData/globals/README.md
new file mode 100644
index 00000000..d4d5f2e6
--- /dev/null
+++ b/snippets/automationData/globals/README.md
@@ -0,0 +1,89 @@
+# Livepeer Release Updater
+
+Three different solutions for updating the Livepeer release version:
+
+## 1. **n8n Workflow** (livepeer-release-updater.json) CURRENT
+
+This is the recommended approach for your setup. It:
+
+- Polls the go-livepeer releases API every 30 minutes
+- Uses Redis to track the last known version (prevents duplicate updates)
+- Only updates the `LatestRelease` value without touching anything else
+- Commits directly to the docs-v2 branch
+
+## 2. **GitHub Action** (update-livepeer-release.yml) RECOMMENDED
+
+If someone with admin access can add this to the docs repo's
+`.github/workflows/` folder, it will run automatically without needing external
+infrastructure like n8n
+
+## 3. **Node.js Script** (update-livepeer-release.js)
+
+Can be run manually or via cron job from any server with Node.js installed.
+
+Since you mentioned you can't get a GitHub token for the livepeer org but can
+use the GUI, the n8n workflow is your best bet. You'll need to:
+
+1. Create a Personal Access Token from your own GitHub account (Settings →
+ Developer settings → Personal access tokens)
+2. Ensure you have write access to the docs repository
+3. Import the n8n workflow and configure it with your token
+
+The workflow specifically:
+
+- Uses regex to update ONLY the `LatestRelease` value
+- Preserves all other content and formatting
+- Includes error handling and validation
+- Can send notifications when updates occur
+
+All files include the setup guide with detailed instructions for each approach.
+
+### 2. Code for yml
+
+on: schedule: # Run every 30 minutes - cron: '_/30 _ \* \* \*'
+workflow_dispatch:
+
+jobs: check-and-update: runs-on: ubuntu-latest
+
+ steps:
+ - name: Checkout docs repository
+ uses: actions/checkout@v3
+ with:
+ ref: docs-v2
+ token: ${{ secrets.GITHUB_TOKEN }}
+
+ - name: Get latest go-livepeer release
+ id: get_release
+ run: |
+ LATEST_RELEASE=$(curl -s https://api.github.com/repos/livepeer/go-livepeer/releases/latest | jq -r .tag_name)
+ echo "release=${LATEST_RELEASE}" >> $GITHUB_OUTPUT
+ echo "Latest release: ${LATEST_RELEASE}"
+
+ - name: Read current version from globals.jsx
+ id: current_version
+ run: |
+ CURRENT=$(grep -oP 'LatestRelease:\s*["'\'']?\K[^"'\'']+' snippets/automationData/globals/globals.jsx || echo "")
+ echo "current=${CURRENT}" >> $GITHUB_OUTPUT
+ echo "Current version: ${CURRENT}"
+
+ - name: Update globals.jsx if needed
+ if: steps.get_release.outputs.release != steps.current_version.outputs.current
+ run: |
+ # Create backup
+ cp snippets/automationData/globals/globals.jsx snippets/automationData/globals/globals.jsx.bak
+
+ # Update the LatestRelease value
+ sed -i "s/LatestRelease:[[:space:]]*[\"'][^\"']*[\"']/LatestRelease: \"${{ steps.get_release.outputs.release }}\"/" snippets/automationData/globals/globals.jsx
+
+ # Verify the change
+ echo "Updated content:"
+ grep "LatestRelease" snippets/automationData/globals/globals.jsx
+
+ - name: Commit and push if changed
+ if: steps.get_release.outputs.release != steps.current_version.outputs.current
+ run: |
+ git config --local user.email "action@github.com"
+ git config --local user.name "GitHub Action"
+ git add snippets/automationData/globals/globals.jsx
+ git commit -m "chore: update latest release to ${{ steps.get_release.outputs.release }}"
+ git push origin docs-v2
diff --git a/snippets/automationData/globals/globals.jsx b/snippets/automationData/globals/globals.jsx
new file mode 100644
index 00000000..1a218b71
--- /dev/null
+++ b/snippets/automationData/globals/globals.jsx
@@ -0,0 +1 @@
+export const LatestRelease = "v0.8.8";
diff --git a/snippets/components/buttons.jsx b/snippets/components/buttons.jsx
new file mode 100644
index 00000000..ca0ecfb9
--- /dev/null
+++ b/snippets/components/buttons.jsx
@@ -0,0 +1,3 @@
+export const BasicBtn = () => {
+ return
+}
diff --git a/snippets/components/buttons.tsx b/snippets/components/buttons.tsx
new file mode 100644
index 00000000..0f5a12af
--- /dev/null
+++ b/snippets/components/buttons.tsx
@@ -0,0 +1,4 @@
+export type buttonsProps = Record;
+export const BasicBtn = () => {
+ return
+}
diff --git a/snippets/components/cards.jsx b/snippets/components/cards.jsx
new file mode 100644
index 00000000..2ab77e83
--- /dev/null
+++ b/snippets/components/cards.jsx
@@ -0,0 +1,234 @@
+// card layouts
+
+export const PostCard = ({
+ title,
+ content,
+ href,
+ author = 'Unknown',
+ datePosted = null,
+ replyCount = null,
+ icon = 'book-open',
+ authorIcon = 'user-pen',
+ dateIcon = 'calendar',
+ cta = 'Read More',
+ img = null,
+}) => {
+ console.log('item', title, content, href, img)
+ // Show hint if content is likely to overflow (>500 chars as proxy)
+ const showScrollHint = content && content.length > 500
+
+ return (
+
+ {author && (
+
+//
+
+export const CardVideo = ({ embedUrl, title }) => {
+ console.log('Props:', { embedUrl, title }) // Add this
+ return (
+
+
+
+
+
+ {title}
+
+
+
+ )
+}
+
+// Notes: Fetch video information for youtube videos
+
+// Yes, **GitHub Actions is viable**. The workflow would:
+
+// 1. **Trigger on commit/PR** to your code repo
+// 2. **Run your script** to fetch YouTube metadata (title, description)
+// 3. **Update MDX files** with the fetched data
+// 4. **Commit changes** back to the repo (or create a new commit)
+// 5. **Mintlify auto-builds** from the updated repo
+
+// The key is that GitHub Actions can modify files and commit them before Mintlify's build process starts. You'd typically have the action commit directly to the branch or create a new commit that triggers Mintlify's deployment.
+
+// **Example flow:**
+// - Push code → GitHub Action runs → Script fetches YouTube data → Updates MDX → Commits changes → Mintlify detects new commit → Builds docs
+
+// This is similar to how the [agent automation workflow](https://mintlify.com/docs/guides/automate-agent) works with GitHub Actions.
diff --git a/snippets/components/video.tsx b/snippets/components/video.tsx
new file mode 100644
index 00000000..5fbe5e36
--- /dev/null
+++ b/snippets/components/video.tsx
@@ -0,0 +1,63 @@
+export type videoProps = Record;
+// TODO: Deconstruct to change icon props. Only render icon if passed in.
+export const YouTubeVideo = ({ embedUrl, title, hint, caption }) => {
+ return (
+
+
+ {caption}
+
+ ),
+ }
+ : {})}
+ >
+
+
+ )
+}
+
+//Self-hosted video
+// ;
+
+// ;
+ );
+};
diff --git a/snippets/generated/docs-status-table.mdx b/snippets/generated/docs-status-table.mdx
new file mode 100644
index 00000000..bc600ce4
--- /dev/null
+++ b/snippets/generated/docs-status-table.mdx
@@ -0,0 +1,156 @@
+{/* Auto-generated from docs.json - DO NOT EDIT DIRECTLY */}
+{/* To update status/priority/notes, edit v2/docs-status-data.json */}
+
+
+This table is auto-generated from `docs.json`. To update status, priority, or notes, edit `v2/docs-status-data.json` and run `npm run generate-status`.
+
+
+| Tab | Group | Page | Status | Priority | Notes |
+|-----|-------|------|--------|----------|-------|
+| Home | Home | [Landing](/v2/pages/00_home/Landing) | | | |
+| Home | Home | [livepeer tl dr](/v2/pages/00_home/home/livepeer-tl-dr) | | | |
+| Home | Home | [trending at livepeer](/v2/pages/00_home/home/trending-at-livepeer) | | | |
+| Home | Livepeer Showcase | [projects built on livepeer](/v2/pages/00_home/project-showcase/projects-built-on-livepeer) | | | |
+| Home | Livepeer Showcase | [livepeer applications](/v2/pages/00_home/project-showcase/livepeer-applications) | | | |
+| Home | Livepeer Showcase | [industry verticals](/v2/pages/00_home/project-showcase/industry-verticals) | | | |
+| Home | Get Started | [use livepeer](/v2/pages/00_home/get-started/use-livepeer) | | | |
+| Home | Get Started | [stream video quickstart](/v2/pages/00_home/get-started/stream-video-quickstart) | | | |
+| Home | Get Started | [livepeer ai quickstart](/v2/pages/00_home/get-started/livepeer-ai-quickstart) | | | |
+| Home | Get Started | [build on livepeer](/v2/pages/00_home/get-started/build-on-livepeer) | | | |
+| Home | Reference HUB | [redirect](/v2/pages/07_resources/redirect) | | | |
+| Home | Help Center | [redirect](/v2/pages/08_help/redirect) | | | |
+| About | About Livepeer | [livepeer overview](/v2/pages/01_about/about-livepeer/livepeer-overview) | | | |
+| About | About Livepeer | [why livepeer](/v2/pages/01_about/about-livepeer/why-livepeer) | | | |
+| About | About Livepeer | [livepeer evolution](/v2/pages/01_about/about-livepeer/livepeer-evolution) | | | |
+| About | About Livepeer | [livepeer ecosystem](/v2/pages/01_about/about-livepeer/livepeer-ecosystem) | | | |
+| About | Livepeer Protocol | [protocol overview](/v2/pages/01_about/livepeer-protocol/protocol-overview) | | | |
+| About | Livepeer Protocol | [livepeer whitepaper](/v2/pages/01_about/livepeer-protocol/livepeer-whitepaper) | | | |
+| About | Livepeer Protocol | [technical overview](/v2/pages/01_about/livepeer-protocol/technical-overview) | | | |
+| About | Livepeer Network | [actor overview](/v2/pages/01_about/livepeer-network/actor-overview) | | | |
+| About | Livepeer Network | [livepeer token economics](/v2/pages/01_about/livepeer-network/livepeer-token-economics) | | | |
+| About | Livepeer Network | [livepeer governance](/v2/pages/01_about/livepeer-network/livepeer-governance) | | | |
+| About | Reference HUB | [redirect](/v2/pages/07_resources/redirect) | | | |
+| About | Help Center | [redirect](/v2/pages/08_help/redirect) | | | |
+| Community | Livepeer Community | [livepeer community hub](/v2/pages/02_community/livepeer-community/livepeer-community-hub) | | | |
+| Community | Livepeer Community | [livepeer Latest Topics](/v2/pages/02_community/livepeer-community/livepeer-Latest-Topics) | | | |
+| Community | Livepeer Community | [community guidelines](/v2/pages/02_community/livepeer-community/community-guidelines) | | | |
+| Community | Livepeer Connect | [news and socials](/v2/pages/02_community/livepeer-connect/news-and-socials) | | | |
+| Community | Livepeer Connect | [events and community streams](/v2/pages/02_community/livepeer-connect/events-and-community-streams) | | | |
+| Community | Livepeer Connect | [forums and discussions](/v2/pages/02_community/livepeer-connect/forums-and-discussions) | | | |
+| Community | Livepeer Contribute | [contribute](/v2/pages/02_community/livepeer-contribute/contribute) | | | |
+| Community | Livepeer Contribute | [opportunities](/v2/pages/02_community/livepeer-contribute/opportunities) | | | |
+| Community | Livepeer Contribute | [build livepeer](/v2/pages/02_community/livepeer-contribute/build-livepeer) | | | |
+| Community | [MOVE HERE] Help Center | [trending test](/v2/pages/02_community/livepeer-community/trending-test) | | | |
+| Community | [TO DELETE] Tests | [trending test](/v2/pages/02_community/livepeer-community/trending-test) | | | |
+| Community | Reference HUB | [redirect](/v2/pages/07_resources/redirect) | | | |
+| Community | Help Center | [redirect](/v2/pages/08_help/redirect) | | | |
+| Developers | Building on Livepeer | [developer guide](/v2/pages/03_developers/building-on-livepeer/developer-guide) | | | |
+| Developers | Quickstart > Real-time Video | [livepeer ai](/v2/pages/03_developers/building-on-livepeer/quick-starts/livepeer-ai) | | | |
+| Developers | Quickstart > Real-time Video | [README.mdx](/v2/pages/03_developers/livepeer-real-time-video/video-streaming-on-livepeer/README.mdx) | | | |
+| Developers | Quickstart > AI Pipelines | [video streaming](/v2/pages/03_developers/building-on-livepeer/quick-starts/video-streaming) | | | |
+| Developers | Quickstart > AI Pipelines | [livepeer ai](/v2/pages/03_developers/building-on-livepeer/quick-starts/livepeer-ai) | | | |
+| Developers | Developer Platforms | [builder hub](/v2/pages/03_developers/developer-platforms/builder-hub) | | | |
+| Developers | Developer Platforms > Daydream | [daydream](/v2/pages/03_developers/developer-platforms/daydream/daydream) | | | |
+| Developers | Developer Platforms > Livepeer Studio | [livepeer studio](/v2/pages/03_developers/developer-platforms/livepeer-studio/livepeer-studio) | | | |
+| Developers | Developer Platforms > Frameworks | [frameworks](/v2/pages/03_developers/developer-platforms/frameworks/frameworks) | | | |
+| Developers | Developer Platforms > Streamplace | [streamplace](/v2/pages/03_developers/developer-platforms/streamplace/streamplace) | | | |
+| Developers | Developer Platforms > All Ecosystem Products | [ecosystem products](/v2/pages/03_developers/developer-platforms/all-ecosystem/ecosystem-products/ecosystem-products) | | | |
+| Developers | Developer Tools | [tooling hub](/v2/pages/03_developers/developer-tools/tooling-hub) | | | |
+| Developers | Developer Tools | [livepeer explorer](/v2/pages/03_developers/developer-tools/livepeer-explorer) | | | |
+| Developers | Developer Tools | [livepeer cloud](/v2/pages/03_developers/developer-tools/livepeer-cloud) | | | |
+| Developers | Developer Tools | [dashboards](/v2/pages/03_developers/developer-tools/dashboards) | | | |
+| Developers | Guides & Tutorials | [developer guides](/v2/pages/03_developers/guides-and-resources/developer-guides) | | | |
+| Developers | Guides & Tutorials | [resources](/v2/pages/03_developers/guides-and-resources/resources) | | | |
+| Developers | Guides & Tutorials | [developer help](/v2/pages/03_developers/guides-and-resources/developer-help) | | | |
+| Developers | Guides & Tutorials | [contribution guide](/v2/pages/03_developers/guides-and-resources/contribution-guide) | | | |
+| Developers | Builder Opportunities | [dev programs](/v2/pages/03_developers/builder-opportunities/dev-programs) | | | |
+| Developers | Builder Opportunities | [livepeer rfps](/v2/pages/03_developers/builder-opportunities/livepeer-rfps) | | | |
+| Developers | Technical References > SDKs & APIs | [sdks](/v2/pages/03_developers/technical-references-sdks.-and-apis/sdks) | | | |
+| Developers | Technical References > SDKs & APIs | [apis](/v2/pages/03_developers/technical-references-sdks.-and-apis/apis) | | | |
+| Developers | Technical References | [awesome livepeer](/v2/pages/03_developers/technical-references/awesome-livepeer) | | | |
+| Developers | Technical References | [wiki](/v2/pages/03_developers/technical-references/wiki) | | | |
+| Developers | Technical References | [deepwiki](/v2/pages/03_developers/technical-references/deepwiki) | | | |
+| Developers | Changelog & Migrations | [changelog](/v2/pages/07_resources/changelog/changelog) | | | |
+| Developers | Changelog & Migrations | [migration guides](/v2/pages/07_resources/changelog/migration-guides) | | | |
+| Developers | Reference HUB | [redirect](/v2/pages/07_resources/redirect) | | | |
+| Developers | Help Center | [redirect](/v2/pages/08_help/redirect) | | | |
+| Gateways | About Gateways | [gateway explainer](/v2/pages/04_gateways/about-gateways/gateway-explainer) | | | |
+| Gateways | About Gateways | [gateway functions](/v2/pages/04_gateways/about-gateways/gateway-functions) | | | |
+| Gateways | About Gateways | [gateway architecture](/v2/pages/04_gateways/about-gateways/gateway-architecture) | | | |
+| Gateways | About Gateways | [gateways vs orchestrators](/v2/pages/04_gateways/about-gateways/gateways-vs-orchestrators) | | | |
+| Gateways | Gateway Services & Providers | [choosing a gateway](/v2/pages/04_gateways/using-gateways/choosing-a-gateway) | | | |
+| Gateways | Gateway Services & Providers > Gateway Providers | [index](/v2/pages/04_gateways/using-gateways/gateway-providers/index) | | | |
+| Gateways | Gateway Services & Providers > Gateway Providers | [daydream gateway](/v2/pages/04_gateways/using-gateways/gateway-providers/daydream-gateway) | | | |
+| Gateways | Gateway Services & Providers > Gateway Providers | [livepeer studio gateway](/v2/pages/04_gateways/using-gateways/gateway-providers/livepeer-studio-gateway) | | | |
+| Gateways | Gateway Services & Providers > Gateway Providers | [cloud spe gateway](/v2/pages/04_gateways/using-gateways/gateway-providers/cloud-spe-gateway) | | | |
+| Gateways | Gateway Services & Providers > Gateway Providers | [streamplace](/v2/pages/04_gateways/using-gateways/gateway-providers/streamplace) | | | |
+| Gateways | Run Your Own Gateway | [run a gateway](/v2/pages/04_gateways/run-a-gateway/run-a-gateway) | | | |
+| Gateways | Run Your Own Gateway > Requirements | [requirements](/v2/pages/04_gateways/run-a-gateway/requirements/requirements) | | | |
+| Gateways | Run Your Own Gateway > Installation | [install overview](/v2/pages/04_gateways/run-a-gateway/install/install-overview) | | | |
+| Gateways | Run Your Own Gateway > Installation | [docker install](/v2/pages/04_gateways/run-a-gateway/install/docker-install) | | | |
+| Gateways | Run Your Own Gateway > Installation | [linux install](/v2/pages/04_gateways/run-a-gateway/install/linux-install) | | | |
+| Gateways | Run Your Own Gateway > Installation | [windows install](/v2/pages/04_gateways/run-a-gateway/install/windows-install) | | | |
+| Gateways | Run Your Own Gateway > Installation | [community projects](/v2/pages/04_gateways/run-a-gateway/install/community-projects) | | | |
+| Gateways | Run Your Own Gateway > Publish Services | [publish offerings](/v2/pages/04_gateways/run-a-gateway/publish/publish-offerings) | | | |
+| Gateways | Gateway Guides & Resources > Gateway Tools & Dashboards | [explorer](/v2/pages/04_gateways/gateway-tools/explorer) | | | |
+| Gateways | Gateway Guides & Resources > Gateway Tools & Dashboards | [livepeer tools](/v2/pages/04_gateways/gateway-tools/livepeer-tools) | | | |
+| Gateways | Gateway Guides & Resources > Community Resources | [community guides](/v2/pages/04_gateways/guides-references/community-guides) | | | |
+| Gateways | Gateway Guides & Resources > Community Resources | [community projects](/v2/pages/04_gateways/guides-references/community-projects) | | | |
+| Gateways | Gateway Guides & Resources > Technical References | [technical architecture](/v2/pages/04_gateways/guides-references/technical-architecture) | | | |
+| Gateways | Gateway Guides & Resources > Technical References | [protocol specifications](/v2/pages/04_gateways/guides-references/protocol-specifications) | | | |
+| Gateways | Gateway Guides & Resources | [FAQ](/v2/pages/04_gateways/guides-references/FAQ) | | | |
+| Gateways | [moved] Gateway Tools & Dashboards | [explorer](/v2/pages/04_gateways/gateway-tools/explorer) | | | |
+| Gateways | [moved] Gateway Tools & Dashboards | [livepeer tools](/v2/pages/04_gateways/gateway-tools/livepeer-tools) | | | |
+| Gateways | Reference HUB | [redirect](/v2/pages/07_resources/redirect) | | | |
+| Gateways | Help Center | [redirect](/v2/pages/08_help/redirect) | | | |
+| GPU Nodes | About Orchestrators (GPU Nodes) | [overview](/v2/pages/05_orchestrators/about-orchestrators/overview) | | | |
+| GPU Nodes | About Orchestrators (GPU Nodes) > Orchestrator Functions | [transcoding](/v2/pages/05_orchestrators/about-orchestrators/orchestrator-functions/transcoding) | | | |
+| GPU Nodes | About Orchestrators (GPU Nodes) > Orchestrator Functions | [ai pipelines](/v2/pages/05_orchestrators/about-orchestrators/orchestrator-functions/ai-pipelines) | | | |
+| GPU Nodes | Set up an Orchestrator | [hardware requirements](/v2/pages/05_orchestrators/setting-up-an-orchestrator/hardware-requirements) | | | |
+| GPU Nodes | Set up an Orchestrator | [orchestrator stats](/v2/pages/05_orchestrators/setting-up-an-orchestrator/orchestrator-stats) | | | |
+| GPU Nodes | Set up an Orchestrator > Setting Up An Orchestrator | [quickstart add your gpu to livepeer](/v2/pages/05_orchestrators/setting-up-an-orchestrator/setting-up-an-orchestrator/quickstart-add-your-gpu-to-livepeer) | | | |
+| GPU Nodes | Set up an Orchestrator > Setting Up An Orchestrator | [join a pool](/v2/pages/05_orchestrators/setting-up-an-orchestrator/join-a-pool) | | | |
+| GPU Nodes | Set up an Orchestrator > Setting Up An Orchestrator | [data centres and large scale hardware providers](/v2/pages/05_orchestrators/setting-up-an-orchestrator/setting-up-an-orchestrator/data-centres-and-large-scale-hardware-providers) | | | |
+| GPU Nodes | Orchestrator Tooling | [orchestrator tools](/v2/pages/05_orchestrators/orchestrator-tooling/orchestrator-tools) | | | |
+| GPU Nodes | Orchestrator Tooling | [orchestrator dashboards](/v2/pages/05_orchestrators/orchestrator-tooling/orchestrator-dashboards) | | | |
+| GPU Nodes | Orchestrator Guides & Resources | [orchestrator guides and references](/v2/pages/05_orchestrators/orchestrator-guides-and-references/orchestrator-guides-and-references) | | | |
+| GPU Nodes | Orchestrator Guides & Resources | [orchestrator resources](/v2/pages/05_orchestrators/orchestrator-guides-and-references/orchestrator-resources) | | | |
+| GPU Nodes | Orchestrator Guides & Resources | [orchestrator community and help](/v2/pages/05_orchestrators/orchestrator-guides-and-references/orchestrator-community-and-help) | | | |
+| GPU Nodes | Reference HUB | [redirect](/v2/pages/07_resources/redirect) | | | |
+| GPU Nodes | Help Center | [redirect](/v2/pages/08_help/redirect) | | | |
+| Delegators & LPT | About LPT | [overview](/v2/pages/06_delegators/about-lpt-livepeer-token/overview) | | | |
+| Delegators & LPT | About LPT | [why have a token](/v2/pages/06_delegators/about-lpt-livepeer-token/why-have-a-token) | | | |
+| Delegators & LPT | About LPT | [livepeer token economics](/v2/pages/06_delegators/about-lpt-livepeer-token/livepeer-token-economics) | | | |
+| Delegators & LPT | About LPT | [how to get lpt](/v2/pages/06_delegators/about-lpt-livepeer-token/how-to-get-lpt) | | | |
+| Delegators & LPT | About LPT | [delegators](/v2/pages/06_delegators/about-lpt-livepeer-token/delegators) | | | |
+| Delegators & LPT | Delegating LPT | [overview](/v2/pages/06_delegators/delegating-lpt/overview) | | | |
+| Delegators & LPT | Delegating LPT | [delegation economics](/v2/pages/06_delegators/delegating-lpt/delegation-economics) | | | |
+| Delegators & LPT | Delegating LPT | [how to delegate lpt](/v2/pages/06_delegators/delegating-lpt/how-to-delegate-lpt) | | | |
+| Delegators & LPT | Livepeer Governance | [overview](/v2/pages/06_delegators/livepeer-governance/overview) | | | |
+| Delegators & LPT | Livepeer Governance | [livepeer governance](/v2/pages/06_delegators/livepeer-governance/livepeer-governance) | | | |
+| Delegators & LPT | Livepeer Governance | [livepeer treasury](/v2/pages/06_delegators/livepeer-governance/livepeer-treasury) | | | |
+| Delegators & LPT | Guides & Resources | [lpt exchanges](/v2/pages/06_delegators/token-resources/lpt-exchanges) | | | |
+| Delegators & LPT | Reference HUB | [redirect](/v2/pages/07_resources/redirect) | | | |
+| Delegators & LPT | Help Center | [redirect](/v2/pages/08_help/redirect) | | | |
+| Reference HUB | Home | [resources_hub](/v2/pages/07_resources/resources_hub) | | | |
+| Reference HUB | Documentation Guide | [documentation overview](/v2/pages/07_resources/documentation-guide/documentation-overview) | | | |
+| Reference HUB | Documentation Guide | [documentation guide](/v2/pages/07_resources/documentation-guide/documentation-guide) | | | |
+| Reference HUB | Documentation Guide | [docs features and ai integrations](/v2/pages/07_resources/documentation-guide/docs-features-and-ai-integrations) | | | |
+| Reference HUB | Documentation Guide | [contribute to the docs](/v2/pages/07_resources/documentation-guide/contribute-to-the-docs) | | | |
+| Reference HUB | Livepeer Concepts | [livepeer core concepts](/v2/pages/07_resources/concepts/livepeer-core-concepts) | | | |
+| Reference HUB | Livepeer Concepts | [livepeer glossary](/v2/pages/07_resources/livepeer-glossary) | | | |
+| Reference HUB | Livepeer Concepts | [livepeer actors](/v2/pages/07_resources/concepts/livepeer-actors) | | | |
+| Reference HUB | Developer References | [livepeer glossary](/v2/pages/07_resources/livepeer-glossary) | | | |
+| Reference HUB | Gateway References | [livepeer ai content directory](/v2/pages/07_resources/ai-inference-on-livepeer/livepeer-ai/livepeer-ai-content-directory) | | | |
+| Reference HUB | Orchestrator References | [livepeer glossary](/v2/pages/07_resources/livepeer-glossary) | | | |
+| Reference HUB | LPT & Delegator References | [livepeer glossary](/v2/pages/07_resources/livepeer-glossary) | | | |
+| Reference HUB | Community Resources | [livepeer glossary](/v2/pages/07_resources/livepeer-glossary) | | | |
+| Reference HUB | Partner Resources | [livepeer glossary](/v2/pages/07_resources/livepeer-glossary) | | | |
+| Reference HUB | Help Center | [livepeer glossary](/v2/pages/07_resources/livepeer-glossary) | | | |
+| Reference HUB | Changelog | [changelog](/v2/pages/00_home/changelog/changelog) | | | |
+| Reference HUB | Changelog | [migration guide](/v2/pages/00_home/changelog/migration-guide) | | | |
+| Reference HUB | Help Center | [redirect](/v2/pages/08_help/redirect) | | | |
+
+---
+
+**Total Pages:** 143
diff --git a/snippets/generated/docs-structure-diagram.mdx b/snippets/generated/docs-structure-diagram.mdx
new file mode 100644
index 00000000..2fa2c2a4
--- /dev/null
+++ b/snippets/generated/docs-structure-diagram.mdx
@@ -0,0 +1,379 @@
+{/* Auto-generated from docs.json - DO NOT EDIT DIRECTLY */}
+
+```mermaid
+%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui', 'fontSize': '14px' }}}%%
+flowchart TB
+ subgraph Tabs[" "]
+ direction LR
+ n3[["Home"]]
+ n7[["About"]]
+ n13[["Community"]]
+ n22[["Developers"]]
+ n28[["Gateways"]]
+ n33[["GPU Nodes"]]
+ n39[["Delegators & LPT"]]
+ n52[["Reference HUB"]]
+ end
+
+ n3 --> n0["Home"]
+ n0 --> n1["Livepeer Showcase"]
+ n1 --> n2["Get Started"]
+ n7 --> n4["About Livepeer"]
+ n4 --> n5["Livepeer Protocol"]
+ n5 --> n6["Livepeer Network"]
+ n13 --> n8["Livepeer Community"]
+ n8 --> n9["Livepeer Connect"]
+ n9 --> n10["Livepeer Contribute"]
+ n10 --> n11["[MOVE HERE] Help Center"]
+ n11 --> n12["[TO DELETE] Tests"]
+ n22 --> n14["Building on Livepeer"]
+ n14 --> n15["Quickstart"]
+ n15 --> n16["Developer Platforms"]
+ n16 --> n17["Developer Tools"]
+ n17 --> n18["Guides & Tutorials"]
+ n18 --> n19["Builder Opportunities"]
+ n19 --> n20["Technical References"]
+ n20 --> n21["Changelog & Migrations"]
+ n28 --> n23["About Gateways"]
+ n23 --> n24["Gateway Services & Providers"]
+ n24 --> n25["Run Your Own Gateway"]
+ n25 --> n26["Gateway Guides & Resources"]
+ n26 --> n27["[moved] Gateway Tools & Dashboards"]
+ n33 --> n29["About Orchestrators (GPU Nodes)"]
+ n29 --> n30["Set up an Orchestrator"]
+ n30 --> n31["Orchestrator Tooling"]
+ n31 --> n32["Orchestrator Guides & Resources"]
+ n39 --> n34["About LPT"]
+ n34 --> n35["Delegating LPT"]
+ n35 --> n36["Livepeer Governance"]
+ n36 --> n37["Livepeer Treasury"]
+ n37 --> n38["Guides & Resources"]
+ n52 --> n40["Home"]
+ n40 --> n41["Documentation Guide"]
+ n41 --> n42["Livepeer Concepts"]
+ n42 --> n43["Developer References"]
+ n43 --> n44["Gateway References"]
+ n44 --> n45["Orchestrator References"]
+ n45 --> n46["LPT & Delegator References"]
+ n46 --> n47["Community Resources"]
+ n47 --> n48["Partner Resources"]
+ n48 --> n49["Help Center"]
+ n49 --> n50["Technical References"]
+ n50 --> n51["Changelog"]
+
+ classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:1px
+ classDef tab fill:#0d0d0d,color:#2d9a67,stroke:#2d9a67,stroke-width:2px
+ style Tabs fill:#0d0d0d,stroke:#2d9a67,stroke-width:2px
+ class n3 tab
+ class n7 tab
+ class n13 tab
+ class n22 tab
+ class n28 tab
+ class n33 tab
+ class n39 tab
+ class n52 tab
+```
+
+---
+
+## Page Structure by Tab
+
+
+
+
+### Home
+
+- [Landing](/v2/pages/00_home/Landing)
+- [livepeer tl dr](/v2/pages/00_home/home/livepeer-tl-dr)
+- [trending at livepeer](/v2/pages/00_home/home/trending-at-livepeer)
+
+### Livepeer Showcase
+
+- [projects built on livepeer](/v2/pages/00_home/project-showcase/projects-built-on-livepeer)
+- [livepeer applications](/v2/pages/00_home/project-showcase/livepeer-applications)
+- [industry verticals](/v2/pages/00_home/project-showcase/industry-verticals)
+
+### Get Started
+
+- [use livepeer](/v2/pages/00_home/get-started/use-livepeer)
+- [stream video quickstart](/v2/pages/00_home/get-started/stream-video-quickstart)
+- [livepeer ai quickstart](/v2/pages/00_home/get-started/livepeer-ai-quickstart)
+- [build on livepeer](/v2/pages/00_home/get-started/build-on-livepeer)
+
+
+
+
+
+### About Livepeer
+
+- [livepeer overview](/v2/pages/01_about/about-livepeer/livepeer-overview)
+- [why livepeer](/v2/pages/01_about/about-livepeer/why-livepeer)
+- [livepeer evolution](/v2/pages/01_about/about-livepeer/livepeer-evolution)
+- [livepeer ecosystem](/v2/pages/01_about/about-livepeer/livepeer-ecosystem)
+
+### Livepeer Protocol
+
+- [protocol overview](/v2/pages/01_about/livepeer-protocol/protocol-overview)
+- [livepeer whitepaper](/v2/pages/01_about/livepeer-protocol/livepeer-whitepaper)
+- [technical overview](/v2/pages/01_about/livepeer-protocol/technical-overview)
+
+### Livepeer Network
+
+- [actor overview](/v2/pages/01_about/livepeer-network/actor-overview)
+- [livepeer token economics](/v2/pages/01_about/livepeer-network/livepeer-token-economics)
+- [livepeer governance](/v2/pages/01_about/livepeer-network/livepeer-governance)
+
+
+
+
+
+### Livepeer Community
+
+- [livepeer community hub](/v2/pages/02_community/livepeer-community/livepeer-community-hub)
+- [livepeer Latest Topics](/v2/pages/02_community/livepeer-community/livepeer-Latest-Topics)
+- [community guidelines](/v2/pages/02_community/livepeer-community/community-guidelines)
+
+### Livepeer Connect
+
+- [news and socials](/v2/pages/02_community/livepeer-connect/news-and-socials)
+- [events and community streams](/v2/pages/02_community/livepeer-connect/events-and-community-streams)
+- [forums and discussions](/v2/pages/02_community/livepeer-connect/forums-and-discussions)
+
+### Livepeer Contribute
+
+- [contribute](/v2/pages/02_community/livepeer-contribute/contribute)
+- [opportunities](/v2/pages/02_community/livepeer-contribute/opportunities)
+- [build livepeer](/v2/pages/02_community/livepeer-contribute/build-livepeer)
+
+### [MOVE HERE] Help Center
+
+- [trending test](/v2/pages/02_community/livepeer-community/trending-test)
+
+### [TO DELETE] Tests
+
+- [trending test](/v2/pages/02_community/livepeer-community/trending-test)
+
+
+
+
+
+### Building on Livepeer
+
+- [developer guide](/v2/pages/03_developers/building-on-livepeer/developer-guide)
+
+### Quickstart
+
+- [livepeer ai](/v2/pages/03_developers/building-on-livepeer/quick-starts/livepeer-ai)
+- [README.mdx](/v2/pages/03_developers/livepeer-real-time-video/video-streaming-on-livepeer/README.mdx)
+- [video streaming](/v2/pages/03_developers/building-on-livepeer/quick-starts/video-streaming)
+- [livepeer ai](/v2/pages/03_developers/building-on-livepeer/quick-starts/livepeer-ai)
+
+### Developer Platforms
+
+- [builder hub](/v2/pages/03_developers/developer-platforms/builder-hub)
+- [daydream](/v2/pages/03_developers/developer-platforms/daydream/daydream)
+- [livepeer studio](/v2/pages/03_developers/developer-platforms/livepeer-studio/livepeer-studio)
+- [frameworks](/v2/pages/03_developers/developer-platforms/frameworks/frameworks)
+- [streamplace](/v2/pages/03_developers/developer-platforms/streamplace/streamplace)
+- [ecosystem products](/v2/pages/03_developers/developer-platforms/all-ecosystem/ecosystem-products/ecosystem-products)
+
+### Developer Tools
+
+- [tooling hub](/v2/pages/03_developers/developer-tools/tooling-hub)
+- [livepeer explorer](/v2/pages/03_developers/developer-tools/livepeer-explorer)
+- [livepeer cloud](/v2/pages/03_developers/developer-tools/livepeer-cloud)
+- [dashboards](/v2/pages/03_developers/developer-tools/dashboards)
+
+### Guides & Tutorials
+
+- [developer guides](/v2/pages/03_developers/guides-and-resources/developer-guides)
+- [resources](/v2/pages/03_developers/guides-and-resources/resources)
+- [developer help](/v2/pages/03_developers/guides-and-resources/developer-help)
+- [contribution guide](/v2/pages/03_developers/guides-and-resources/contribution-guide)
+
+### Builder Opportunities
+
+- [dev programs](/v2/pages/03_developers/builder-opportunities/dev-programs)
+- [livepeer rfps](/v2/pages/03_developers/builder-opportunities/livepeer-rfps)
+
+### Technical References
+
+- [sdks](/v2/pages/03_developers/technical-references-sdks.-and-apis/sdks)
+- [apis](/v2/pages/03_developers/technical-references-sdks.-and-apis/apis)
+- [awesome livepeer](/v2/pages/03_developers/technical-references/awesome-livepeer)
+- [wiki](/v2/pages/03_developers/technical-references/wiki)
+- [deepwiki](/v2/pages/03_developers/technical-references/deepwiki)
+
+### Changelog & Migrations
+
+- [changelog](/v2/pages/07_resources/changelog/changelog)
+- [migration guides](/v2/pages/07_resources/changelog/migration-guides)
+
+
+
+
+
+### About Gateways
+
+- [gateway explainer](/v2/pages/04_gateways/about-gateways/gateway-explainer)
+- [gateway functions](/v2/pages/04_gateways/about-gateways/gateway-functions)
+- [gateway architecture](/v2/pages/04_gateways/about-gateways/gateway-architecture)
+- [gateways vs orchestrators](/v2/pages/04_gateways/about-gateways/gateways-vs-orchestrators)
+
+### Gateway Services & Providers
+
+- [choosing a gateway](/v2/pages/04_gateways/using-gateways/choosing-a-gateway)
+- [index](/v2/pages/04_gateways/using-gateways/gateway-providers/index)
+- [daydream gateway](/v2/pages/04_gateways/using-gateways/gateway-providers/daydream-gateway)
+- [livepeer studio gateway](/v2/pages/04_gateways/using-gateways/gateway-providers/livepeer-studio-gateway)
+- [cloud spe gateway](/v2/pages/04_gateways/using-gateways/gateway-providers/cloud-spe-gateway)
+- [streamplace](/v2/pages/04_gateways/using-gateways/gateway-providers/streamplace)
+
+### Run Your Own Gateway
+
+- [run a gateway](/v2/pages/04_gateways/run-a-gateway/run-a-gateway)
+- [requirements](/v2/pages/04_gateways/run-a-gateway/requirements/requirements)
+- [install overview](/v2/pages/04_gateways/run-a-gateway/install/install-overview)
+- [docker install](/v2/pages/04_gateways/run-a-gateway/install/docker-install)
+- [linux install](/v2/pages/04_gateways/run-a-gateway/install/linux-install)
+- [windows install](/v2/pages/04_gateways/run-a-gateway/install/windows-install)
+- [community projects](/v2/pages/04_gateways/run-a-gateway/install/community-projects)
+- [publish offerings](/v2/pages/04_gateways/run-a-gateway/publish/publish-offerings)
+
+### Gateway Guides & Resources
+
+- [explorer](/v2/pages/04_gateways/gateway-tools/explorer)
+- [livepeer tools](/v2/pages/04_gateways/gateway-tools/livepeer-tools)
+- [community guides](/v2/pages/04_gateways/guides-references/community-guides)
+- [community projects](/v2/pages/04_gateways/guides-references/community-projects)
+- [technical architecture](/v2/pages/04_gateways/guides-references/technical-architecture)
+- [protocol specifications](/v2/pages/04_gateways/guides-references/protocol-specifications)
+- [FAQ](/v2/pages/04_gateways/guides-references/FAQ)
+
+### [moved] Gateway Tools & Dashboards
+
+- [explorer](/v2/pages/04_gateways/gateway-tools/explorer)
+- [livepeer tools](/v2/pages/04_gateways/gateway-tools/livepeer-tools)
+
+
+
+
+
+### About Orchestrators (GPU Nodes)
+
+- [overview](/v2/pages/05_orchestrators/about-orchestrators/overview)
+- [transcoding](/v2/pages/05_orchestrators/about-orchestrators/orchestrator-functions/transcoding)
+- [ai pipelines](/v2/pages/05_orchestrators/about-orchestrators/orchestrator-functions/ai-pipelines)
+
+### Set up an Orchestrator
+
+- [hardware requirements](/v2/pages/05_orchestrators/setting-up-an-orchestrator/hardware-requirements)
+- [orchestrator stats](/v2/pages/05_orchestrators/setting-up-an-orchestrator/orchestrator-stats)
+- [quickstart add your gpu to livepeer](/v2/pages/05_orchestrators/setting-up-an-orchestrator/setting-up-an-orchestrator/quickstart-add-your-gpu-to-livepeer)
+- [join a pool](/v2/pages/05_orchestrators/setting-up-an-orchestrator/join-a-pool)
+- [data centres and large scale hardware providers](/v2/pages/05_orchestrators/setting-up-an-orchestrator/setting-up-an-orchestrator/data-centres-and-large-scale-hardware-providers)
+
+### Orchestrator Tooling
+
+- [orchestrator tools](/v2/pages/05_orchestrators/orchestrator-tooling/orchestrator-tools)
+- [orchestrator dashboards](/v2/pages/05_orchestrators/orchestrator-tooling/orchestrator-dashboards)
+
+### Orchestrator Guides & Resources
+
+- [orchestrator guides and references](/v2/pages/05_orchestrators/orchestrator-guides-and-references/orchestrator-guides-and-references)
+- [orchestrator resources](/v2/pages/05_orchestrators/orchestrator-guides-and-references/orchestrator-resources)
+- [orchestrator community and help](/v2/pages/05_orchestrators/orchestrator-guides-and-references/orchestrator-community-and-help)
+
+
+
+
+
+### About LPT
+
+- [overview](/v2/pages/06_delegators/about-lpt-livepeer-token/overview)
+- [why have a token](/v2/pages/06_delegators/about-lpt-livepeer-token/why-have-a-token)
+- [livepeer token economics](/v2/pages/06_delegators/about-lpt-livepeer-token/livepeer-token-economics)
+- [how to get lpt](/v2/pages/06_delegators/about-lpt-livepeer-token/how-to-get-lpt)
+- [delegators](/v2/pages/06_delegators/about-lpt-livepeer-token/delegators)
+
+### Delegating LPT
+
+- [overview](/v2/pages/06_delegators/delegating-lpt/overview)
+- [delegation economics](/v2/pages/06_delegators/delegating-lpt/delegation-economics)
+- [how to delegate lpt](/v2/pages/06_delegators/delegating-lpt/how-to-delegate-lpt)
+
+### Livepeer Governance
+
+- [overview](/v2/pages/06_delegators/livepeer-governance/overview)
+- [livepeer governance](/v2/pages/06_delegators/livepeer-governance/livepeer-governance)
+- [livepeer treasury](/v2/pages/06_delegators/livepeer-governance/livepeer-treasury)
+
+### Livepeer Treasury
+
+*No pages*
+
+### Guides & Resources
+
+- [lpt exchanges](/v2/pages/06_delegators/token-resources/lpt-exchanges)
+
+
+
+
+
+### Home
+
+- [resources_hub](/v2/pages/07_resources/resources_hub)
+
+### Documentation Guide
+
+- [documentation overview](/v2/pages/07_resources/documentation-guide/documentation-overview)
+- [documentation guide](/v2/pages/07_resources/documentation-guide/documentation-guide)
+- [docs features and ai integrations](/v2/pages/07_resources/documentation-guide/docs-features-and-ai-integrations)
+- [contribute to the docs](/v2/pages/07_resources/documentation-guide/contribute-to-the-docs)
+
+### Livepeer Concepts
+
+- [livepeer core concepts](/v2/pages/07_resources/concepts/livepeer-core-concepts)
+- [livepeer glossary](/v2/pages/07_resources/livepeer-glossary)
+- [livepeer actors](/v2/pages/07_resources/concepts/livepeer-actors)
+
+### Developer References
+
+- [livepeer glossary](/v2/pages/07_resources/livepeer-glossary)
+
+### Gateway References
+
+- [livepeer ai content directory](/v2/pages/07_resources/ai-inference-on-livepeer/livepeer-ai/livepeer-ai-content-directory)
+
+### Orchestrator References
+
+- [livepeer glossary](/v2/pages/07_resources/livepeer-glossary)
+
+### LPT & Delegator References
+
+- [livepeer glossary](/v2/pages/07_resources/livepeer-glossary)
+
+### Community Resources
+
+- [livepeer glossary](/v2/pages/07_resources/livepeer-glossary)
+
+### Partner Resources
+
+- [livepeer glossary](/v2/pages/07_resources/livepeer-glossary)
+
+### Help Center
+
+- [livepeer glossary](/v2/pages/07_resources/livepeer-glossary)
+
+### Technical References
+
+*No pages*
+
+### Changelog
+
+- [changelog](/v2/pages/00_home/changelog/changelog)
+- [migration guide](/v2/pages/00_home/changelog/migration-guide)
+
+
+
+
diff --git a/snippets/variables.mdx b/snippets/variables.mdx
new file mode 100644
index 00000000..37eeea3a
--- /dev/null
+++ b/snippets/variables.mdx
@@ -0,0 +1,4 @@
+export const url = 'https://www.youtube.com/watch?v=9yLIPZ4iBLw'
+export const caption = 'Co-Founder & CTO Doug Petkanics on Livepeer (2025)'
+export const embedUrl = 'https://www.youtube.com/embed/9yLIPZ4iBLw'
+export const title = `Reinventing Live Video: AI & Decentralization | Co-Founder and CTO Doug Petkanics`
diff --git a/snippets/variables/about.mdx b/snippets/variables/about.mdx
new file mode 100644
index 00000000..e69de29b
diff --git a/snippets/variables/community.mdx b/snippets/variables/community.mdx
new file mode 100644
index 00000000..e69de29b
diff --git a/snippets/variables/delegators.mdx b/snippets/variables/delegators.mdx
new file mode 100644
index 00000000..e69de29b
diff --git a/snippets/variables/developers.mdx b/snippets/variables/developers.mdx
new file mode 100644
index 00000000..e69de29b
diff --git a/snippets/variables/gateways.mdx b/snippets/variables/gateways.mdx
new file mode 100644
index 00000000..e69de29b
diff --git a/snippets/variables/home.mdx b/snippets/variables/home.mdx
new file mode 100644
index 00000000..e78bce65
--- /dev/null
+++ b/snippets/variables/home.mdx
@@ -0,0 +1,134 @@
+//TODO: LINKS WRONG
+
+{/* HOME/HOME */}
+
+{/* HOME/TLDR */}
+export const tldrList = [
+{
+title: 'New Users',
+content: 'Learn what Livepeer is and how it can benefit you.',
+icon: 'user',
+link: '../../01_about/about-home/',
+},
+{
+title: 'Project Showcase',
+content: 'See real-world projects and get inspired.',
+icon: 'lightbulb',
+link: '../../01_about/project-showcase/',
+},
+{
+title: 'Video Streaming',
+content: 'Start streaming or broadcasting live.',
+icon: 'video',
+link: '../../03_developers/livepeer-real-time-video/',
+},
+{
+title: 'AI Pipelines',
+content: 'Explore AI capabilities using Livepeer.',
+icon: 'robot',
+link: '../../03_developers/ai-inference-on-livepeer/',
+},
+{
+title: 'Developers',
+content: 'Build on the Livepeer open network.',
+icon: 'Code',
+link: '../../03_developers/building-on-livepeer/',
+},
+{
+title: 'Token Holders',
+content: 'Delegate LPT and engage as a token participant.',
+icon: 'Coins',
+link: '../../06_delegators/delegating-lpt/',
+},
+{
+title: 'Gateway Operators',
+content: 'Access compute or set up a gateway.',
+icon: 'Network-Wired',
+link: '../../04_gateways/',
+},
+{
+title: 'Orchestrators',
+content: 'Monetise your GPU.',
+icon: 'Microchip',
+link: '../../05_orchestrators/orchestrator-setup-add-a-gpu-to-livepeer/',
+},
+{
+title: 'Research & Writing',
+content: 'Read or contribute deep research.',
+icon: 'Book-Open',
+link: '../../07_resources/references/',
+},
+{
+title: 'Partners & Clients',
+content: 'Explore partnership opportunities.',
+icon: 'Handshake',
+link: '',
+},
+]
+
+{/* HOME/TRENDING */}
+
+{/* DOCUMENTATION/OVERVIEW */}
+
+{/* DOCUMENTATION/GUIDE */}
+
+{/* DOCUMENTATION/FEATURES */}
+
+{/* DOCUMENTATION/CONTRIBUTE */}
+
+{/* CHANGELOG/CHANGELOG */}
+
+{/* CHANGELOG/MIGRATE */}
+
+{/* UNUSED/ARCHIVED */}
+// export const tldrTitles = [
+// 'New Users',
+// 'Project Showcase',
+// 'Video Streaming',
+// 'AI Pipelines',
+// 'Developers',
+// 'Token Holders',
+// 'Gateway Operators',
+// 'Orchestrators',
+// 'Research & Writing',
+// 'Partners & Clients',
+// ]
+
+// export const tldrContents = [
+// 'Learn what Livepeer is and how it can benefit you.',
+// 'See real-world projects and get inspired.',
+// 'Start streaming or broadcasting live.',
+// 'Explore AI capabilities using Livepeer.',
+// 'Build on the Livepeer open network.',
+// 'Delegate LPT and engage as a token participant.',
+// 'Access compute or set up a gateway.',
+// 'Monetise your GPU.',
+// 'Read or contribute deep research.',
+// 'Explore partnership opportunities.',
+// ]
+
+// export const tldrIcons = [
+// 'faUser',
+// 'faLightbulb',
+// 'faVideo',
+// 'faRobot',
+// 'faCode',
+// 'faCoins',
+// 'faNetworkWired',
+// 'faMicrochip',
+// 'faBookOpen',
+// 'faHandshake',
+// ]
+
+// export const tldrLinks = [
+// '../../01_about/about-home/',
+// '../../01_about/project-showcase/',
+// '../../03_developers/livepeer-real-time-video/',
+// '../../03_developers/ai-inference-on-livepeer/',
+// '../../03_developers/building-on-livepeer/',
+// '../../06_delegators/delegating-lpt/',
+// '../../04_gateways/',
+// '../../05_orchestrators/orchestrator-setup-add-a-gpu-to-livepeer/',
+// '../../07_resources/references/',
+// '', // TODO: Add link
+// ]
diff --git a/snippets/variables/orchestrators.mdx b/snippets/variables/orchestrators.mdx
new file mode 100644
index 00000000..e69de29b
diff --git a/snippets/variables/pages.mdx b/snippets/variables/pages.mdx
new file mode 100644
index 00000000..e69de29b
diff --git a/snippets/variables/resources.mdx b/snippets/variables/resources.mdx
new file mode 100644
index 00000000..e69de29b
diff --git a/style.css b/style.css
index 1859b45f..304bf36d 100644
--- a/style.css
+++ b/style.css
@@ -2,3 +2,137 @@
img[alt="light logo"] {
max-width: 180px;
} */
+
+/* V2 TEST */
+/* a.nav-tabs-item[href="/pages/07_resources/resources_hub.mdx"],
+a.nav-tabs-item[href="/pages/08_help/README"] {
+ color: rgba(255, 90, 90, 0.342) !important;
+} */
+
+/* Make the nav-tabs container full width */
+.nav-tabs {
+ width: 100%;
+ justify-content: flex-start;
+}
+
+.nav-tabs
+
+/* Make the nav-tabs container full width */
+.nav-tabs {
+ width: 100%;
+ justify-content: flex-start;
+}
+
+#navbar > div.z-10.mx-auto.relative > div.hidden.lg\:flex.px-12.h-12 > div {
+ column-gap: 2rem !important;
+}
+
+/* .gap-x-6 {
+ column-gap: 2rem !important;
+} */
+
+/* .nav-tabs h-full flex text-sm gap-x-6 {
+ column-gap: 2rem !important;
+} */
+
+/* Push Reference HUB to the right and style as outlined button */
+a.nav-tabs-item[href="/v2/pages/07_resources/resources_hub"] {
+ margin-left: auto;
+ background-color: transparent;
+ border: 1px solid #2b9a66 !important;
+ padding: 4px 8px;
+ border-radius: 4px;
+ font-size: 0.7rem;
+ height: auto !important;
+ align-self: center;
+ margin-right: -2rem;
+}
+
+/* Color the text */
+/* a.nav-tabs-item[href="/v2/pages/07_resources/resources_hub"] {
+ color: #2b9a66 !important;
+} */
+
+/* Shrink & color the icon */
+a.nav-tabs-item[href="/v2/pages/07_resources/resources_hub"] svg {
+ height: 0.75rem;
+ width: 0.75rem;
+ /* background-color: #2b9a66 !important; */
+}
+
+/* Hide the underline on the button */
+a.nav-tabs-item[href="/v2/pages/07_resources/resources_hub"] > div:last-child {
+ display: none;
+}
+
+/* Stack footer links vertically */
+#footer .flex-col .flex.gap-4 {
+ flex-direction: column !important;
+ gap: 0rem !important;
+}
+
+/* Reduce footer padding */
+#footer > div {
+ padding-top: 2rem !important;
+ padding-bottom: 1rem !important;
+}
+
+/* #footer > div > div:first-child {
+ display: flex;
+ flex-direction: row !important;
+ color: red !important;
+}
+
+#footer > div > div:first-child > div {
+ display: flex;
+ flex-direction: row !important;
+ color: green !important;
+} */
+
+/* Fix bad styling of cards with arrows */
+[data-component-part="card-content-container"] {
+ padding-right: 2.5rem; /* Creates space for the arrow */
+}
+
+.code-block > div > div > svg {
+ background-color: #18794e !important;
+}
+
+/* Error 404 Styling */
+#error-description > span > div > div {
+ border: 1px solid #18794e !important;
+}
+
+body
+ > div.relative.antialiased.text-gray-500.dark\:text-gray-400
+ > div.peer-\[\.is-not-custom\]\:lg\:flex.peer-\[\.is-custom\]\:\[\&\>div\:first-child\]\:\!hidden.peer-\[\.is-custom\]\:\[\&\>div\:first-child\]\:sm\:\!hidden.peer-\[\.is-custom\]\:\[\&\>div\:first-child\]\:md\:\!hidden.peer-\[\.is-custom\]\:\[\&\>div\:first-child\]\:lg\:\!hidden.peer-\[\.is-custom\]\:\[\&\>div\:first-child\]\:xl\:\!hidden
+ > div.flex.flex-col.items-center.justify-center.w-full.max-w-lg.overflow-x-hidden.mx-auto.py-48.px-5.text-center.\*\:text-center.gap-y-8.not-found-container
+ > div {
+ margin-top: -5rem;
+}
+
+#error-description
+ > span
+ > div
+ > div
+ > div.relative.rounded-xl.overflow-hidden.flex.justify-center
+ > img {
+ width: 500px;
+ aspect-ratio: 4 / 3;
+ object-fit: cover;
+ /* border: 1px solid #fff; */
+}
+
+/* Step List Color Icons Styling */
+/* #content > div.steps > div > div.absolute.ml-\[-13px\].py-2 > div {
+ background-color: #18794e !important;
+} */
+
+/* Step List Color Titles */
+#content
+ > div.steps.ml-3\.5.mt-10.mb-6
+ > div
+ > div.w-full.overflow-hidden.pl-8.pr-px
+ > p {
+ color: #2b9a66 !important;
+}
diff --git a/ai/api-reference/audio-to-text.mdx b/v1/ai/api-reference/audio-to-text.mdx
similarity index 100%
rename from ai/api-reference/audio-to-text.mdx
rename to v1/ai/api-reference/audio-to-text.mdx
diff --git a/ai/api-reference/gateway.openapi.yaml b/v1/ai/api-reference/gateway.openapi.yaml
similarity index 100%
rename from ai/api-reference/gateway.openapi.yaml
rename to v1/ai/api-reference/gateway.openapi.yaml
diff --git a/ai/api-reference/image-to-image.mdx b/v1/ai/api-reference/image-to-image.mdx
similarity index 100%
rename from ai/api-reference/image-to-image.mdx
rename to v1/ai/api-reference/image-to-image.mdx
diff --git a/ai/api-reference/image-to-text.mdx b/v1/ai/api-reference/image-to-text.mdx
similarity index 100%
rename from ai/api-reference/image-to-text.mdx
rename to v1/ai/api-reference/image-to-text.mdx
diff --git a/ai/api-reference/image-to-video.mdx b/v1/ai/api-reference/image-to-video.mdx
similarity index 100%
rename from ai/api-reference/image-to-video.mdx
rename to v1/ai/api-reference/image-to-video.mdx
diff --git a/ai/api-reference/llm.mdx b/v1/ai/api-reference/llm.mdx
similarity index 100%
rename from ai/api-reference/llm.mdx
rename to v1/ai/api-reference/llm.mdx
diff --git a/ai/api-reference/overview.mdx b/v1/ai/api-reference/overview.mdx
similarity index 100%
rename from ai/api-reference/overview.mdx
rename to v1/ai/api-reference/overview.mdx
diff --git a/ai/api-reference/segment-anything-2.mdx b/v1/ai/api-reference/segment-anything-2.mdx
similarity index 100%
rename from ai/api-reference/segment-anything-2.mdx
rename to v1/ai/api-reference/segment-anything-2.mdx
diff --git a/ai/api-reference/text-to-image.mdx b/v1/ai/api-reference/text-to-image.mdx
similarity index 100%
rename from ai/api-reference/text-to-image.mdx
rename to v1/ai/api-reference/text-to-image.mdx
diff --git a/ai/api-reference/text-to-speech.mdx b/v1/ai/api-reference/text-to-speech.mdx
similarity index 100%
rename from ai/api-reference/text-to-speech.mdx
rename to v1/ai/api-reference/text-to-speech.mdx
diff --git a/ai/api-reference/upscale.mdx b/v1/ai/api-reference/upscale.mdx
similarity index 100%
rename from ai/api-reference/upscale.mdx
rename to v1/ai/api-reference/upscale.mdx
diff --git a/ai/builders/gateways.mdx b/v1/ai/builders/gateways.mdx
similarity index 100%
rename from ai/builders/gateways.mdx
rename to v1/ai/builders/gateways.mdx
diff --git a/ai/builders/get-started.mdx b/v1/ai/builders/get-started.mdx
similarity index 100%
rename from ai/builders/get-started.mdx
rename to v1/ai/builders/get-started.mdx
diff --git a/ai/builders/showcase.mdx b/v1/ai/builders/showcase.mdx
similarity index 85%
rename from ai/builders/showcase.mdx
rename to v1/ai/builders/showcase.mdx
index bdbb132e..e390b591 100644
--- a/ai/builders/showcase.mdx
+++ b/v1/ai/builders/showcase.mdx
@@ -15,7 +15,7 @@ few that have agreed to be featured.
@@ -26,13 +26,13 @@ few that have agreed to be featured.
title="Dream (by livepeer.cloud)"
href="https://dream.livepeer.cloud/generate"
>
-
+
An open-source platform, built on **Stability-AI/StableStudio**, designed for
experimenting with all pipelines on the AI Subnet.
@@ -40,7 +40,7 @@ few that have agreed to be featured.
diff --git a/ai/contributors/coming-soon.mdx b/v1/ai/contributors/coming-soon.mdx
similarity index 100%
rename from ai/contributors/coming-soon.mdx
rename to v1/ai/contributors/coming-soon.mdx
diff --git a/ai/contributors/developers.mdx b/v1/ai/contributors/developers.mdx
similarity index 100%
rename from ai/contributors/developers.mdx
rename to v1/ai/contributors/developers.mdx
diff --git a/ai/contributors/get-started.mdx b/v1/ai/contributors/get-started.mdx
similarity index 100%
rename from ai/contributors/get-started.mdx
rename to v1/ai/contributors/get-started.mdx
diff --git a/ai/contributors/guides/add-model.mdx b/v1/ai/contributors/guides/add-model.mdx
similarity index 100%
rename from ai/contributors/guides/add-model.mdx
rename to v1/ai/contributors/guides/add-model.mdx
diff --git a/ai/contributors/guides/add-pipeline.mdx b/v1/ai/contributors/guides/add-pipeline.mdx
similarity index 100%
rename from ai/contributors/guides/add-pipeline.mdx
rename to v1/ai/contributors/guides/add-pipeline.mdx
diff --git a/ai/gateways/get-started.mdx b/v1/ai/gateways/get-started.mdx
similarity index 100%
rename from ai/gateways/get-started.mdx
rename to v1/ai/gateways/get-started.mdx
diff --git a/ai/gateways/onchain.mdx b/v1/ai/gateways/onchain.mdx
similarity index 100%
rename from ai/gateways/onchain.mdx
rename to v1/ai/gateways/onchain.mdx
diff --git a/ai/gateways/start-gateway.mdx b/v1/ai/gateways/start-gateway.mdx
similarity index 100%
rename from ai/gateways/start-gateway.mdx
rename to v1/ai/gateways/start-gateway.mdx
diff --git a/ai/introduction.mdx b/v1/ai/introduction.mdx
similarity index 100%
rename from ai/introduction.mdx
rename to v1/ai/introduction.mdx
diff --git a/ai/orchestrators/ai-worker.mdx b/v1/ai/orchestrators/ai-worker.mdx
similarity index 100%
rename from ai/orchestrators/ai-worker.mdx
rename to v1/ai/orchestrators/ai-worker.mdx
diff --git a/ai/orchestrators/benchmarking.mdx b/v1/ai/orchestrators/benchmarking.mdx
similarity index 100%
rename from ai/orchestrators/benchmarking.mdx
rename to v1/ai/orchestrators/benchmarking.mdx
diff --git a/ai/orchestrators/get-started.mdx b/v1/ai/orchestrators/get-started.mdx
similarity index 100%
rename from ai/orchestrators/get-started.mdx
rename to v1/ai/orchestrators/get-started.mdx
diff --git a/ai/orchestrators/models-config.mdx b/v1/ai/orchestrators/models-config.mdx
similarity index 100%
rename from ai/orchestrators/models-config.mdx
rename to v1/ai/orchestrators/models-config.mdx
diff --git a/ai/orchestrators/models-download.mdx b/v1/ai/orchestrators/models-download.mdx
similarity index 100%
rename from ai/orchestrators/models-download.mdx
rename to v1/ai/orchestrators/models-download.mdx
diff --git a/ai/orchestrators/onchain.mdx b/v1/ai/orchestrators/onchain.mdx
similarity index 97%
rename from ai/orchestrators/onchain.mdx
rename to v1/ai/orchestrators/onchain.mdx
index 3b7eb839..69258d3e 100644
--- a/ai/orchestrators/onchain.mdx
+++ b/v1/ai/orchestrators/onchain.mdx
@@ -124,7 +124,7 @@ contract on the [Arbitrum Mainnet](https://arbitrum.io).
Visit the [AIServiceRegistry](https://arbiscan.io/address/0x04C0b249740175999E5BF5c9ac1dA92431EF34C5) contract page on the Arbitrum Explorer and click on the `Contract` tab.
- 
+ 
On the contract page, click the `Write Contract` button and connect your wallet to the Arbitrum Explorer by clicking the `Connect to Web3` button. Then, select the wallet you imported in the first step.
@@ -134,7 +134,7 @@ contract on the [Arbitrum Mainnet](https://arbitrum.io).
be successfully set.
- 
+ 
To verify that the Service URI has been set correctly, click the `Read Contract` button on the contract page. Access the [getServiceURI](https://arbiscan.io/address/0x04C0b249740175999E5BF5c9ac1dA92431EF34C5#readContract#F2) function and input the address of your **Mainnet Transcoding Network Orchestrator** in the `_addr` field. Click the `Query` button to retrieve the Service URI set for your AI Orchestrator.
diff --git a/ai/orchestrators/start-orchestrator.mdx b/v1/ai/orchestrators/start-orchestrator.mdx
similarity index 100%
rename from ai/orchestrators/start-orchestrator.mdx
rename to v1/ai/orchestrators/start-orchestrator.mdx
diff --git a/ai/pipelines/audio-to-text.mdx b/v1/ai/pipelines/audio-to-text.mdx
similarity index 100%
rename from ai/pipelines/audio-to-text.mdx
rename to v1/ai/pipelines/audio-to-text.mdx
diff --git a/ai/pipelines/image-to-image.mdx b/v1/ai/pipelines/image-to-image.mdx
similarity index 100%
rename from ai/pipelines/image-to-image.mdx
rename to v1/ai/pipelines/image-to-image.mdx
diff --git a/ai/pipelines/image-to-text.mdx b/v1/ai/pipelines/image-to-text.mdx
similarity index 100%
rename from ai/pipelines/image-to-text.mdx
rename to v1/ai/pipelines/image-to-text.mdx
diff --git a/ai/pipelines/image-to-video.mdx b/v1/ai/pipelines/image-to-video.mdx
similarity index 100%
rename from ai/pipelines/image-to-video.mdx
rename to v1/ai/pipelines/image-to-video.mdx
diff --git a/ai/pipelines/llm.mdx b/v1/ai/pipelines/llm.mdx
similarity index 100%
rename from ai/pipelines/llm.mdx
rename to v1/ai/pipelines/llm.mdx
diff --git a/ai/pipelines/overview.mdx b/v1/ai/pipelines/overview.mdx
similarity index 100%
rename from ai/pipelines/overview.mdx
rename to v1/ai/pipelines/overview.mdx
diff --git a/ai/pipelines/segment-anything-2.mdx b/v1/ai/pipelines/segment-anything-2.mdx
similarity index 100%
rename from ai/pipelines/segment-anything-2.mdx
rename to v1/ai/pipelines/segment-anything-2.mdx
diff --git a/ai/pipelines/text-to-image.mdx b/v1/ai/pipelines/text-to-image.mdx
similarity index 100%
rename from ai/pipelines/text-to-image.mdx
rename to v1/ai/pipelines/text-to-image.mdx
diff --git a/ai/pipelines/text-to-speech.mdx b/v1/ai/pipelines/text-to-speech.mdx
similarity index 100%
rename from ai/pipelines/text-to-speech.mdx
rename to v1/ai/pipelines/text-to-speech.mdx
diff --git a/ai/pipelines/upscale.mdx b/v1/ai/pipelines/upscale.mdx
similarity index 100%
rename from ai/pipelines/upscale.mdx
rename to v1/ai/pipelines/upscale.mdx
diff --git a/ai/sdks/go.mdx b/v1/ai/sdks/go.mdx
similarity index 100%
rename from ai/sdks/go.mdx
rename to v1/ai/sdks/go.mdx
diff --git a/ai/sdks/javascript.mdx b/v1/ai/sdks/javascript.mdx
similarity index 100%
rename from ai/sdks/javascript.mdx
rename to v1/ai/sdks/javascript.mdx
diff --git a/ai/sdks/overview.mdx b/v1/ai/sdks/overview.mdx
similarity index 100%
rename from ai/sdks/overview.mdx
rename to v1/ai/sdks/overview.mdx
diff --git a/ai/sdks/python.mdx b/v1/ai/sdks/python.mdx
similarity index 100%
rename from ai/sdks/python.mdx
rename to v1/ai/sdks/python.mdx
diff --git a/ai/whats-new.mdx b/v1/ai/whats-new.mdx
similarity index 100%
rename from ai/whats-new.mdx
rename to v1/ai/whats-new.mdx
diff --git a/api-reference/asset/delete.mdx b/v1/api-reference/asset/delete.mdx
similarity index 100%
rename from api-reference/asset/delete.mdx
rename to v1/api-reference/asset/delete.mdx
diff --git a/api-reference/asset/get-all.mdx b/v1/api-reference/asset/get-all.mdx
similarity index 100%
rename from api-reference/asset/get-all.mdx
rename to v1/api-reference/asset/get-all.mdx
diff --git a/api-reference/asset/get.mdx b/v1/api-reference/asset/get.mdx
similarity index 100%
rename from api-reference/asset/get.mdx
rename to v1/api-reference/asset/get.mdx
diff --git a/api-reference/asset/overview.mdx b/v1/api-reference/asset/overview.mdx
similarity index 100%
rename from api-reference/asset/overview.mdx
rename to v1/api-reference/asset/overview.mdx
diff --git a/api-reference/asset/update.mdx b/v1/api-reference/asset/update.mdx
similarity index 100%
rename from api-reference/asset/update.mdx
rename to v1/api-reference/asset/update.mdx
diff --git a/api-reference/asset/upload-via-url.mdx b/v1/api-reference/asset/upload-via-url.mdx
similarity index 100%
rename from api-reference/asset/upload-via-url.mdx
rename to v1/api-reference/asset/upload-via-url.mdx
diff --git a/api-reference/asset/upload.mdx b/v1/api-reference/asset/upload.mdx
similarity index 100%
rename from api-reference/asset/upload.mdx
rename to v1/api-reference/asset/upload.mdx
diff --git a/api-reference/generate/audio-to-text.mdx b/v1/api-reference/generate/audio-to-text.mdx
similarity index 100%
rename from api-reference/generate/audio-to-text.mdx
rename to v1/api-reference/generate/audio-to-text.mdx
diff --git a/api-reference/generate/image-to-image.mdx b/v1/api-reference/generate/image-to-image.mdx
similarity index 100%
rename from api-reference/generate/image-to-image.mdx
rename to v1/api-reference/generate/image-to-image.mdx
diff --git a/api-reference/generate/image-to-text.mdx b/v1/api-reference/generate/image-to-text.mdx
similarity index 100%
rename from api-reference/generate/image-to-text.mdx
rename to v1/api-reference/generate/image-to-text.mdx
diff --git a/api-reference/generate/image-to-video.mdx b/v1/api-reference/generate/image-to-video.mdx
similarity index 100%
rename from api-reference/generate/image-to-video.mdx
rename to v1/api-reference/generate/image-to-video.mdx
diff --git a/api-reference/generate/llm.mdx b/v1/api-reference/generate/llm.mdx
similarity index 100%
rename from api-reference/generate/llm.mdx
rename to v1/api-reference/generate/llm.mdx
diff --git a/api-reference/generate/overview.mdx b/v1/api-reference/generate/overview.mdx
similarity index 100%
rename from api-reference/generate/overview.mdx
rename to v1/api-reference/generate/overview.mdx
diff --git a/api-reference/generate/segment-anything-2.mdx b/v1/api-reference/generate/segment-anything-2.mdx
similarity index 100%
rename from api-reference/generate/segment-anything-2.mdx
rename to v1/api-reference/generate/segment-anything-2.mdx
diff --git a/api-reference/generate/text-to-image.mdx b/v1/api-reference/generate/text-to-image.mdx
similarity index 100%
rename from api-reference/generate/text-to-image.mdx
rename to v1/api-reference/generate/text-to-image.mdx
diff --git a/api-reference/generate/text-to-speech.mdx b/v1/api-reference/generate/text-to-speech.mdx
similarity index 100%
rename from api-reference/generate/text-to-speech.mdx
rename to v1/api-reference/generate/text-to-speech.mdx
diff --git a/api-reference/generate/upscale.mdx b/v1/api-reference/generate/upscale.mdx
similarity index 100%
rename from api-reference/generate/upscale.mdx
rename to v1/api-reference/generate/upscale.mdx
diff --git a/api-reference/multistream/create.mdx b/v1/api-reference/multistream/create.mdx
similarity index 100%
rename from api-reference/multistream/create.mdx
rename to v1/api-reference/multistream/create.mdx
diff --git a/api-reference/multistream/delete.mdx b/v1/api-reference/multistream/delete.mdx
similarity index 100%
rename from api-reference/multistream/delete.mdx
rename to v1/api-reference/multistream/delete.mdx
diff --git a/api-reference/multistream/get-all.mdx b/v1/api-reference/multistream/get-all.mdx
similarity index 100%
rename from api-reference/multistream/get-all.mdx
rename to v1/api-reference/multistream/get-all.mdx
diff --git a/api-reference/multistream/get.mdx b/v1/api-reference/multistream/get.mdx
similarity index 100%
rename from api-reference/multistream/get.mdx
rename to v1/api-reference/multistream/get.mdx
diff --git a/api-reference/multistream/overview.mdx b/v1/api-reference/multistream/overview.mdx
similarity index 100%
rename from api-reference/multistream/overview.mdx
rename to v1/api-reference/multistream/overview.mdx
diff --git a/api-reference/multistream/update.mdx b/v1/api-reference/multistream/update.mdx
similarity index 100%
rename from api-reference/multistream/update.mdx
rename to v1/api-reference/multistream/update.mdx
diff --git a/api-reference/overview/authentication.mdx b/v1/api-reference/overview/authentication.mdx
similarity index 96%
rename from api-reference/overview/authentication.mdx
rename to v1/api-reference/overview/authentication.mdx
index 6a7d7c52..4ad8f0e5 100644
--- a/api-reference/overview/authentication.mdx
+++ b/v1/api-reference/overview/authentication.mdx
@@ -45,4 +45,4 @@ CORS API key, they can modify the stream or view the stream key. If a viewer had
access to the stream ID + CORS API key, they could hijack the stream. **A
`playbackId` should be exposed to the viewer only.**
-
+
diff --git a/api-reference/overview/introduction.mdx b/v1/api-reference/overview/introduction.mdx
similarity index 100%
rename from api-reference/overview/introduction.mdx
rename to v1/api-reference/overview/introduction.mdx
diff --git a/api-reference/playback/get.mdx b/v1/api-reference/playback/get.mdx
similarity index 100%
rename from api-reference/playback/get.mdx
rename to v1/api-reference/playback/get.mdx
diff --git a/api-reference/playback/overview.mdx b/v1/api-reference/playback/overview.mdx
similarity index 100%
rename from api-reference/playback/overview.mdx
rename to v1/api-reference/playback/overview.mdx
diff --git a/api-reference/room/create-user.mdx b/v1/api-reference/room/create-user.mdx
similarity index 100%
rename from api-reference/room/create-user.mdx
rename to v1/api-reference/room/create-user.mdx
diff --git a/api-reference/room/create.mdx b/v1/api-reference/room/create.mdx
similarity index 100%
rename from api-reference/room/create.mdx
rename to v1/api-reference/room/create.mdx
diff --git a/api-reference/room/delete.mdx b/v1/api-reference/room/delete.mdx
similarity index 100%
rename from api-reference/room/delete.mdx
rename to v1/api-reference/room/delete.mdx
diff --git a/api-reference/room/get-user.mdx b/v1/api-reference/room/get-user.mdx
similarity index 100%
rename from api-reference/room/get-user.mdx
rename to v1/api-reference/room/get-user.mdx
diff --git a/api-reference/room/get.mdx b/v1/api-reference/room/get.mdx
similarity index 100%
rename from api-reference/room/get.mdx
rename to v1/api-reference/room/get.mdx
diff --git a/api-reference/room/remove-user.mdx b/v1/api-reference/room/remove-user.mdx
similarity index 100%
rename from api-reference/room/remove-user.mdx
rename to v1/api-reference/room/remove-user.mdx
diff --git a/api-reference/room/start-egress.mdx b/v1/api-reference/room/start-egress.mdx
similarity index 100%
rename from api-reference/room/start-egress.mdx
rename to v1/api-reference/room/start-egress.mdx
diff --git a/api-reference/room/stop-egress.mdx b/v1/api-reference/room/stop-egress.mdx
similarity index 100%
rename from api-reference/room/stop-egress.mdx
rename to v1/api-reference/room/stop-egress.mdx
diff --git a/api-reference/room/update-user.mdx b/v1/api-reference/room/update-user.mdx
similarity index 100%
rename from api-reference/room/update-user.mdx
rename to v1/api-reference/room/update-user.mdx
diff --git a/api-reference/room/update.mdx b/v1/api-reference/room/update.mdx
similarity index 100%
rename from api-reference/room/update.mdx
rename to v1/api-reference/room/update.mdx
diff --git a/api-reference/session/get-all.mdx b/v1/api-reference/session/get-all.mdx
similarity index 100%
rename from api-reference/session/get-all.mdx
rename to v1/api-reference/session/get-all.mdx
diff --git a/api-reference/session/get-clip.mdx b/v1/api-reference/session/get-clip.mdx
similarity index 100%
rename from api-reference/session/get-clip.mdx
rename to v1/api-reference/session/get-clip.mdx
diff --git a/api-reference/session/get-recording.mdx b/v1/api-reference/session/get-recording.mdx
similarity index 100%
rename from api-reference/session/get-recording.mdx
rename to v1/api-reference/session/get-recording.mdx
diff --git a/api-reference/session/get.mdx b/v1/api-reference/session/get.mdx
similarity index 100%
rename from api-reference/session/get.mdx
rename to v1/api-reference/session/get.mdx
diff --git a/api-reference/session/overview.mdx b/v1/api-reference/session/overview.mdx
similarity index 100%
rename from api-reference/session/overview.mdx
rename to v1/api-reference/session/overview.mdx
diff --git a/api-reference/signing-key/create.mdx b/v1/api-reference/signing-key/create.mdx
similarity index 100%
rename from api-reference/signing-key/create.mdx
rename to v1/api-reference/signing-key/create.mdx
diff --git a/api-reference/signing-key/delete.mdx b/v1/api-reference/signing-key/delete.mdx
similarity index 100%
rename from api-reference/signing-key/delete.mdx
rename to v1/api-reference/signing-key/delete.mdx
diff --git a/api-reference/signing-key/get-all.mdx b/v1/api-reference/signing-key/get-all.mdx
similarity index 100%
rename from api-reference/signing-key/get-all.mdx
rename to v1/api-reference/signing-key/get-all.mdx
diff --git a/api-reference/signing-key/get.mdx b/v1/api-reference/signing-key/get.mdx
similarity index 100%
rename from api-reference/signing-key/get.mdx
rename to v1/api-reference/signing-key/get.mdx
diff --git a/api-reference/signing-key/overview.mdx b/v1/api-reference/signing-key/overview.mdx
similarity index 100%
rename from api-reference/signing-key/overview.mdx
rename to v1/api-reference/signing-key/overview.mdx
diff --git a/api-reference/signing-key/update.mdx b/v1/api-reference/signing-key/update.mdx
similarity index 100%
rename from api-reference/signing-key/update.mdx
rename to v1/api-reference/signing-key/update.mdx
diff --git a/api-reference/stream/add-multistream-target.mdx b/v1/api-reference/stream/add-multistream-target.mdx
similarity index 100%
rename from api-reference/stream/add-multistream-target.mdx
rename to v1/api-reference/stream/add-multistream-target.mdx
diff --git a/api-reference/stream/create-clip.mdx b/v1/api-reference/stream/create-clip.mdx
similarity index 100%
rename from api-reference/stream/create-clip.mdx
rename to v1/api-reference/stream/create-clip.mdx
diff --git a/api-reference/stream/create.mdx b/v1/api-reference/stream/create.mdx
similarity index 100%
rename from api-reference/stream/create.mdx
rename to v1/api-reference/stream/create.mdx
diff --git a/api-reference/stream/delete-multistream-target.mdx b/v1/api-reference/stream/delete-multistream-target.mdx
similarity index 100%
rename from api-reference/stream/delete-multistream-target.mdx
rename to v1/api-reference/stream/delete-multistream-target.mdx
diff --git a/api-reference/stream/delete.mdx b/v1/api-reference/stream/delete.mdx
similarity index 100%
rename from api-reference/stream/delete.mdx
rename to v1/api-reference/stream/delete.mdx
diff --git a/api-reference/stream/get-all.mdx b/v1/api-reference/stream/get-all.mdx
similarity index 100%
rename from api-reference/stream/get-all.mdx
rename to v1/api-reference/stream/get-all.mdx
diff --git a/api-reference/stream/get-clip.mdx b/v1/api-reference/stream/get-clip.mdx
similarity index 100%
rename from api-reference/stream/get-clip.mdx
rename to v1/api-reference/stream/get-clip.mdx
diff --git a/api-reference/stream/get.mdx b/v1/api-reference/stream/get.mdx
similarity index 100%
rename from api-reference/stream/get.mdx
rename to v1/api-reference/stream/get.mdx
diff --git a/api-reference/stream/overview.mdx b/v1/api-reference/stream/overview.mdx
similarity index 100%
rename from api-reference/stream/overview.mdx
rename to v1/api-reference/stream/overview.mdx
diff --git a/api-reference/stream/terminate.mdx b/v1/api-reference/stream/terminate.mdx
similarity index 100%
rename from api-reference/stream/terminate.mdx
rename to v1/api-reference/stream/terminate.mdx
diff --git a/api-reference/stream/update.mdx b/v1/api-reference/stream/update.mdx
similarity index 100%
rename from api-reference/stream/update.mdx
rename to v1/api-reference/stream/update.mdx
diff --git a/api-reference/task/get-all.mdx b/v1/api-reference/task/get-all.mdx
similarity index 100%
rename from api-reference/task/get-all.mdx
rename to v1/api-reference/task/get-all.mdx
diff --git a/api-reference/task/get.mdx b/v1/api-reference/task/get.mdx
similarity index 100%
rename from api-reference/task/get.mdx
rename to v1/api-reference/task/get.mdx
diff --git a/api-reference/task/overview.mdx b/v1/api-reference/task/overview.mdx
similarity index 100%
rename from api-reference/task/overview.mdx
rename to v1/api-reference/task/overview.mdx
diff --git a/api-reference/transcode/create.mdx b/v1/api-reference/transcode/create.mdx
similarity index 100%
rename from api-reference/transcode/create.mdx
rename to v1/api-reference/transcode/create.mdx
diff --git a/api-reference/transcode/overview.mdx b/v1/api-reference/transcode/overview.mdx
similarity index 100%
rename from api-reference/transcode/overview.mdx
rename to v1/api-reference/transcode/overview.mdx
diff --git a/api-reference/viewership/get-creators-metrics.mdx b/v1/api-reference/viewership/get-creators-metrics.mdx
similarity index 100%
rename from api-reference/viewership/get-creators-metrics.mdx
rename to v1/api-reference/viewership/get-creators-metrics.mdx
diff --git a/api-reference/viewership/get-public-total-views.mdx b/v1/api-reference/viewership/get-public-total-views.mdx
similarity index 100%
rename from api-reference/viewership/get-public-total-views.mdx
rename to v1/api-reference/viewership/get-public-total-views.mdx
diff --git a/api-reference/viewership/get-realtime-viewership.mdx b/v1/api-reference/viewership/get-realtime-viewership.mdx
similarity index 100%
rename from api-reference/viewership/get-realtime-viewership.mdx
rename to v1/api-reference/viewership/get-realtime-viewership.mdx
diff --git a/api-reference/viewership/get-usage-metrics.mdx b/v1/api-reference/viewership/get-usage-metrics.mdx
similarity index 100%
rename from api-reference/viewership/get-usage-metrics.mdx
rename to v1/api-reference/viewership/get-usage-metrics.mdx
diff --git a/api-reference/viewership/get-viewership-metrics.mdx b/v1/api-reference/viewership/get-viewership-metrics.mdx
similarity index 100%
rename from api-reference/viewership/get-viewership-metrics.mdx
rename to v1/api-reference/viewership/get-viewership-metrics.mdx
diff --git a/api-reference/webhook/create.mdx b/v1/api-reference/webhook/create.mdx
similarity index 100%
rename from api-reference/webhook/create.mdx
rename to v1/api-reference/webhook/create.mdx
diff --git a/api-reference/webhook/delete.mdx b/v1/api-reference/webhook/delete.mdx
similarity index 100%
rename from api-reference/webhook/delete.mdx
rename to v1/api-reference/webhook/delete.mdx
diff --git a/api-reference/webhook/get-all.mdx b/v1/api-reference/webhook/get-all.mdx
similarity index 100%
rename from api-reference/webhook/get-all.mdx
rename to v1/api-reference/webhook/get-all.mdx
diff --git a/api-reference/webhook/get.mdx b/v1/api-reference/webhook/get.mdx
similarity index 100%
rename from api-reference/webhook/get.mdx
rename to v1/api-reference/webhook/get.mdx
diff --git a/api-reference/webhook/overview.mdx b/v1/api-reference/webhook/overview.mdx
similarity index 100%
rename from api-reference/webhook/overview.mdx
rename to v1/api-reference/webhook/overview.mdx
diff --git a/api-reference/webhook/update.mdx b/v1/api-reference/webhook/update.mdx
similarity index 100%
rename from api-reference/webhook/update.mdx
rename to v1/api-reference/webhook/update.mdx
diff --git a/delegators/guides/bridge-lpt-to-arbitrum.mdx b/v1/delegators/guides/bridge-lpt-to-arbitrum.mdx
similarity index 98%
rename from delegators/guides/bridge-lpt-to-arbitrum.mdx
rename to v1/delegators/guides/bridge-lpt-to-arbitrum.mdx
index 2ecfb4c5..c142ed10 100644
--- a/delegators/guides/bridge-lpt-to-arbitrum.mdx
+++ b/v1/delegators/guides/bridge-lpt-to-arbitrum.mdx
@@ -84,7 +84,7 @@ will not reach your L2 wallet after an hour. Arbitrum
[provides a page](https://retryable-tx-panel.arbitrum.io/) to check on the
status of your L1 deposit transaction:
-
+
In the event of a failure of LPT to bridge due to gas spikes, you should see a
message similar to the following:
diff --git a/delegators/guides/migrate-stake-to-arbitrum.mdx b/v1/delegators/guides/migrate-stake-to-arbitrum.mdx
similarity index 94%
rename from delegators/guides/migrate-stake-to-arbitrum.mdx
rename to v1/delegators/guides/migrate-stake-to-arbitrum.mdx
index ee83dc04..575bba12 100644
--- a/delegators/guides/migrate-stake-to-arbitrum.mdx
+++ b/v1/delegators/guides/migrate-stake-to-arbitrum.mdx
@@ -38,7 +38,7 @@ will use Arbitrum in lieu of Ethereum Mainnet for all protocol actions.
@@ -48,7 +48,7 @@ will use Arbitrum in lieu of Ethereum Mainnet for all protocol actions.
@@ -61,7 +61,7 @@ will use Arbitrum in lieu of Ethereum Mainnet for all protocol actions.
diff --git a/delegators/guides/yield-calculation.mdx b/v1/delegators/guides/yield-calculation.mdx
similarity index 100%
rename from delegators/guides/yield-calculation.mdx
rename to v1/delegators/guides/yield-calculation.mdx
diff --git a/developers/introduction.mdx b/v1/delegators/introduction.mdx
similarity index 100%
rename from developers/introduction.mdx
rename to v1/delegators/introduction.mdx
diff --git a/developers/livepeer-studio-cli.mdx b/v1/delegators/livepeer-studio-cli.mdx
similarity index 100%
rename from developers/livepeer-studio-cli.mdx
rename to v1/delegators/livepeer-studio-cli.mdx
diff --git a/developers/quick-start.mdx b/v1/delegators/quick-start.mdx
similarity index 98%
rename from developers/quick-start.mdx
rename to v1/delegators/quick-start.mdx
index e87293e7..a1b7aa3d 100644
--- a/developers/quick-start.mdx
+++ b/v1/delegators/quick-start.mdx
@@ -19,7 +19,7 @@ an API key by clicking on the "Create API Key" button on Developers page.
+ page](/v1/images/tutorials/studio-create-api.png)
You can now use this API key in Livepeer SDKs and APIs in order to authenticate
diff --git a/developers/core-concepts/core-api/access-control.mdx b/v1/developers/core-concepts/core-api/access-control.mdx
similarity index 100%
rename from developers/core-concepts/core-api/access-control.mdx
rename to v1/developers/core-concepts/core-api/access-control.mdx
diff --git a/developers/core-concepts/core-api/asset.mdx b/v1/developers/core-concepts/core-api/asset.mdx
similarity index 100%
rename from developers/core-concepts/core-api/asset.mdx
rename to v1/developers/core-concepts/core-api/asset.mdx
diff --git a/developers/core-concepts/core-api/multistream.mdx b/v1/developers/core-concepts/core-api/multistream.mdx
similarity index 100%
rename from developers/core-concepts/core-api/multistream.mdx
rename to v1/developers/core-concepts/core-api/multistream.mdx
diff --git a/developers/core-concepts/core-api/stream.mdx b/v1/developers/core-concepts/core-api/stream.mdx
similarity index 100%
rename from developers/core-concepts/core-api/stream.mdx
rename to v1/developers/core-concepts/core-api/stream.mdx
diff --git a/developers/core-concepts/livepeer-network/delegators.mdx b/v1/developers/core-concepts/livepeer-network/delegators.mdx
similarity index 100%
rename from developers/core-concepts/livepeer-network/delegators.mdx
rename to v1/developers/core-concepts/livepeer-network/delegators.mdx
diff --git a/developers/core-concepts/livepeer-network/gateways.mdx b/v1/developers/core-concepts/livepeer-network/gateways.mdx
similarity index 100%
rename from developers/core-concepts/livepeer-network/gateways.mdx
rename to v1/developers/core-concepts/livepeer-network/gateways.mdx
diff --git a/developers/core-concepts/livepeer-network/orchestrators.mdx b/v1/developers/core-concepts/livepeer-network/orchestrators.mdx
similarity index 97%
rename from developers/core-concepts/livepeer-network/orchestrators.mdx
rename to v1/developers/core-concepts/livepeer-network/orchestrators.mdx
index 25eb1a17..b782cbfd 100644
--- a/developers/core-concepts/livepeer-network/orchestrators.mdx
+++ b/v1/developers/core-concepts/livepeer-network/orchestrators.mdx
@@ -10,7 +10,7 @@ join the Livepeer network as Orchestrators.
Livepeer network.
-
+
#### Micropayments
diff --git a/developers/core-concepts/player/overview.mdx b/v1/developers/core-concepts/player/overview.mdx
similarity index 100%
rename from developers/core-concepts/player/overview.mdx
rename to v1/developers/core-concepts/player/overview.mdx
diff --git a/developers/core-concepts/studio/in-browser-broadcast.mdx b/v1/developers/core-concepts/studio/in-browser-broadcast.mdx
similarity index 95%
rename from developers/core-concepts/studio/in-browser-broadcast.mdx
rename to v1/developers/core-concepts/studio/in-browser-broadcast.mdx
index 0d700963..563ddb8c 100644
--- a/developers/core-concepts/studio/in-browser-broadcast.mdx
+++ b/v1/developers/core-concepts/studio/in-browser-broadcast.mdx
@@ -4,7 +4,7 @@ by Livepeer's low latency WebRTC technology. This method eliminates the need for
specialized broadcasting equipment or external software such as OBS, allowing
content creators to engage with their viewers effortlessly.
-
+
1. **Initialization:**
diff --git a/developers/core-concepts/studio/stream-health.mdx b/v1/developers/core-concepts/studio/stream-health.mdx
similarity index 97%
rename from developers/core-concepts/studio/stream-health.mdx
rename to v1/developers/core-concepts/studio/stream-health.mdx
index 76c29328..39a31701 100644
--- a/developers/core-concepts/studio/stream-health.mdx
+++ b/v1/developers/core-concepts/studio/stream-health.mdx
@@ -1,7 +1,7 @@
Stream Health is a multi-faceted indicator representing the operational and
performance status of a video stream within Livepeer.
-
+
1. **Global Health Status** is a holistic status of the stream. It can be one of
the following:
diff --git a/developers/core-concepts/studio/webhooks.mdx b/v1/developers/core-concepts/studio/webhooks.mdx
similarity index 98%
rename from developers/core-concepts/studio/webhooks.mdx
rename to v1/developers/core-concepts/studio/webhooks.mdx
index 0aef3a09..5468774f 100644
--- a/developers/core-concepts/studio/webhooks.mdx
+++ b/v1/developers/core-concepts/studio/webhooks.mdx
@@ -13,7 +13,7 @@ information or notifications to the application endpoint.
Webhooks can be created in Studio under the Developer/Webhooks page:
-
+
### Types of Events
diff --git a/developers/guides/access-control-jwt.mdx b/v1/developers/guides/access-control-jwt.mdx
similarity index 100%
rename from developers/guides/access-control-jwt.mdx
rename to v1/developers/guides/access-control-jwt.mdx
diff --git a/developers/guides/access-control-webhooks.mdx b/v1/developers/guides/access-control-webhooks.mdx
similarity index 100%
rename from developers/guides/access-control-webhooks.mdx
rename to v1/developers/guides/access-control-webhooks.mdx
diff --git a/developers/guides/clip-a-livestream.mdx b/v1/developers/guides/clip-a-livestream.mdx
similarity index 100%
rename from developers/guides/clip-a-livestream.mdx
rename to v1/developers/guides/clip-a-livestream.mdx
diff --git a/developers/guides/create-livestream.mdx b/v1/developers/guides/create-livestream.mdx
similarity index 100%
rename from developers/guides/create-livestream.mdx
rename to v1/developers/guides/create-livestream.mdx
diff --git a/developers/guides/encrypted-asset.mdx b/v1/developers/guides/encrypted-asset.mdx
similarity index 100%
rename from developers/guides/encrypted-asset.mdx
rename to v1/developers/guides/encrypted-asset.mdx
diff --git a/developers/guides/get-engagement-analytics-via-api.mdx b/v1/developers/guides/get-engagement-analytics-via-api.mdx
similarity index 98%
rename from developers/guides/get-engagement-analytics-via-api.mdx
rename to v1/developers/guides/get-engagement-analytics-via-api.mdx
index 4395b073..a9b8297d 100644
--- a/developers/guides/get-engagement-analytics-via-api.mdx
+++ b/v1/developers/guides/get-engagement-analytics-via-api.mdx
@@ -179,7 +179,7 @@ the dashboard to retrieve viewership metrics.
### Navigate to the assets page
-
+
### Click on an existing asset
@@ -187,12 +187,12 @@ Click on an existing asset and you'll be brought to that asset's specific
details page. If you haven't created an asset yet, you can follow the
[upload a video asset guide](/developers/guides/upload-video-asset).
-
+
### View your asset's viewership metrics
In the asset's specific detail page you can view its total number of views.
-
+
## Retrieving views from the API
### Get the `playbackId` of an existing stream/asset
diff --git a/developers/guides/get-engagement-analytics-via-grafana.mdx b/v1/developers/guides/get-engagement-analytics-via-grafana.mdx
similarity index 95%
rename from developers/guides/get-engagement-analytics-via-grafana.mdx
rename to v1/developers/guides/get-engagement-analytics-via-grafana.mdx
index 985527c4..a1176388 100644
--- a/developers/guides/get-engagement-analytics-via-grafana.mdx
+++ b/v1/developers/guides/get-engagement-analytics-via-grafana.mdx
@@ -36,7 +36,7 @@ With that we are ready to set up our dashboard!
@@ -58,7 +58,7 @@ With that we are ready to set up our dashboard!
diff --git a/developers/guides/get-engagement-analytics-via-timeplus.mdx b/v1/developers/guides/get-engagement-analytics-via-timeplus.mdx
similarity index 97%
rename from developers/guides/get-engagement-analytics-via-timeplus.mdx
rename to v1/developers/guides/get-engagement-analytics-via-timeplus.mdx
index 3957b9b2..eeee8a78 100644
--- a/developers/guides/get-engagement-analytics-via-timeplus.mdx
+++ b/v1/developers/guides/get-engagement-analytics-via-timeplus.mdx
@@ -41,7 +41,7 @@ to:
combining diverse data sources.
-
+
# How to get started using Timeplus with Livepeer's Engagement Data
@@ -101,7 +101,7 @@ deployed to Timeplus:
diff --git a/developers/guides/listen-to-asset-events.mdx b/v1/developers/guides/listen-to-asset-events.mdx
similarity index 97%
rename from developers/guides/listen-to-asset-events.mdx
rename to v1/developers/guides/listen-to-asset-events.mdx
index 72defe6f..101b4d03 100644
--- a/developers/guides/listen-to-asset-events.mdx
+++ b/v1/developers/guides/listen-to-asset-events.mdx
@@ -33,7 +33,7 @@ Log in to the [Livepeer Studio](https://livepeer.studio/) and navigate to the
[Developers/Webhooks](https://livepeer.studio/dashboard/developers/webhooks)
page.
-
+
Click the "Create Webhook" button and enter the URL of the webhook endpoint. Select any
asset event (with an `asset` prefix) and click "Create Webhook".
diff --git a/developers/guides/listen-to-stream-events.mdx b/v1/developers/guides/listen-to-stream-events.mdx
similarity index 98%
rename from developers/guides/listen-to-stream-events.mdx
rename to v1/developers/guides/listen-to-stream-events.mdx
index 80007d16..2218bd88 100644
--- a/developers/guides/listen-to-stream-events.mdx
+++ b/v1/developers/guides/listen-to-stream-events.mdx
@@ -36,7 +36,7 @@ Log in to the [Livepeer Studio](https://livepeer.studio/) and navigate to the
[Developers/Webhooks](https://livepeer.studio/dashboard/developers/webhooks)
page.
-
+
Click the "Create Webhook" button and enter URL of webhook endpoint. Select any
stream event (with stream/multistream prefix) to receive notifications for and
diff --git a/developers/guides/livestream-from-browser.mdx b/v1/developers/guides/livestream-from-browser.mdx
similarity index 100%
rename from developers/guides/livestream-from-browser.mdx
rename to v1/developers/guides/livestream-from-browser.mdx
diff --git a/developers/guides/managing-projects.mdx b/v1/developers/guides/managing-projects.mdx
similarity index 98%
rename from developers/guides/managing-projects.mdx
rename to v1/developers/guides/managing-projects.mdx
index 88fe781e..1da18a78 100644
--- a/developers/guides/managing-projects.mdx
+++ b/v1/developers/guides/managing-projects.mdx
@@ -4,7 +4,7 @@ description:
"Explore best practices for managing multiple environments in Livepeer Studio"
---
-
+
## Overview
diff --git a/developers/guides/monitor-stream-health.mdx b/v1/developers/guides/monitor-stream-health.mdx
similarity index 100%
rename from developers/guides/monitor-stream-health.mdx
rename to v1/developers/guides/monitor-stream-health.mdx
diff --git a/developers/guides/multistream.mdx b/v1/developers/guides/multistream.mdx
similarity index 100%
rename from developers/guides/multistream.mdx
rename to v1/developers/guides/multistream.mdx
diff --git a/developers/guides/optimize-latency-of-a-livestream.mdx b/v1/developers/guides/optimize-latency-of-a-livestream.mdx
similarity index 100%
rename from developers/guides/optimize-latency-of-a-livestream.mdx
rename to v1/developers/guides/optimize-latency-of-a-livestream.mdx
diff --git a/developers/guides/overview.mdx b/v1/developers/guides/overview.mdx
similarity index 100%
rename from developers/guides/overview.mdx
rename to v1/developers/guides/overview.mdx
diff --git a/developers/guides/playback-a-livestream.mdx b/v1/developers/guides/playback-a-livestream.mdx
similarity index 100%
rename from developers/guides/playback-a-livestream.mdx
rename to v1/developers/guides/playback-a-livestream.mdx
diff --git a/developers/guides/playback-an-asset.mdx b/v1/developers/guides/playback-an-asset.mdx
similarity index 100%
rename from developers/guides/playback-an-asset.mdx
rename to v1/developers/guides/playback-an-asset.mdx
diff --git a/developers/guides/setup-and-listen-to-webhooks.mdx b/v1/developers/guides/setup-and-listen-to-webhooks.mdx
similarity index 99%
rename from developers/guides/setup-and-listen-to-webhooks.mdx
rename to v1/developers/guides/setup-and-listen-to-webhooks.mdx
index 1e997335..0bde68ea 100644
--- a/developers/guides/setup-and-listen-to-webhooks.mdx
+++ b/v1/developers/guides/setup-and-listen-to-webhooks.mdx
@@ -102,7 +102,7 @@ Log in to [Livepeer Studio](https://livepeer.studio/) and navigate to the
[Developers/Webhooks](https://livepeer.studio/dashboard/developers/webhooks)
page.
-
+
Click the Create Webhook button and enter your Ngrok URL as the webhook
endpoint. Select the an event to receive notifications for and click Create
diff --git a/developers/guides/stream-via-obs.mdx b/v1/developers/guides/stream-via-obs.mdx
similarity index 96%
rename from developers/guides/stream-via-obs.mdx
rename to v1/developers/guides/stream-via-obs.mdx
index 9b451135..1573adea 100644
--- a/developers/guides/stream-via-obs.mdx
+++ b/v1/developers/guides/stream-via-obs.mdx
@@ -28,11 +28,11 @@ The creator will then need to:
browser window, select **Window Capture**.
2. Give the device a name:
-
+
-
+
-
+
## Update stream settings
@@ -43,7 +43,7 @@ The creator will then need to:
ignore the streaming service recommendations. If you choose to do this,
please see the [low latency](#configuring-obs-for-low-latency) section below.
-
+
## Stream and play back
@@ -54,7 +54,7 @@ settings above). Any player will now be able to
[play back the livestream](/developers/guides/playback-a-livestream) with the
playback ID.
-
+
## Configuring OBS for Low Latency
diff --git a/developers/guides/thumbnails-live.mdx b/v1/developers/guides/thumbnails-live.mdx
similarity index 100%
rename from developers/guides/thumbnails-live.mdx
rename to v1/developers/guides/thumbnails-live.mdx
diff --git a/developers/guides/thumbnails-vod.mdx b/v1/developers/guides/thumbnails-vod.mdx
similarity index 100%
rename from developers/guides/thumbnails-vod.mdx
rename to v1/developers/guides/thumbnails-vod.mdx
diff --git a/developers/guides/transcode-video-storj.mdx b/v1/developers/guides/transcode-video-storj.mdx
similarity index 100%
rename from developers/guides/transcode-video-storj.mdx
rename to v1/developers/guides/transcode-video-storj.mdx
diff --git a/developers/guides/transcode-video-w3s.mdx b/v1/developers/guides/transcode-video-w3s.mdx
similarity index 100%
rename from developers/guides/transcode-video-w3s.mdx
rename to v1/developers/guides/transcode-video-w3s.mdx
diff --git a/developers/guides/upload-video-asset.mdx b/v1/developers/guides/upload-video-asset.mdx
similarity index 100%
rename from developers/guides/upload-video-asset.mdx
rename to v1/developers/guides/upload-video-asset.mdx
diff --git a/v1/developers/introduction.mdx b/v1/developers/introduction.mdx
new file mode 100644
index 00000000..897dfbdf
--- /dev/null
+++ b/v1/developers/introduction.mdx
@@ -0,0 +1,61 @@
+---
+title: "Introduction"
+description: "Explore APIs, guides, and examples"
+icon: "hand-wave"
+---
+
+
+ If you're looking for documentation on Livepeer's hosted realtime StreamDiffusion AI platform "Daydream", please navigate [here](https://pipelines.livepeer.org/docs)
+
+
+Learn how to add live and on-demand video experience to your app using Livepeer
+Studio. Effortlessly manage livestreams, video uploads, API keys, network usage,
+billing, and more.
+
+
+
+ Get started with Livepeer Studio in less than 5 minutes.
+
+
+ Learn how to add live or on-demand video experiences to your app.
+
+
+ Explore the Livepeer Studio API
+
+
+ Get up and running with SDKs and pre-built UI components
+
+
+
+## Explore the Livepeer Studio SDKs
+
+Explore developer SDKs, pre-built UI components, and tools for interacting with
+the Livepeer Studio API.
+
+### Server-side SDKs
+
+
+
+
+
+
+
+
+
+
+
+
+
+### React Components
+
+
+
+ Fully customizable video player component for seamless playback
+
+
+ Full-featured broadcast component with controls, settings, and device
+ selection
+
+
+
+[View all developer tools](/sdks/introduction)
\ No newline at end of file
diff --git a/v1/developers/livepeer-studio-cli.mdx b/v1/developers/livepeer-studio-cli.mdx
new file mode 100644
index 00000000..7ec1aa64
--- /dev/null
+++ b/v1/developers/livepeer-studio-cli.mdx
@@ -0,0 +1,27 @@
+---
+title: CLI
+description: "Generate a new Livepeer app."
+icon: "rectangle-terminal"
+---
+
+The Livepeer Studio CLI is a command line tool that helps you generate a new
+Livepeer app in just a few seconds.
+
+## Getting Started
+
+First, create a Livepeer API key
+[here](https://livepeer.studio/dashboard/developers/api-keys). Next, use the CLI
+to generate a new project.
+
+```sh
+npx @livepeer/create
+```
+
+When prompted, enter your Livepeer **API key** and **Stream ID**.
+
+Once the app has been created, `cd` into the new directory and run the start
+command:
+
+```sh
+npm run dev
+```
diff --git a/v1/developers/quick-start.mdx b/v1/developers/quick-start.mdx
new file mode 100644
index 00000000..a1b7aa3d
--- /dev/null
+++ b/v1/developers/quick-start.mdx
@@ -0,0 +1,128 @@
+---
+title: Quickstart
+description:
+ "Learn how to create an API key and start adding live and on-demand video to
+ your app or website!"
+icon: "bolt"
+---
+
+First, go to [Livepeer Studio](https://livepeer.studio), if you haven't already,
+and create an account. Once you've created an account, you'll be able to create
+an API key by clicking on the "Create API Key" button on Developers page.
+
+
+ We do not recommend using ["CORS-enabled" API
+ keys](/api-reference/overview/authentication) - they will be deprecated in an
+ upcoming release. We recommend making requests from your backend to the
+ Livepeer Studio API.
+
+
+
+ 
+
+
+You can now use this API key in Livepeer SDKs and APIs in order to authenticate
+your requests and start building.
+
+
+ We recommend creating separate accounts for your development and production
+ environments. This will allow you to easily isolate your environments. We will
+ be shipping a solution for multi-environment management soon.
+
+
+In this exampe, we will use Javascript anld React to upload a video. Make sure
+to set up a React app first.
+
+## Install the JS SDK and Livepeer React
+
+We install both the NodeJS SDK (which works in all JS environments with `fetch`)
+and the Livepeer React library, which provides composable React primitives for
+building video apps.
+
+```
+npm install livepeer @livepeer/react
+```
+
+## Set up the SDK
+
+Add an API key to the environment variables, and construct a new Livepeer SDK
+client.
+
+```tsx
+import Livepeer from "livepeer";
+
+const livepeer = new Livepeer({
+ apiKey: process.env.YOUR_PRIVATE_API_KEY,
+});
+```
+
+## Retrieve playback info
+
+We can now use the SDK on the backend to fetch the playback info for our asset.
+
+This asset was uploaded using the dashboard, but this can also be an asset
+created from an application.
+
+```ts
+import { getSrc } from "@livepeer/react/external";
+
+const playbackId = "f5eese9wwl88k4g8";
+
+export const getPlaybackSource = () => {
+ const playbackInfo = await livepeer.playback.get(playbackId);
+
+ const src = getSrc(playbackInfo.playbackInfo);
+
+ return src;
+};
+```
+
+## Play the asset
+
+We can now use Player component from the SDK to play a video. In the below
+example, we style the elements with Tailwind, but you can use any styling
+solution:
+
+```tsx
+import { PauseIcon, PlayIcon } from "@livepeer/react/assets";
+import { getSrc } from "@livepeer/react/external";
+import * as Player from "@livepeer/react/player";
+import { vodSource } from "./source";
+
+export const DemoPlayer = ({ src }: { src: Src[] | null }) => {
+ return (
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ );
+};
+```
+
+## Start building
+
+Check out the [SDKs](/sdks/introduction) and
+[API Reference](/api-reference/overview/introduction) pages to learn more about
+how to use the SDKs and API to build your application.
+
+You can also refer to the [Guides](/developers/guides/overview) section for more
+in-depth tutorials on how to use the SDKs and API to build specific
+applications.
+
+Don't know where to start? Check out these four tutorials:
+
+- [Learn how to create a livestream](/developers/guides/create-livestream)
+- [Learn how to listen to asset events](/developers/guides/listen-to-asset-events)
diff --git a/developers/tutorials/decentralized-app-with-fvm.mdx b/v1/developers/tutorials/decentralized-app-with-fvm.mdx
similarity index 99%
rename from developers/tutorials/decentralized-app-with-fvm.mdx
rename to v1/developers/tutorials/decentralized-app-with-fvm.mdx
index 27250141..17ec1c2c 100644
--- a/developers/tutorials/decentralized-app-with-fvm.mdx
+++ b/v1/developers/tutorials/decentralized-app-with-fvm.mdx
@@ -553,7 +553,7 @@ Then, click on Create API Key, give a name to your key and then copy it as we
will need it later.
- 
+ 
Now back to the code, create a new file inside of the root directory named
diff --git a/developers/tutorials/token-gate-videos-with-lit.mdx b/v1/developers/tutorials/token-gate-videos-with-lit.mdx
similarity index 99%
rename from developers/tutorials/token-gate-videos-with-lit.mdx
rename to v1/developers/tutorials/token-gate-videos-with-lit.mdx
index 8451d051..69dedce2 100644
--- a/developers/tutorials/token-gate-videos-with-lit.mdx
+++ b/v1/developers/tutorials/token-gate-videos-with-lit.mdx
@@ -35,7 +35,7 @@ video application with Lit and Livepeer.
Here is a high-level workflow diagram of how Livepeer’s access control feature
works and how we will use it in our app:
-
+
## Prerequisites
Before you start with this tutorial, make sure you have the following tool
@@ -144,7 +144,7 @@ the sidebar.
+ page](/v1/images/tutorials/studio-create-api.png)
Then, click on Create API Key, give a name to your key, and then copy it as we
@@ -371,7 +371,7 @@ access control endpoint.
+ page](/v1/images/tutorials/studio-add-webhook.png)
Once created, copy the id of Webhook as we will need it later in the next step.
@@ -767,7 +767,7 @@ page:
-
+
diff --git a/developers/tutorials/upload-playback-videos-4everland.mdx b/v1/developers/tutorials/upload-playback-videos-4everland.mdx
similarity index 98%
rename from developers/tutorials/upload-playback-videos-4everland.mdx
rename to v1/developers/tutorials/upload-playback-videos-4everland.mdx
index 7bd7a325..8405686d 100644
--- a/developers/tutorials/upload-playback-videos-4everland.mdx
+++ b/v1/developers/tutorials/upload-playback-videos-4everland.mdx
@@ -126,7 +126,7 @@ Once you have created an account, in the dashboard, click on the Developers on
the sidebar.
- 
+ 
Then, click on Create API Key, give a name to your key and then copy it as we
diff --git a/developers/tutorials/upload-playback-videos-on-arweave.mdx b/v1/developers/tutorials/upload-playback-videos-on-arweave.mdx
similarity index 99%
rename from developers/tutorials/upload-playback-videos-on-arweave.mdx
rename to v1/developers/tutorials/upload-playback-videos-on-arweave.mdx
index 1be93256..3d4f4afd 100644
--- a/developers/tutorials/upload-playback-videos-on-arweave.mdx
+++ b/v1/developers/tutorials/upload-playback-videos-on-arweave.mdx
@@ -125,7 +125,7 @@ Once you have created an account, in the dashboard, click on the Developers on
the sidebar.
- 
+ 
Then, click on Create API Key, give a name to your key and then copy it as we
diff --git a/developers/tutorials/upload-playback-videos-on-ipfs.mdx b/v1/developers/tutorials/upload-playback-videos-on-ipfs.mdx
similarity index 99%
rename from developers/tutorials/upload-playback-videos-on-ipfs.mdx
rename to v1/developers/tutorials/upload-playback-videos-on-ipfs.mdx
index c99c2f94..85995c55 100644
--- a/developers/tutorials/upload-playback-videos-on-ipfs.mdx
+++ b/v1/developers/tutorials/upload-playback-videos-on-ipfs.mdx
@@ -124,7 +124,7 @@ the sidebar.
-
+
diff --git a/gateways/guides/docker-install.mdx b/v1/gateways/guides/docker-install.mdx
similarity index 100%
rename from gateways/guides/docker-install.mdx
rename to v1/gateways/guides/docker-install.mdx
diff --git a/gateways/guides/fund-gateway.mdx b/v1/gateways/guides/fund-gateway.mdx
similarity index 100%
rename from gateways/guides/fund-gateway.mdx
rename to v1/gateways/guides/fund-gateway.mdx
diff --git a/gateways/guides/gateway-overview.mdx b/v1/gateways/guides/gateway-overview.mdx
similarity index 100%
rename from gateways/guides/gateway-overview.mdx
rename to v1/gateways/guides/gateway-overview.mdx
diff --git a/gateways/guides/linux-install.mdx b/v1/gateways/guides/linux-install.mdx
similarity index 100%
rename from gateways/guides/linux-install.mdx
rename to v1/gateways/guides/linux-install.mdx
diff --git a/gateways/guides/playback-content.mdx b/v1/gateways/guides/playback-content.mdx
similarity index 100%
rename from gateways/guides/playback-content.mdx
rename to v1/gateways/guides/playback-content.mdx
diff --git a/gateways/guides/publish-content.mdx b/v1/gateways/guides/publish-content.mdx
similarity index 100%
rename from gateways/guides/publish-content.mdx
rename to v1/gateways/guides/publish-content.mdx
diff --git a/gateways/guides/transcoding-options.mdx b/v1/gateways/guides/transcoding-options.mdx
similarity index 100%
rename from gateways/guides/transcoding-options.mdx
rename to v1/gateways/guides/transcoding-options.mdx
diff --git a/gateways/guides/windows-install.mdx b/v1/gateways/guides/windows-install.mdx
similarity index 100%
rename from gateways/guides/windows-install.mdx
rename to v1/gateways/guides/windows-install.mdx
diff --git a/v1/gateways/introduction.mdx b/v1/gateways/introduction.mdx
new file mode 100644
index 00000000..897dfbdf
--- /dev/null
+++ b/v1/gateways/introduction.mdx
@@ -0,0 +1,61 @@
+---
+title: "Introduction"
+description: "Explore APIs, guides, and examples"
+icon: "hand-wave"
+---
+
+
+ If you're looking for documentation on Livepeer's hosted realtime StreamDiffusion AI platform "Daydream", please navigate [here](https://pipelines.livepeer.org/docs)
+
+
+Learn how to add live and on-demand video experience to your app using Livepeer
+Studio. Effortlessly manage livestreams, video uploads, API keys, network usage,
+billing, and more.
+
+
+
+ Get started with Livepeer Studio in less than 5 minutes.
+
+
+ Learn how to add live or on-demand video experiences to your app.
+
+
+ Explore the Livepeer Studio API
+
+
+ Get up and running with SDKs and pre-built UI components
+
+
+
+## Explore the Livepeer Studio SDKs
+
+Explore developer SDKs, pre-built UI components, and tools for interacting with
+the Livepeer Studio API.
+
+### Server-side SDKs
+
+
+
+
+
+
+
+
+
+
+
+
+
+### React Components
+
+
+
+ Fully customizable video player component for seamless playback
+
+
+ Full-featured broadcast component with controls, settings, and device
+ selection
+
+
+
+[View all developer tools](/sdks/introduction)
\ No newline at end of file
diff --git a/v1/gateways/livepeer-studio-cli.mdx b/v1/gateways/livepeer-studio-cli.mdx
new file mode 100644
index 00000000..7ec1aa64
--- /dev/null
+++ b/v1/gateways/livepeer-studio-cli.mdx
@@ -0,0 +1,27 @@
+---
+title: CLI
+description: "Generate a new Livepeer app."
+icon: "rectangle-terminal"
+---
+
+The Livepeer Studio CLI is a command line tool that helps you generate a new
+Livepeer app in just a few seconds.
+
+## Getting Started
+
+First, create a Livepeer API key
+[here](https://livepeer.studio/dashboard/developers/api-keys). Next, use the CLI
+to generate a new project.
+
+```sh
+npx @livepeer/create
+```
+
+When prompted, enter your Livepeer **API key** and **Stream ID**.
+
+Once the app has been created, `cd` into the new directory and run the start
+command:
+
+```sh
+npm run dev
+```
diff --git a/v1/gateways/quick-start.mdx b/v1/gateways/quick-start.mdx
new file mode 100644
index 00000000..a1b7aa3d
--- /dev/null
+++ b/v1/gateways/quick-start.mdx
@@ -0,0 +1,128 @@
+---
+title: Quickstart
+description:
+ "Learn how to create an API key and start adding live and on-demand video to
+ your app or website!"
+icon: "bolt"
+---
+
+First, go to [Livepeer Studio](https://livepeer.studio), if you haven't already,
+and create an account. Once you've created an account, you'll be able to create
+an API key by clicking on the "Create API Key" button on Developers page.
+
+
+ We do not recommend using ["CORS-enabled" API
+ keys](/api-reference/overview/authentication) - they will be deprecated in an
+ upcoming release. We recommend making requests from your backend to the
+ Livepeer Studio API.
+
+
+
+ 
+
+
+You can now use this API key in Livepeer SDKs and APIs in order to authenticate
+your requests and start building.
+
+
+ We recommend creating separate accounts for your development and production
+ environments. This will allow you to easily isolate your environments. We will
+ be shipping a solution for multi-environment management soon.
+
+
+In this exampe, we will use Javascript anld React to upload a video. Make sure
+to set up a React app first.
+
+## Install the JS SDK and Livepeer React
+
+We install both the NodeJS SDK (which works in all JS environments with `fetch`)
+and the Livepeer React library, which provides composable React primitives for
+building video apps.
+
+```
+npm install livepeer @livepeer/react
+```
+
+## Set up the SDK
+
+Add an API key to the environment variables, and construct a new Livepeer SDK
+client.
+
+```tsx
+import Livepeer from "livepeer";
+
+const livepeer = new Livepeer({
+ apiKey: process.env.YOUR_PRIVATE_API_KEY,
+});
+```
+
+## Retrieve playback info
+
+We can now use the SDK on the backend to fetch the playback info for our asset.
+
+This asset was uploaded using the dashboard, but this can also be an asset
+created from an application.
+
+```ts
+import { getSrc } from "@livepeer/react/external";
+
+const playbackId = "f5eese9wwl88k4g8";
+
+export const getPlaybackSource = () => {
+ const playbackInfo = await livepeer.playback.get(playbackId);
+
+ const src = getSrc(playbackInfo.playbackInfo);
+
+ return src;
+};
+```
+
+## Play the asset
+
+We can now use Player component from the SDK to play a video. In the below
+example, we style the elements with Tailwind, but you can use any styling
+solution:
+
+```tsx
+import { PauseIcon, PlayIcon } from "@livepeer/react/assets";
+import { getSrc } from "@livepeer/react/external";
+import * as Player from "@livepeer/react/player";
+import { vodSource } from "./source";
+
+export const DemoPlayer = ({ src }: { src: Src[] | null }) => {
+ return (
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ );
+};
+```
+
+## Start building
+
+Check out the [SDKs](/sdks/introduction) and
+[API Reference](/api-reference/overview/introduction) pages to learn more about
+how to use the SDKs and API to build your application.
+
+You can also refer to the [Guides](/developers/guides/overview) section for more
+in-depth tutorials on how to use the SDKs and API to build specific
+applications.
+
+Don't know where to start? Check out these four tutorials:
+
+- [Learn how to create a livestream](/developers/guides/create-livestream)
+- [Learn how to listen to asset events](/developers/guides/listen-to-asset-events)
diff --git a/images/ai/ai-serviceregistry-explorer-page.png b/v1/images/ai/ai-serviceregistry-explorer-page.png
similarity index 100%
rename from images/ai/ai-serviceregistry-explorer-page.png
rename to v1/images/ai/ai-serviceregistry-explorer-page.png
diff --git a/images/ai/ai-serviceregistry-setserviceuri.png b/v1/images/ai/ai-serviceregistry-setserviceuri.png
similarity index 100%
rename from images/ai/ai-serviceregistry-setserviceuri.png
rename to v1/images/ai/ai-serviceregistry-setserviceuri.png
diff --git a/images/ai/cool-cat-hat-moving.gif b/v1/images/ai/cool-cat-hat-moving.gif
similarity index 100%
rename from images/ai/cool-cat-hat-moving.gif
rename to v1/images/ai/cool-cat-hat-moving.gif
diff --git a/images/ai/cool-cat-hat.png b/v1/images/ai/cool-cat-hat.png
similarity index 100%
rename from images/ai/cool-cat-hat.png
rename to v1/images/ai/cool-cat-hat.png
diff --git a/images/ai/cool-cat-low-res.png b/v1/images/ai/cool-cat-low-res.png
similarity index 100%
rename from images/ai/cool-cat-low-res.png
rename to v1/images/ai/cool-cat-low-res.png
diff --git a/images/ai/cool-cat.png b/v1/images/ai/cool-cat.png
similarity index 100%
rename from images/ai/cool-cat.png
rename to v1/images/ai/cool-cat.png
diff --git a/images/ai/showcase/dream.png b/v1/images/ai/showcase/dream.png
similarity index 100%
rename from images/ai/showcase/dream.png
rename to v1/images/ai/showcase/dream.png
diff --git a/images/ai/showcase/inference_stronk_rocks.png b/v1/images/ai/showcase/inference_stronk_rocks.png
similarity index 100%
rename from images/ai/showcase/inference_stronk_rocks.png
rename to v1/images/ai/showcase/inference_stronk_rocks.png
diff --git a/images/ai/showcase/letsgenerate_ai.png b/v1/images/ai/showcase/letsgenerate_ai.png
similarity index 100%
rename from images/ai/showcase/letsgenerate_ai.png
rename to v1/images/ai/showcase/letsgenerate_ai.png
diff --git a/images/ai/showcase/tsunameme_ai.png b/v1/images/ai/showcase/tsunameme_ai.png
similarity index 100%
rename from images/ai/showcase/tsunameme_ai.png
rename to v1/images/ai/showcase/tsunameme_ai.png
diff --git a/images/ai/swagger_ui.png b/v1/images/ai/swagger_ui.png
similarity index 100%
rename from images/ai/swagger_ui.png
rename to v1/images/ai/swagger_ui.png
diff --git a/images/asset-page.png b/v1/images/asset-page.png
similarity index 100%
rename from images/asset-page.png
rename to v1/images/asset-page.png
diff --git a/images/background.png b/v1/images/background.png
similarity index 100%
rename from images/background.png
rename to v1/images/background.png
diff --git a/images/blender-poster-2.png b/v1/images/blender-poster-2.png
similarity index 100%
rename from images/blender-poster-2.png
rename to v1/images/blender-poster-2.png
diff --git a/images/blender-poster.png b/v1/images/blender-poster.png
similarity index 100%
rename from images/blender-poster.png
rename to v1/images/blender-poster.png
diff --git a/images/codepen-player.png b/v1/images/codepen-player.png
similarity index 100%
rename from images/codepen-player.png
rename to v1/images/codepen-player.png
diff --git a/images/create-api-key.png b/v1/images/create-api-key.png
similarity index 100%
rename from images/create-api-key.png
rename to v1/images/create-api-key.png
diff --git a/images/delegating-guides/arbitrum-oog.png b/v1/images/delegating-guides/arbitrum-oog.png
similarity index 100%
rename from images/delegating-guides/arbitrum-oog.png
rename to v1/images/delegating-guides/arbitrum-oog.png
diff --git a/images/delegating-guides/arbitrum-retry-ui.png b/v1/images/delegating-guides/arbitrum-retry-ui.png
similarity index 100%
rename from images/delegating-guides/arbitrum-retry-ui.png
rename to v1/images/delegating-guides/arbitrum-retry-ui.png
diff --git a/images/delegating-guides/claim-d.png b/v1/images/delegating-guides/claim-d.png
similarity index 100%
rename from images/delegating-guides/claim-d.png
rename to v1/images/delegating-guides/claim-d.png
diff --git a/images/delegating-guides/confirm-d.png b/v1/images/delegating-guides/confirm-d.png
similarity index 100%
rename from images/delegating-guides/confirm-d.png
rename to v1/images/delegating-guides/confirm-d.png
diff --git a/images/delegating-guides/connect-wallet-d.png b/v1/images/delegating-guides/connect-wallet-d.png
similarity index 100%
rename from images/delegating-guides/connect-wallet-d.png
rename to v1/images/delegating-guides/connect-wallet-d.png
diff --git a/images/delegating-guides/connect-wallet-d2.png b/v1/images/delegating-guides/connect-wallet-d2.png
similarity index 100%
rename from images/delegating-guides/connect-wallet-d2.png
rename to v1/images/delegating-guides/connect-wallet-d2.png
diff --git a/images/delegating-guides/migrate-d1.png b/v1/images/delegating-guides/migrate-d1.png
similarity index 100%
rename from images/delegating-guides/migrate-d1.png
rename to v1/images/delegating-guides/migrate-d1.png
diff --git a/images/engagement/Dashboard-1.png b/v1/images/engagement/Dashboard-1.png
similarity index 100%
rename from images/engagement/Dashboard-1.png
rename to v1/images/engagement/Dashboard-1.png
diff --git a/images/engagement/Dashboard-10.png b/v1/images/engagement/Dashboard-10.png
similarity index 100%
rename from images/engagement/Dashboard-10.png
rename to v1/images/engagement/Dashboard-10.png
diff --git a/images/engagement/Dashboard-4.png b/v1/images/engagement/Dashboard-4.png
similarity index 100%
rename from images/engagement/Dashboard-4.png
rename to v1/images/engagement/Dashboard-4.png
diff --git a/images/obs/LVS4.png b/v1/images/obs/LVS4.png
similarity index 100%
rename from images/obs/LVS4.png
rename to v1/images/obs/LVS4.png
diff --git a/images/obs/LVS5.png b/v1/images/obs/LVS5.png
similarity index 100%
rename from images/obs/LVS5.png
rename to v1/images/obs/LVS5.png
diff --git a/images/obs/OBS1.png b/v1/images/obs/OBS1.png
similarity index 100%
rename from images/obs/OBS1.png
rename to v1/images/obs/OBS1.png
diff --git a/images/obs/OBS2.png b/v1/images/obs/OBS2.png
similarity index 100%
rename from images/obs/OBS2.png
rename to v1/images/obs/OBS2.png
diff --git a/images/obs/OBS3.png b/v1/images/obs/OBS3.png
similarity index 100%
rename from images/obs/OBS3.png
rename to v1/images/obs/OBS3.png
diff --git a/images/obs/OBS4.png b/v1/images/obs/OBS4.png
similarity index 100%
rename from images/obs/OBS4.png
rename to v1/images/obs/OBS4.png
diff --git a/images/orchestrating-guides/begin-migration.png b/v1/images/orchestrating-guides/begin-migration.png
similarity index 100%
rename from images/orchestrating-guides/begin-migration.png
rename to v1/images/orchestrating-guides/begin-migration.png
diff --git a/images/orchestrating-guides/connect-wallet.png b/v1/images/orchestrating-guides/connect-wallet.png
similarity index 100%
rename from images/orchestrating-guides/connect-wallet.png
rename to v1/images/orchestrating-guides/connect-wallet.png
diff --git a/images/orchestrating-guides/connect-wallet2.png b/v1/images/orchestrating-guides/connect-wallet2.png
similarity index 100%
rename from images/orchestrating-guides/connect-wallet2.png
rename to v1/images/orchestrating-guides/connect-wallet2.png
diff --git a/images/orchestrating-guides/sign-cli.png b/v1/images/orchestrating-guides/sign-cli.png
similarity index 100%
rename from images/orchestrating-guides/sign-cli.png
rename to v1/images/orchestrating-guides/sign-cli.png
diff --git a/images/orchestrating-guides/sign-cli2.png b/v1/images/orchestrating-guides/sign-cli2.png
similarity index 100%
rename from images/orchestrating-guides/sign-cli2.png
rename to v1/images/orchestrating-guides/sign-cli2.png
diff --git a/images/orchestrating-guides/sign-cli3.png b/v1/images/orchestrating-guides/sign-cli3.png
similarity index 100%
rename from images/orchestrating-guides/sign-cli3.png
rename to v1/images/orchestrating-guides/sign-cli3.png
diff --git a/images/orchestrating-guides/sign-cli4.png b/v1/images/orchestrating-guides/sign-cli4.png
similarity index 100%
rename from images/orchestrating-guides/sign-cli4.png
rename to v1/images/orchestrating-guides/sign-cli4.png
diff --git a/images/orchestrating-guides/sign-web.png b/v1/images/orchestrating-guides/sign-web.png
similarity index 100%
rename from images/orchestrating-guides/sign-web.png
rename to v1/images/orchestrating-guides/sign-web.png
diff --git a/images/orchestrating-guides/stake-info.png b/v1/images/orchestrating-guides/stake-info.png
similarity index 100%
rename from images/orchestrating-guides/stake-info.png
rename to v1/images/orchestrating-guides/stake-info.png
diff --git a/images/poll.png b/v1/images/poll.png
similarity index 100%
rename from images/poll.png
rename to v1/images/poll.png
diff --git a/images/project-creation.png b/v1/images/project-creation.png
similarity index 100%
rename from images/project-creation.png
rename to v1/images/project-creation.png
diff --git a/images/quickstart/api-keys.png b/v1/images/quickstart/api-keys.png
similarity index 100%
rename from images/quickstart/api-keys.png
rename to v1/images/quickstart/api-keys.png
diff --git a/images/quickstart/cors.png b/v1/images/quickstart/cors.png
similarity index 100%
rename from images/quickstart/cors.png
rename to v1/images/quickstart/cors.png
diff --git a/images/quickstart/create-an-account.png b/v1/images/quickstart/create-an-account.png
similarity index 100%
rename from images/quickstart/create-an-account.png
rename to v1/images/quickstart/create-an-account.png
diff --git a/images/quickstart/create-an-api-key.png b/v1/images/quickstart/create-an-api-key.png
similarity index 100%
rename from images/quickstart/create-an-api-key.png
rename to v1/images/quickstart/create-an-api-key.png
diff --git a/images/quickstart/create-key.png b/v1/images/quickstart/create-key.png
similarity index 100%
rename from images/quickstart/create-key.png
rename to v1/images/quickstart/create-key.png
diff --git a/images/stream-health.png b/v1/images/stream-health.png
similarity index 100%
rename from images/stream-health.png
rename to v1/images/stream-health.png
diff --git a/images/stream-page.png b/v1/images/stream-page.png
similarity index 100%
rename from images/stream-page.png
rename to v1/images/stream-page.png
diff --git a/images/studio-in-browser-stream.png b/v1/images/studio-in-browser-stream.png
similarity index 100%
rename from images/studio-in-browser-stream.png
rename to v1/images/studio-in-browser-stream.png
diff --git a/images/titan-node.png b/v1/images/titan-node.png
similarity index 100%
rename from images/titan-node.png
rename to v1/images/titan-node.png
diff --git a/images/tutorials/authors/evan.jpeg b/v1/images/tutorials/authors/evan.jpeg
similarity index 100%
rename from images/tutorials/authors/evan.jpeg
rename to v1/images/tutorials/authors/evan.jpeg
diff --git a/images/tutorials/authors/suhail.jpeg b/v1/images/tutorials/authors/suhail.jpeg
similarity index 100%
rename from images/tutorials/authors/suhail.jpeg
rename to v1/images/tutorials/authors/suhail.jpeg
diff --git a/images/tutorials/grafana-connections.jpg b/v1/images/tutorials/grafana-connections.jpg
similarity index 100%
rename from images/tutorials/grafana-connections.jpg
rename to v1/images/tutorials/grafana-connections.jpg
diff --git a/images/tutorials/grafana-import-dashboard.png b/v1/images/tutorials/grafana-import-dashboard.png
similarity index 100%
rename from images/tutorials/grafana-import-dashboard.png
rename to v1/images/tutorials/grafana-import-dashboard.png
diff --git a/images/tutorials/guildxyz-app-homepage.png b/v1/images/tutorials/guildxyz-app-homepage.png
similarity index 100%
rename from images/tutorials/guildxyz-app-homepage.png
rename to v1/images/tutorials/guildxyz-app-homepage.png
diff --git a/images/tutorials/lit-app-homepage.png b/v1/images/tutorials/lit-app-homepage.png
similarity index 100%
rename from images/tutorials/lit-app-homepage.png
rename to v1/images/tutorials/lit-app-homepage.png
diff --git a/images/tutorials/livepeer_dashboard.png b/v1/images/tutorials/livepeer_dashboard.png
similarity index 100%
rename from images/tutorials/livepeer_dashboard.png
rename to v1/images/tutorials/livepeer_dashboard.png
diff --git a/images/tutorials/studio-add-webhook.png b/v1/images/tutorials/studio-add-webhook.png
similarity index 100%
rename from images/tutorials/studio-add-webhook.png
rename to v1/images/tutorials/studio-add-webhook.png
diff --git a/images/tutorials/studio-create-api.png b/v1/images/tutorials/studio-create-api.png
similarity index 100%
rename from images/tutorials/studio-create-api.png
rename to v1/images/tutorials/studio-create-api.png
diff --git a/images/tutorials/timeplus.png b/v1/images/tutorials/timeplus.png
similarity index 100%
rename from images/tutorials/timeplus.png
rename to v1/images/tutorials/timeplus.png
diff --git a/images/tutorials/vod-diagram.png b/v1/images/tutorials/vod-diagram.png
similarity index 100%
rename from images/tutorials/vod-diagram.png
rename to v1/images/tutorials/vod-diagram.png
diff --git a/images/vote-livepeer-cli-instructions.png b/v1/images/vote-livepeer-cli-instructions.png
similarity index 100%
rename from images/vote-livepeer-cli-instructions.png
rename to v1/images/vote-livepeer-cli-instructions.png
diff --git a/images/vote-livepeer-cli.png b/v1/images/vote-livepeer-cli.png
similarity index 100%
rename from images/vote-livepeer-cli.png
rename to v1/images/vote-livepeer-cli.png
diff --git a/images/waterfalls-poster.png b/v1/images/waterfalls-poster.png
similarity index 100%
rename from images/waterfalls-poster.png
rename to v1/images/waterfalls-poster.png
diff --git a/images/webhooks.png b/v1/images/webhooks.png
similarity index 100%
rename from images/webhooks.png
rename to v1/images/webhooks.png
diff --git a/images/webrtmp.png b/v1/images/webrtmp.png
similarity index 100%
rename from images/webrtmp.png
rename to v1/images/webrtmp.png
diff --git a/orchestrators/guides/assess-capabilities.mdx b/v1/orchestrators/guides/assess-capabilities.mdx
similarity index 100%
rename from orchestrators/guides/assess-capabilities.mdx
rename to v1/orchestrators/guides/assess-capabilities.mdx
diff --git a/orchestrators/guides/benchmark-transcoding.mdx b/v1/orchestrators/guides/benchmark-transcoding.mdx
similarity index 100%
rename from orchestrators/guides/benchmark-transcoding.mdx
rename to v1/orchestrators/guides/benchmark-transcoding.mdx
diff --git a/orchestrators/guides/configure-reward-calling.mdx b/v1/orchestrators/guides/configure-reward-calling.mdx
similarity index 100%
rename from orchestrators/guides/configure-reward-calling.mdx
rename to v1/orchestrators/guides/configure-reward-calling.mdx
diff --git a/orchestrators/guides/connect-to-arbitrum.mdx b/v1/orchestrators/guides/connect-to-arbitrum.mdx
similarity index 100%
rename from orchestrators/guides/connect-to-arbitrum.mdx
rename to v1/orchestrators/guides/connect-to-arbitrum.mdx
diff --git a/orchestrators/guides/dual-mine.mdx b/v1/orchestrators/guides/dual-mine.mdx
similarity index 100%
rename from orchestrators/guides/dual-mine.mdx
rename to v1/orchestrators/guides/dual-mine.mdx
diff --git a/orchestrators/guides/gateway-introspection.mdx b/v1/orchestrators/guides/gateway-introspection.mdx
similarity index 100%
rename from orchestrators/guides/gateway-introspection.mdx
rename to v1/orchestrators/guides/gateway-introspection.mdx
diff --git a/orchestrators/guides/get-started.mdx b/v1/orchestrators/guides/get-started.mdx
similarity index 100%
rename from orchestrators/guides/get-started.mdx
rename to v1/orchestrators/guides/get-started.mdx
diff --git a/orchestrators/guides/install-go-livepeer.mdx b/v1/orchestrators/guides/install-go-livepeer.mdx
similarity index 100%
rename from orchestrators/guides/install-go-livepeer.mdx
rename to v1/orchestrators/guides/install-go-livepeer.mdx
diff --git a/orchestrators/guides/migrate-from-contract-wallet.mdx b/v1/orchestrators/guides/migrate-from-contract-wallet.mdx
similarity index 100%
rename from orchestrators/guides/migrate-from-contract-wallet.mdx
rename to v1/orchestrators/guides/migrate-from-contract-wallet.mdx
diff --git a/orchestrators/guides/migrate-to-arbitrum.mdx b/v1/orchestrators/guides/migrate-to-arbitrum.mdx
similarity index 94%
rename from orchestrators/guides/migrate-to-arbitrum.mdx
rename to v1/orchestrators/guides/migrate-to-arbitrum.mdx
index d3811835..b5d60f58 100644
--- a/orchestrators/guides/migrate-to-arbitrum.mdx
+++ b/v1/orchestrators/guides/migrate-to-arbitrum.mdx
@@ -102,13 +102,13 @@ Alternatively, you can:
**For example:**
@@ -116,7 +116,7 @@ Alternatively, you can:
2. Navigate to the L2 Migration Tool to begin migration to Arbitrum:
@@ -133,7 +133,7 @@ Alternatively, you can:
browser extension.
@@ -149,7 +149,7 @@ Alternatively, you can:
> enter your Ethereum account address.
@@ -163,7 +163,7 @@ Alternatively, you can:
{' '}
@@ -176,7 +176,7 @@ Alternatively, you can:
{' '}
@@ -186,7 +186,7 @@ Alternatively, you can:
{' '}
diff --git a/orchestrators/guides/monitor-metrics.mdx b/v1/orchestrators/guides/monitor-metrics.mdx
similarity index 100%
rename from orchestrators/guides/monitor-metrics.mdx
rename to v1/orchestrators/guides/monitor-metrics.mdx
diff --git a/orchestrators/guides/o-t-split.mdx b/v1/orchestrators/guides/o-t-split.mdx
similarity index 100%
rename from orchestrators/guides/o-t-split.mdx
rename to v1/orchestrators/guides/o-t-split.mdx
diff --git a/orchestrators/guides/set-pricing.mdx b/v1/orchestrators/guides/set-pricing.mdx
similarity index 100%
rename from orchestrators/guides/set-pricing.mdx
rename to v1/orchestrators/guides/set-pricing.mdx
diff --git a/orchestrators/guides/set-session-limits.mdx b/v1/orchestrators/guides/set-session-limits.mdx
similarity index 100%
rename from orchestrators/guides/set-session-limits.mdx
rename to v1/orchestrators/guides/set-session-limits.mdx
diff --git a/orchestrators/guides/troubleshoot.mdx b/v1/orchestrators/guides/troubleshoot.mdx
similarity index 100%
rename from orchestrators/guides/troubleshoot.mdx
rename to v1/orchestrators/guides/troubleshoot.mdx
diff --git a/orchestrators/guides/vote.mdx b/v1/orchestrators/guides/vote.mdx
similarity index 91%
rename from orchestrators/guides/vote.mdx
rename to v1/orchestrators/guides/vote.mdx
index e98ee1c0..91d2505a 100644
--- a/orchestrators/guides/vote.mdx
+++ b/v1/orchestrators/guides/vote.mdx
@@ -16,7 +16,7 @@ Follow the steps herein to access and vote with the `livepeer_cli`:
- 
+ 
@@ -24,7 +24,7 @@ Follow the steps herein to access and vote with the `livepeer_cli`:
- 
+ 
@@ -33,7 +33,7 @@ Follow the steps herein to access and vote with the `livepeer_cli`:
- 
+ 
diff --git a/v1/orchestrators/introduction.mdx b/v1/orchestrators/introduction.mdx
new file mode 100644
index 00000000..897dfbdf
--- /dev/null
+++ b/v1/orchestrators/introduction.mdx
@@ -0,0 +1,61 @@
+---
+title: "Introduction"
+description: "Explore APIs, guides, and examples"
+icon: "hand-wave"
+---
+
+
+ If you're looking for documentation on Livepeer's hosted realtime StreamDiffusion AI platform "Daydream", please navigate [here](https://pipelines.livepeer.org/docs)
+
+
+Learn how to add live and on-demand video experience to your app using Livepeer
+Studio. Effortlessly manage livestreams, video uploads, API keys, network usage,
+billing, and more.
+
+
+
+ Get started with Livepeer Studio in less than 5 minutes.
+
+
+ Learn how to add live or on-demand video experiences to your app.
+
+
+ Explore the Livepeer Studio API
+
+
+ Get up and running with SDKs and pre-built UI components
+
+
+
+## Explore the Livepeer Studio SDKs
+
+Explore developer SDKs, pre-built UI components, and tools for interacting with
+the Livepeer Studio API.
+
+### Server-side SDKs
+
+
+
+
+
+
+
+
+
+
+
+
+
+### React Components
+
+
+
+ Fully customizable video player component for seamless playback
+
+
+ Full-featured broadcast component with controls, settings, and device
+ selection
+
+
+
+[View all developer tools](/sdks/introduction)
\ No newline at end of file
diff --git a/v1/orchestrators/livepeer-studio-cli.mdx b/v1/orchestrators/livepeer-studio-cli.mdx
new file mode 100644
index 00000000..7ec1aa64
--- /dev/null
+++ b/v1/orchestrators/livepeer-studio-cli.mdx
@@ -0,0 +1,27 @@
+---
+title: CLI
+description: "Generate a new Livepeer app."
+icon: "rectangle-terminal"
+---
+
+The Livepeer Studio CLI is a command line tool that helps you generate a new
+Livepeer app in just a few seconds.
+
+## Getting Started
+
+First, create a Livepeer API key
+[here](https://livepeer.studio/dashboard/developers/api-keys). Next, use the CLI
+to generate a new project.
+
+```sh
+npx @livepeer/create
+```
+
+When prompted, enter your Livepeer **API key** and **Stream ID**.
+
+Once the app has been created, `cd` into the new directory and run the start
+command:
+
+```sh
+npm run dev
+```
diff --git a/v1/orchestrators/quick-start.mdx b/v1/orchestrators/quick-start.mdx
new file mode 100644
index 00000000..a1b7aa3d
--- /dev/null
+++ b/v1/orchestrators/quick-start.mdx
@@ -0,0 +1,128 @@
+---
+title: Quickstart
+description:
+ "Learn how to create an API key and start adding live and on-demand video to
+ your app or website!"
+icon: "bolt"
+---
+
+First, go to [Livepeer Studio](https://livepeer.studio), if you haven't already,
+and create an account. Once you've created an account, you'll be able to create
+an API key by clicking on the "Create API Key" button on Developers page.
+
+
+ We do not recommend using ["CORS-enabled" API
+ keys](/api-reference/overview/authentication) - they will be deprecated in an
+ upcoming release. We recommend making requests from your backend to the
+ Livepeer Studio API.
+
+
+
+ 
+
+
+You can now use this API key in Livepeer SDKs and APIs in order to authenticate
+your requests and start building.
+
+
+ We recommend creating separate accounts for your development and production
+ environments. This will allow you to easily isolate your environments. We will
+ be shipping a solution for multi-environment management soon.
+
+
+In this exampe, we will use Javascript anld React to upload a video. Make sure
+to set up a React app first.
+
+## Install the JS SDK and Livepeer React
+
+We install both the NodeJS SDK (which works in all JS environments with `fetch`)
+and the Livepeer React library, which provides composable React primitives for
+building video apps.
+
+```
+npm install livepeer @livepeer/react
+```
+
+## Set up the SDK
+
+Add an API key to the environment variables, and construct a new Livepeer SDK
+client.
+
+```tsx
+import Livepeer from "livepeer";
+
+const livepeer = new Livepeer({
+ apiKey: process.env.YOUR_PRIVATE_API_KEY,
+});
+```
+
+## Retrieve playback info
+
+We can now use the SDK on the backend to fetch the playback info for our asset.
+
+This asset was uploaded using the dashboard, but this can also be an asset
+created from an application.
+
+```ts
+import { getSrc } from "@livepeer/react/external";
+
+const playbackId = "f5eese9wwl88k4g8";
+
+export const getPlaybackSource = () => {
+ const playbackInfo = await livepeer.playback.get(playbackId);
+
+ const src = getSrc(playbackInfo.playbackInfo);
+
+ return src;
+};
+```
+
+## Play the asset
+
+We can now use Player component from the SDK to play a video. In the below
+example, we style the elements with Tailwind, but you can use any styling
+solution:
+
+```tsx
+import { PauseIcon, PlayIcon } from "@livepeer/react/assets";
+import { getSrc } from "@livepeer/react/external";
+import * as Player from "@livepeer/react/player";
+import { vodSource } from "./source";
+
+export const DemoPlayer = ({ src }: { src: Src[] | null }) => {
+ return (
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ );
+};
+```
+
+## Start building
+
+Check out the [SDKs](/sdks/introduction) and
+[API Reference](/api-reference/overview/introduction) pages to learn more about
+how to use the SDKs and API to build your application.
+
+You can also refer to the [Guides](/developers/guides/overview) section for more
+in-depth tutorials on how to use the SDKs and API to build specific
+applications.
+
+Don't know where to start? Check out these four tutorials:
+
+- [Learn how to create a livestream](/developers/guides/create-livestream)
+- [Learn how to listen to asset events](/developers/guides/listen-to-asset-events)
diff --git a/references/api-support-matrix.mdx b/v1/references/api-support-matrix.mdx
similarity index 100%
rename from references/api-support-matrix.mdx
rename to v1/references/api-support-matrix.mdx
diff --git a/references/awesome-livepeer.mdx b/v1/references/awesome-livepeer.mdx
similarity index 100%
rename from references/awesome-livepeer.mdx
rename to v1/references/awesome-livepeer.mdx
diff --git a/references/contract-addresses.mdx b/v1/references/contract-addresses.mdx
similarity index 100%
rename from references/contract-addresses.mdx
rename to v1/references/contract-addresses.mdx
diff --git a/references/example-applications.mdx b/v1/references/example-applications.mdx
similarity index 100%
rename from references/example-applications.mdx
rename to v1/references/example-applications.mdx
diff --git a/references/go-livepeer/bandwidth-requirements.mdx b/v1/references/go-livepeer/bandwidth-requirements.mdx
similarity index 100%
rename from references/go-livepeer/bandwidth-requirements.mdx
rename to v1/references/go-livepeer/bandwidth-requirements.mdx
diff --git a/references/go-livepeer/cli-reference.mdx b/v1/references/go-livepeer/cli-reference.mdx
similarity index 100%
rename from references/go-livepeer/cli-reference.mdx
rename to v1/references/go-livepeer/cli-reference.mdx
diff --git a/references/go-livepeer/gpu-support.mdx b/v1/references/go-livepeer/gpu-support.mdx
similarity index 100%
rename from references/go-livepeer/gpu-support.mdx
rename to v1/references/go-livepeer/gpu-support.mdx
diff --git a/references/go-livepeer/hardware-requirements.mdx b/v1/references/go-livepeer/hardware-requirements.mdx
similarity index 100%
rename from references/go-livepeer/hardware-requirements.mdx
rename to v1/references/go-livepeer/hardware-requirements.mdx
diff --git a/references/go-livepeer/prometheus-metrics.mdx b/v1/references/go-livepeer/prometheus-metrics.mdx
similarity index 100%
rename from references/go-livepeer/prometheus-metrics.mdx
rename to v1/references/go-livepeer/prometheus-metrics.mdx
diff --git a/references/knowledge-base/livestream.mdx b/v1/references/knowledge-base/livestream.mdx
similarity index 100%
rename from references/knowledge-base/livestream.mdx
rename to v1/references/knowledge-base/livestream.mdx
diff --git a/references/knowledge-base/playback.mdx b/v1/references/knowledge-base/playback.mdx
similarity index 100%
rename from references/knowledge-base/playback.mdx
rename to v1/references/knowledge-base/playback.mdx
diff --git a/references/knowledge-base/vod.mdx b/v1/references/knowledge-base/vod.mdx
similarity index 100%
rename from references/knowledge-base/vod.mdx
rename to v1/references/knowledge-base/vod.mdx
diff --git a/references/subgraph.mdx b/v1/references/subgraph.mdx
similarity index 100%
rename from references/subgraph.mdx
rename to v1/references/subgraph.mdx
diff --git a/sdks/go.mdx b/v1/sdks/go.mdx
similarity index 100%
rename from sdks/go.mdx
rename to v1/sdks/go.mdx
diff --git a/sdks/introduction.mdx b/v1/sdks/introduction.mdx
similarity index 100%
rename from sdks/introduction.mdx
rename to v1/sdks/introduction.mdx
diff --git a/sdks/javascript.mdx b/v1/sdks/javascript.mdx
similarity index 100%
rename from sdks/javascript.mdx
rename to v1/sdks/javascript.mdx
diff --git a/sdks/python.mdx b/v1/sdks/python.mdx
similarity index 100%
rename from sdks/python.mdx
rename to v1/sdks/python.mdx
diff --git a/sdks/react/Broadcast.mdx b/v1/sdks/react/Broadcast.mdx
similarity index 100%
rename from sdks/react/Broadcast.mdx
rename to v1/sdks/react/Broadcast.mdx
diff --git a/sdks/react/Player.mdx b/v1/sdks/react/Player.mdx
similarity index 100%
rename from sdks/react/Player.mdx
rename to v1/sdks/react/Player.mdx
diff --git a/sdks/react/broadcast/Audio.mdx b/v1/sdks/react/broadcast/Audio.mdx
similarity index 100%
rename from sdks/react/broadcast/Audio.mdx
rename to v1/sdks/react/broadcast/Audio.mdx
diff --git a/sdks/react/broadcast/Camera.mdx b/v1/sdks/react/broadcast/Camera.mdx
similarity index 100%
rename from sdks/react/broadcast/Camera.mdx
rename to v1/sdks/react/broadcast/Camera.mdx
diff --git a/sdks/react/broadcast/Container.mdx b/v1/sdks/react/broadcast/Container.mdx
similarity index 100%
rename from sdks/react/broadcast/Container.mdx
rename to v1/sdks/react/broadcast/Container.mdx
diff --git a/sdks/react/broadcast/Controls.mdx b/v1/sdks/react/broadcast/Controls.mdx
similarity index 100%
rename from sdks/react/broadcast/Controls.mdx
rename to v1/sdks/react/broadcast/Controls.mdx
diff --git a/sdks/react/broadcast/Enabled.mdx b/v1/sdks/react/broadcast/Enabled.mdx
similarity index 100%
rename from sdks/react/broadcast/Enabled.mdx
rename to v1/sdks/react/broadcast/Enabled.mdx
diff --git a/sdks/react/broadcast/Error.mdx b/v1/sdks/react/broadcast/Error.mdx
similarity index 100%
rename from sdks/react/broadcast/Error.mdx
rename to v1/sdks/react/broadcast/Error.mdx
diff --git a/sdks/react/broadcast/Fullscreen.mdx b/v1/sdks/react/broadcast/Fullscreen.mdx
similarity index 100%
rename from sdks/react/broadcast/Fullscreen.mdx
rename to v1/sdks/react/broadcast/Fullscreen.mdx
diff --git a/sdks/react/broadcast/Loading.mdx b/v1/sdks/react/broadcast/Loading.mdx
similarity index 100%
rename from sdks/react/broadcast/Loading.mdx
rename to v1/sdks/react/broadcast/Loading.mdx
diff --git a/sdks/react/broadcast/PictureInPicture.mdx b/v1/sdks/react/broadcast/PictureInPicture.mdx
similarity index 100%
rename from sdks/react/broadcast/PictureInPicture.mdx
rename to v1/sdks/react/broadcast/PictureInPicture.mdx
diff --git a/sdks/react/broadcast/Portal.mdx b/v1/sdks/react/broadcast/Portal.mdx
similarity index 100%
rename from sdks/react/broadcast/Portal.mdx
rename to v1/sdks/react/broadcast/Portal.mdx
diff --git a/sdks/react/broadcast/Root.mdx b/v1/sdks/react/broadcast/Root.mdx
similarity index 100%
rename from sdks/react/broadcast/Root.mdx
rename to v1/sdks/react/broadcast/Root.mdx
diff --git a/sdks/react/broadcast/Screenshare.mdx b/v1/sdks/react/broadcast/Screenshare.mdx
similarity index 100%
rename from sdks/react/broadcast/Screenshare.mdx
rename to v1/sdks/react/broadcast/Screenshare.mdx
diff --git a/sdks/react/broadcast/Source.mdx b/v1/sdks/react/broadcast/Source.mdx
similarity index 100%
rename from sdks/react/broadcast/Source.mdx
rename to v1/sdks/react/broadcast/Source.mdx
diff --git a/sdks/react/broadcast/Status.mdx b/v1/sdks/react/broadcast/Status.mdx
similarity index 100%
rename from sdks/react/broadcast/Status.mdx
rename to v1/sdks/react/broadcast/Status.mdx
diff --git a/sdks/react/broadcast/Video.mdx b/v1/sdks/react/broadcast/Video.mdx
similarity index 100%
rename from sdks/react/broadcast/Video.mdx
rename to v1/sdks/react/broadcast/Video.mdx
diff --git a/sdks/react/broadcast/get-ingest.mdx b/v1/sdks/react/broadcast/get-ingest.mdx
similarity index 100%
rename from sdks/react/broadcast/get-ingest.mdx
rename to v1/sdks/react/broadcast/get-ingest.mdx
diff --git a/sdks/react/broadcast/useBroadcastContext.mdx b/v1/sdks/react/broadcast/useBroadcastContext.mdx
similarity index 100%
rename from sdks/react/broadcast/useBroadcastContext.mdx
rename to v1/sdks/react/broadcast/useBroadcastContext.mdx
diff --git a/sdks/react/getting-started.mdx b/v1/sdks/react/getting-started.mdx
similarity index 100%
rename from sdks/react/getting-started.mdx
rename to v1/sdks/react/getting-started.mdx
diff --git a/sdks/react/migration/3.x/Broadcast.mdx b/v1/sdks/react/migration/3.x/Broadcast.mdx
similarity index 100%
rename from sdks/react/migration/3.x/Broadcast.mdx
rename to v1/sdks/react/migration/3.x/Broadcast.mdx
diff --git a/sdks/react/migration/3.x/LivepeerConfig.mdx b/v1/sdks/react/migration/3.x/LivepeerConfig.mdx
similarity index 100%
rename from sdks/react/migration/3.x/LivepeerConfig.mdx
rename to v1/sdks/react/migration/3.x/LivepeerConfig.mdx
diff --git a/sdks/react/migration/3.x/Player.mdx b/v1/sdks/react/migration/3.x/Player.mdx
similarity index 99%
rename from sdks/react/migration/3.x/Player.mdx
rename to v1/sdks/react/migration/3.x/Player.mdx
index 9a3c6bf6..d92973b7 100644
--- a/sdks/react/migration/3.x/Player.mdx
+++ b/v1/sdks/react/migration/3.x/Player.mdx
@@ -508,7 +508,7 @@ function PlayerComponent() {
);
}
diff --git a/sdks/react/migration/3.x/asset/useAsset.mdx b/v1/sdks/react/migration/3.x/asset/useAsset.mdx
similarity index 100%
rename from sdks/react/migration/3.x/asset/useAsset.mdx
rename to v1/sdks/react/migration/3.x/asset/useAsset.mdx
diff --git a/sdks/react/migration/3.x/asset/useAssetMetrics.mdx b/v1/sdks/react/migration/3.x/asset/useAssetMetrics.mdx
similarity index 100%
rename from sdks/react/migration/3.x/asset/useAssetMetrics.mdx
rename to v1/sdks/react/migration/3.x/asset/useAssetMetrics.mdx
diff --git a/sdks/react/migration/3.x/asset/useCreateAsset.mdx b/v1/sdks/react/migration/3.x/asset/useCreateAsset.mdx
similarity index 100%
rename from sdks/react/migration/3.x/asset/useCreateAsset.mdx
rename to v1/sdks/react/migration/3.x/asset/useCreateAsset.mdx
diff --git a/sdks/react/migration/3.x/asset/useUpdateAsset.mdx b/v1/sdks/react/migration/3.x/asset/useUpdateAsset.mdx
similarity index 100%
rename from sdks/react/migration/3.x/asset/useUpdateAsset.mdx
rename to v1/sdks/react/migration/3.x/asset/useUpdateAsset.mdx
diff --git a/sdks/react/migration/3.x/client.mdx b/v1/sdks/react/migration/3.x/client.mdx
similarity index 100%
rename from sdks/react/migration/3.x/client.mdx
rename to v1/sdks/react/migration/3.x/client.mdx
diff --git a/sdks/react/migration/3.x/constants/abis.mdx b/v1/sdks/react/migration/3.x/constants/abis.mdx
similarity index 100%
rename from sdks/react/migration/3.x/constants/abis.mdx
rename to v1/sdks/react/migration/3.x/constants/abis.mdx
diff --git a/sdks/react/migration/3.x/constants/contract-addresses.mdx b/v1/sdks/react/migration/3.x/constants/contract-addresses.mdx
similarity index 100%
rename from sdks/react/migration/3.x/constants/contract-addresses.mdx
rename to v1/sdks/react/migration/3.x/constants/contract-addresses.mdx
diff --git a/sdks/react/migration/3.x/getting-started.mdx b/v1/sdks/react/migration/3.x/getting-started.mdx
similarity index 100%
rename from sdks/react/migration/3.x/getting-started.mdx
rename to v1/sdks/react/migration/3.x/getting-started.mdx
diff --git a/sdks/react/migration/3.x/playback/usePlaybackInfo.mdx b/v1/sdks/react/migration/3.x/playback/usePlaybackInfo.mdx
similarity index 100%
rename from sdks/react/migration/3.x/playback/usePlaybackInfo.mdx
rename to v1/sdks/react/migration/3.x/playback/usePlaybackInfo.mdx
diff --git a/sdks/react/migration/3.x/providers/studio.mdx b/v1/sdks/react/migration/3.x/providers/studio.mdx
similarity index 100%
rename from sdks/react/migration/3.x/providers/studio.mdx
rename to v1/sdks/react/migration/3.x/providers/studio.mdx
diff --git a/sdks/react/migration/3.x/stream/useCreateStream.mdx b/v1/sdks/react/migration/3.x/stream/useCreateStream.mdx
similarity index 100%
rename from sdks/react/migration/3.x/stream/useCreateStream.mdx
rename to v1/sdks/react/migration/3.x/stream/useCreateStream.mdx
diff --git a/sdks/react/migration/3.x/stream/useStream.mdx b/v1/sdks/react/migration/3.x/stream/useStream.mdx
similarity index 100%
rename from sdks/react/migration/3.x/stream/useStream.mdx
rename to v1/sdks/react/migration/3.x/stream/useStream.mdx
diff --git a/sdks/react/migration/3.x/stream/useStreamSession.mdx b/v1/sdks/react/migration/3.x/stream/useStreamSession.mdx
similarity index 100%
rename from sdks/react/migration/3.x/stream/useStreamSession.mdx
rename to v1/sdks/react/migration/3.x/stream/useStreamSession.mdx
diff --git a/sdks/react/migration/3.x/stream/useStreamSessions.mdx b/v1/sdks/react/migration/3.x/stream/useStreamSessions.mdx
similarity index 100%
rename from sdks/react/migration/3.x/stream/useStreamSessions.mdx
rename to v1/sdks/react/migration/3.x/stream/useStreamSessions.mdx
diff --git a/sdks/react/migration/3.x/stream/useUpdateStream.mdx b/v1/sdks/react/migration/3.x/stream/useUpdateStream.mdx
similarity index 100%
rename from sdks/react/migration/3.x/stream/useUpdateStream.mdx
rename to v1/sdks/react/migration/3.x/stream/useUpdateStream.mdx
diff --git a/sdks/react/migration/migration-4.x.mdx b/v1/sdks/react/migration/migration-4.x.mdx
similarity index 100%
rename from sdks/react/migration/migration-4.x.mdx
rename to v1/sdks/react/migration/migration-4.x.mdx
diff --git a/sdks/react/player/Clip.mdx b/v1/sdks/react/player/Clip.mdx
similarity index 100%
rename from sdks/react/player/Clip.mdx
rename to v1/sdks/react/player/Clip.mdx
diff --git a/sdks/react/player/Container.mdx b/v1/sdks/react/player/Container.mdx
similarity index 100%
rename from sdks/react/player/Container.mdx
rename to v1/sdks/react/player/Container.mdx
diff --git a/sdks/react/player/Controls.mdx b/v1/sdks/react/player/Controls.mdx
similarity index 100%
rename from sdks/react/player/Controls.mdx
rename to v1/sdks/react/player/Controls.mdx
diff --git a/sdks/react/player/Error.mdx b/v1/sdks/react/player/Error.mdx
similarity index 100%
rename from sdks/react/player/Error.mdx
rename to v1/sdks/react/player/Error.mdx
diff --git a/sdks/react/player/Fullscreen.mdx b/v1/sdks/react/player/Fullscreen.mdx
similarity index 100%
rename from sdks/react/player/Fullscreen.mdx
rename to v1/sdks/react/player/Fullscreen.mdx
diff --git a/sdks/react/player/Live.mdx b/v1/sdks/react/player/Live.mdx
similarity index 100%
rename from sdks/react/player/Live.mdx
rename to v1/sdks/react/player/Live.mdx
diff --git a/sdks/react/player/Loading.mdx b/v1/sdks/react/player/Loading.mdx
similarity index 100%
rename from sdks/react/player/Loading.mdx
rename to v1/sdks/react/player/Loading.mdx
diff --git a/sdks/react/player/PictureInPicture.mdx b/v1/sdks/react/player/PictureInPicture.mdx
similarity index 100%
rename from sdks/react/player/PictureInPicture.mdx
rename to v1/sdks/react/player/PictureInPicture.mdx
diff --git a/sdks/react/player/Play.mdx b/v1/sdks/react/player/Play.mdx
similarity index 100%
rename from sdks/react/player/Play.mdx
rename to v1/sdks/react/player/Play.mdx
diff --git a/sdks/react/player/Portal.mdx b/v1/sdks/react/player/Portal.mdx
similarity index 100%
rename from sdks/react/player/Portal.mdx
rename to v1/sdks/react/player/Portal.mdx
diff --git a/sdks/react/player/Poster.mdx b/v1/sdks/react/player/Poster.mdx
similarity index 100%
rename from sdks/react/player/Poster.mdx
rename to v1/sdks/react/player/Poster.mdx
diff --git a/sdks/react/player/RateSelect.mdx b/v1/sdks/react/player/RateSelect.mdx
similarity index 100%
rename from sdks/react/player/RateSelect.mdx
rename to v1/sdks/react/player/RateSelect.mdx
diff --git a/sdks/react/player/Root.mdx b/v1/sdks/react/player/Root.mdx
similarity index 100%
rename from sdks/react/player/Root.mdx
rename to v1/sdks/react/player/Root.mdx
diff --git a/sdks/react/player/Seek.mdx b/v1/sdks/react/player/Seek.mdx
similarity index 100%
rename from sdks/react/player/Seek.mdx
rename to v1/sdks/react/player/Seek.mdx
diff --git a/sdks/react/player/Time.mdx b/v1/sdks/react/player/Time.mdx
similarity index 100%
rename from sdks/react/player/Time.mdx
rename to v1/sdks/react/player/Time.mdx
diff --git a/sdks/react/player/Video.mdx b/v1/sdks/react/player/Video.mdx
similarity index 100%
rename from sdks/react/player/Video.mdx
rename to v1/sdks/react/player/Video.mdx
diff --git a/sdks/react/player/VideoQualitySelect.mdx b/v1/sdks/react/player/VideoQualitySelect.mdx
similarity index 100%
rename from sdks/react/player/VideoQualitySelect.mdx
rename to v1/sdks/react/player/VideoQualitySelect.mdx
diff --git a/sdks/react/player/Volume.mdx b/v1/sdks/react/player/Volume.mdx
similarity index 100%
rename from sdks/react/player/Volume.mdx
rename to v1/sdks/react/player/Volume.mdx
diff --git a/sdks/react/player/get-src.mdx b/v1/sdks/react/player/get-src.mdx
similarity index 100%
rename from sdks/react/player/get-src.mdx
rename to v1/sdks/react/player/get-src.mdx
diff --git a/sdks/react/player/useMediaContext.mdx b/v1/sdks/react/player/useMediaContext.mdx
similarity index 100%
rename from sdks/react/player/useMediaContext.mdx
rename to v1/sdks/react/player/useMediaContext.mdx
diff --git a/self-hosting/deploying.mdx b/v1/self-hosting/deploying.mdx
similarity index 100%
rename from self-hosting/deploying.mdx
rename to v1/self-hosting/deploying.mdx
diff --git a/self-hosting/how-to-contribute.mdx b/v1/self-hosting/how-to-contribute.mdx
similarity index 100%
rename from self-hosting/how-to-contribute.mdx
rename to v1/self-hosting/how-to-contribute.mdx
diff --git a/self-hosting/overview.mdx b/v1/self-hosting/overview.mdx
similarity index 100%
rename from self-hosting/overview.mdx
rename to v1/self-hosting/overview.mdx
diff --git a/self-hosting/self-hosting-with-docker.mdx b/v1/self-hosting/self-hosting-with-docker.mdx
similarity index 100%
rename from self-hosting/self-hosting-with-docker.mdx
rename to v1/self-hosting/self-hosting-with-docker.mdx
diff --git a/v2/.gitignore b/v2/.gitignore
new file mode 100644
index 00000000..75ab7974
--- /dev/null
+++ b/v2/.gitignore
@@ -0,0 +1,66 @@
+# ------------------------------------
+# Node
+# ------------------------------------
+node_modules/
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+package-lock.json
+yarn.lock
+pnpm-lock.yaml
+
+# Optional: ignore local `.env` files
+.env
+.env.*local
+
+# ------------------------------------
+# Logs
+# ------------------------------------
+logs/
+*.log
+*.log.*
+debug.log
+
+# ------------------------------------
+# OS / Editor files
+# ------------------------------------
+.DS_Store
+Thumbs.db
+.idea/
+
+# VSCode — allow settings.json, ignore rest
+.vscode/*
+!.vscode/settings.json
+!.vscode/extensions.json
+
+# ------------------------------------
+# Mintlify / Build Stuff
+# ------------------------------------
+.mintlify/
+.mintlify-cache/
+.out/
+dist/
+build/
+
+# ------------------------------------
+# Temporary files
+# ------------------------------------
+*.tmp
+*.temp
+*.swp
+*.swo
+
+# ------------------------------------
+# TypeScript
+# ------------------------------------
+*.tsbuildinfo
+
+# ------------------------------------
+# Project specific ignores
+# ------------------------------------
+gitbook-docs/
+mintlify-docs-examples/
+test/
+
+
diff --git a/v2/.prettierrc b/v2/.prettierrc
new file mode 100644
index 00000000..80a3328d
--- /dev/null
+++ b/v2/.prettierrc
@@ -0,0 +1,15 @@
+{
+ "semi": false,
+ "singleQuote": true,
+ "tabWidth": 2,
+ "trailingComma": "es5",
+ "proseWrap": "preserve",
+ "overrides": [
+ {
+ "files": "*.mdx",
+ "options": {
+ "parser": "mdx"
+ }
+ }
+ ]
+}
\ No newline at end of file
diff --git a/v2/ai-tools/claude-code.mdx b/v2/ai-tools/claude-code.mdx
new file mode 100644
index 00000000..ee2218d1
--- /dev/null
+++ b/v2/ai-tools/claude-code.mdx
@@ -0,0 +1,74 @@
+---
+title: "Claude Code setup"
+---
+
+Claude Code is Anthropic's official CLI tool. This guide will help you set up Claude Code to help you write and maintain your documentation.
+
+## Prerequisites
+
+- Active Claude subscription (Pro, Max, or API access)
+
+## Setup
+
+1. Install Claude Code globally:
+
+ ```bash
+ npm install -g @anthropic-ai/claude-code
+```
+
+2. Navigate to your docs directory.
+3. (Optional) Add the `CLAUDE.md` file below to your project.
+4. Run `claude` to start.
+
+## Create `CLAUDE.md`
+
+Create a `CLAUDE.md` file at the root of your documentation repository to train Claude Code on your specific documentation standards:
+
+````markdown
+# Mintlify documentation
+
+## Working relationship
+- You can push back on ideas-this can lead to better documentation. Cite sources and explain your reasoning when you do so
+- ALWAYS ask for clarification rather than making assumptions
+- NEVER lie, guess, or make up information
+
+## Project context
+- Format: MDX files with YAML frontmatter
+- Config: docs.json for navigation, theme, settings
+- Components: Mintlify components
+
+## Content strategy
+- Document just enough for user success - not too much, not too little
+- Prioritize accuracy and usability of information
+- Make content evergreen when possible
+- Search for existing information before adding new content. Avoid duplication unless it is done for a strategic reason
+- Check existing patterns for consistency
+- Start by making the smallest reasonable changes
+
+## Frontmatter requirements for pages
+- title: Clear, descriptive page title
+- description: Concise summary for SEO/navigation
+
+## Writing standards
+- Second-person voice ("you")
+- Prerequisites at start of procedural content
+- Test all code examples before publishing
+- Match style and formatting of existing pages
+- Include both basic and advanced use cases
+- Language tags on all code blocks
+- Alt text on all images
+- Relative paths for internal links
+
+## Git workflow
+- NEVER use --no-verify when committing
+- Ask how to handle uncommitted changes before starting
+- Create a new branch when no clear branch exists for changes
+- Commit frequently throughout development
+- NEVER skip or disable pre-commit hooks
+
+## Do not
+- Skip frontmatter on any MDX file
+- Use absolute URLs for internal links
+- Include untested code examples
+- Make assumptions - always ask for clarification
+````
diff --git a/v2/ai-tools/cursor.mdx b/v2/ai-tools/cursor.mdx
new file mode 100644
index 00000000..a9af8495
--- /dev/null
+++ b/v2/ai-tools/cursor.mdx
@@ -0,0 +1,418 @@
+---
+title: "Cursor setup"
+---
+
+Use Cursor to help write and maintain your documentation. This guide shows how to configure Cursor for better results on technical writing tasks and using Mintlify components.
+
+## Prerequisites
+
+- Cursor editor installed
+- Access to your documentation repository
+
+## Project rules
+
+Create project rules that all team members can use. In your documentation repository root:
+
+```bash
+mkdir -p .cursor
+```
+
+Create `.cursor/rules.md`:
+
+````markdown
+# Mintlify technical writing rule
+
+You are an AI writing assistant specialized in creating exceptional technical documentation using Mintlify components and following industry-leading technical writing practices.
+
+## Core writing principles
+
+### Language and style requirements
+
+- Use clear, direct language appropriate for technical audiences
+- Write in second person ("you") for instructions and procedures
+- Use active voice over passive voice
+- Employ present tense for current states, future tense for outcomes
+- Avoid jargon unless necessary and define terms when first used
+- Maintain consistent terminology throughout all documentation
+- Keep sentences concise while providing necessary context
+- Use parallel structure in lists, headings, and procedures
+
+### Content organization standards
+
+- Lead with the most important information (inverted pyramid structure)
+- Use progressive disclosure: basic concepts before advanced ones
+- Break complex procedures into numbered steps
+- Include prerequisites and context before instructions
+- Provide expected outcomes for each major step
+- Use descriptive, keyword-rich headings for navigation and SEO
+- Group related information logically with clear section breaks
+
+### User-centered approach
+
+- Focus on user goals and outcomes rather than system features
+- Anticipate common questions and address them proactively
+- Include troubleshooting for likely failure points
+- Write for scannability with clear headings, lists, and white space
+- Include verification steps to confirm success
+
+## Mintlify component reference
+
+### Callout components
+
+#### Note - Additional helpful information
+
+
+Supplementary information that supports the main content without interrupting flow
+
+
+#### Tip - Best practices and pro tips
+
+
+Expert advice, shortcuts, or best practices that enhance user success
+
+
+#### Warning - Important cautions
+
+
+Critical information about potential issues, breaking changes, or destructive actions
+
+
+#### Info - Neutral contextual information
+
+
+Background information, context, or neutral announcements
+
+
+#### Check - Success confirmations
+
+
+Positive confirmations, successful completions, or achievement indicators
+
+
+### Code components
+
+#### Single code block
+
+Example of a single code block:
+
+```javascript config.js
+const apiConfig = {
+ baseURL: 'https://api.example.com',
+ timeout: 5000,
+ headers: {
+ 'Authorization': `Bearer ${process.env.API_TOKEN}`
+ }
+};
+```
+
+#### Code group with multiple languages
+
+Example of a code group:
+
+
+```javascript Node.js
+const response = await fetch('/api/endpoint', {
+ headers: { Authorization: `Bearer ${apiKey}` }
+});
+```
+
+```python Python
+import requests
+response = requests.get('/api/endpoint',
+ headers={'Authorization': f'Bearer {api_key}'})
+```
+
+```curl cURL
+curl -X GET '/api/endpoint' \
+ -H 'Authorization: Bearer YOUR_API_KEY'
+```
+
+
+#### Request/response examples
+
+Example of request/response documentation:
+
+
+```bash cURL
+curl -X POST 'https://api.example.com/users' \
+ -H 'Content-Type: application/json' \
+ -d '{"name": "John Doe", "email": "john@example.com"}'
+```
+
+
+
+```json Success
+{
+ "id": "user_123",
+ "name": "John Doe",
+ "email": "john@example.com",
+ "created_at": "2024-01-15T10:30:00Z"
+}
+```
+
+
+### Structural components
+
+#### Steps for procedures
+
+Example of step-by-step instructions:
+
+
+
+ Run `npm install` to install required packages.
+
+
+ Verify installation by running `npm list`.
+
+
+
+
+ Create a `.env` file with your API credentials.
+
+ ```bash
+ API_KEY=your_api_key_here
+ ```
+
+
+ Never commit API keys to version control.
+
+
+
+
+#### Tabs for alternative content
+
+Example of tabbed content:
+
+
+
+ ```bash
+ brew install node
+ npm install -g package-name
+ ```
+
+
+
+ ```powershell
+ choco install nodejs
+ npm install -g package-name
+ ```
+
+
+
+ ```bash
+ sudo apt install nodejs npm
+ npm install -g package-name
+ ```
+
+
+
+#### Accordions for collapsible content
+
+Example of accordion groups:
+
+
+
+ - **Firewall blocking**: Ensure ports 80 and 443 are open
+ - **Proxy configuration**: Set HTTP_PROXY environment variable
+ - **DNS resolution**: Try using 8.8.8.8 as DNS server
+
+
+
+ ```javascript
+ const config = {
+ performance: { cache: true, timeout: 30000 },
+ security: { encryption: 'AES-256' }
+ };
+ ```
+
+
+
+### Cards and columns for emphasizing information
+
+Example of cards and card groups:
+
+
+Complete walkthrough from installation to your first API call in under 10 minutes.
+
+
+
+
+ Learn how to authenticate requests using API keys or JWT tokens.
+
+
+
+ Understand rate limits and best practices for high-volume usage.
+
+
+
+### API documentation components
+
+#### Parameter fields
+
+Example of parameter documentation:
+
+
+Unique identifier for the user. Must be a valid UUID v4 format.
+
+
+
+User's email address. Must be valid and unique within the system.
+
+
+
+Maximum number of results to return. Range: 1-100.
+
+
+
+Bearer token for API authentication. Format: `Bearer YOUR_API_KEY`
+
+
+#### Response fields
+
+Example of response field documentation:
+
+
+Unique identifier assigned to the newly created user.
+
+
+
+ISO 8601 formatted timestamp of when the user was created.
+
+
+
+List of permission strings assigned to this user.
+
+
+#### Expandable nested fields
+
+Example of nested field documentation:
+
+
+Complete user object with all associated data.
+
+
+
+ User profile information including personal details.
+
+
+
+ User's first name as entered during registration.
+
+
+
+ URL to user's profile picture. Returns null if no avatar is set.
+
+
+
+
+
+
+### Media and advanced components
+
+#### Frames for images
+
+Wrap all images in frames:
+
+
+
+
+
+
+
+
+
+#### Videos
+
+Use the HTML video element for self-hosted video content:
+
+
+
+Embed YouTube videos using iframe elements:
+
+
+
+#### Tooltips
+
+Example of tooltip usage:
+
+
+API
+
+
+#### Updates
+
+Use updates for changelogs:
+
+
+## New features
+- Added bulk user import functionality
+- Improved error messages with actionable suggestions
+
+## Bug fixes
+- Fixed pagination issue with large datasets
+- Resolved authentication timeout problems
+
+
+## Required page structure
+
+Every documentation page must begin with YAML frontmatter:
+
+```yaml
+---
+title: "Clear, specific, keyword-rich title"
+description: "Concise description explaining page purpose and value"
+---
+```
+
+## Content quality standards
+
+### Code examples requirements
+
+- Always include complete, runnable examples that users can copy and execute
+- Show proper error handling and edge case management
+- Use realistic data instead of placeholder values
+- Include expected outputs and results for verification
+- Test all code examples thoroughly before publishing
+- Specify language and include filename when relevant
+- Add explanatory comments for complex logic
+- Never include real API keys or secrets in code examples
+
+### API documentation requirements
+
+- Document all parameters including optional ones with clear descriptions
+- Show both success and error response examples with realistic data
+- Include rate limiting information with specific limits
+- Provide authentication examples showing proper format
+- Explain all HTTP status codes and error handling
+- Cover complete request/response cycles
+
+### Accessibility requirements
+
+- Include descriptive alt text for all images and diagrams
+- Use specific, actionable link text instead of "click here"
+- Ensure proper heading hierarchy starting with H2
+- Provide keyboard navigation considerations
+- Use sufficient color contrast in examples and visuals
+- Structure content for easy scanning with headers and lists
+
+## Component selection logic
+
+- Use **Steps** for procedures and sequential instructions
+- Use **Tabs** for platform-specific content or alternative approaches
+- Use **CodeGroup** when showing the same concept in multiple programming languages
+- Use **Accordions** for progressive disclosure of information
+- Use **RequestExample/ResponseExample** specifically for API endpoint documentation
+- Use **ParamField** for API parameters, **ResponseField** for API responses
+- Use **Expandable** for nested object properties or hierarchical information
+````
diff --git a/v2/ai-tools/windsurf.mdx b/v2/ai-tools/windsurf.mdx
new file mode 100644
index 00000000..c88e0992
--- /dev/null
+++ b/v2/ai-tools/windsurf.mdx
@@ -0,0 +1,94 @@
+---
+title: "Windsurf setup"
+---
+
+Configure Windsurf's Cascade AI assistant to help you write and maintain documentation. This guide shows how to set up Windsurf specifically for your Mintlify documentation workflow.
+
+## Prerequisites
+
+- Windsurf editor installed
+- Access to your documentation repository
+
+## Workspace rules
+
+Create workspace rules that provide Windsurf with context about your documentation project and standards.
+
+Create `.windsurf/rules.md` in your project root:
+
+````markdown
+# Mintlify technical writing rule
+
+## Project context
+
+- This is a documentation project on the Mintlify platform
+- We use MDX files with YAML frontmatter
+- Navigation is configured in `docs.json`
+- We follow technical writing best practices
+
+## Writing standards
+
+- Use second person ("you") for instructions
+- Write in active voice and present tense
+- Start procedures with prerequisites
+- Include expected outcomes for major steps
+- Use descriptive, keyword-rich headings
+- Keep sentences concise but informative
+
+## Required page structure
+
+Every page must start with frontmatter:
+
+```yaml
+---
+title: "Clear, specific title"
+description: "Concise description for SEO and navigation"
+---
+```
+
+## Mintlify components
+
+### Callouts
+
+- `` for helpful supplementary information
+- `` for important cautions and breaking changes
+- `` for best practices and expert advice
+- `` for neutral contextual information
+- `` for success confirmations
+
+### Code examples
+
+- When appropriate, include complete, runnable examples
+- Use `` for multiple language examples
+- Specify language tags on all code blocks
+- Include realistic data, not placeholders
+- Use `` and `` for API docs
+
+### Procedures
+
+- Use `` component for sequential instructions
+- Include verification steps with `` components when relevant
+- Break complex procedures into smaller steps
+
+### Content organization
+
+- Use `` for platform-specific content
+- Use `` for progressive disclosure
+- Use `` and `` for highlighting content
+- Wrap images in `` components with descriptive alt text
+
+## API documentation requirements
+
+- Document all parameters with ``
+- Show response structure with ``
+- Include both success and error examples
+- Use `` for nested object properties
+- Always include authentication examples
+
+## Quality standards
+
+- Test all code examples before publishing
+- Use relative paths for internal links
+- Include alt text for all images
+- Ensure proper heading hierarchy (start with h2)
+- Check existing patterns for consistency
+````
diff --git a/v2/assets/about/Building the Decentralized Generative AI Tech Stack.png b/v2/assets/about/Building the Decentralized Generative AI Tech Stack.png
new file mode 100644
index 00000000..2d77a6e3
Binary files /dev/null and b/v2/assets/about/Building the Decentralized Generative AI Tech Stack.png differ
diff --git a/v2/assets/about/Eric Shreck Gif.gif b/v2/assets/about/Eric Shreck Gif.gif
new file mode 100644
index 00000000..d046da7d
Binary files /dev/null and b/v2/assets/about/Eric Shreck Gif.gif differ
diff --git "a/v2/assets/about/Introducing Livepeer Cascade - A Vision For Livepeer\342\200\231s Future in the Age of Real-Time AI Video.png" "b/v2/assets/about/Introducing Livepeer Cascade - A Vision For Livepeer\342\200\231s Future in the Age of Real-Time AI Video.png"
new file mode 100644
index 00000000..282155e3
Binary files /dev/null and "b/v2/assets/about/Introducing Livepeer Cascade - A Vision For Livepeer\342\200\231s Future in the Age of Real-Time AI Video.png" differ
diff --git a/v2/assets/about/api-reference.jpg b/v2/assets/about/api-reference.jpg
new file mode 100644
index 00000000..13440be7
Binary files /dev/null and b/v2/assets/about/api-reference.jpg differ
diff --git a/v2/assets/about/hosted.jpg b/v2/assets/about/hosted.jpg
new file mode 100644
index 00000000..d5f275eb
Binary files /dev/null and b/v2/assets/about/hosted.jpg differ
diff --git a/v2/assets/about/image (1).png b/v2/assets/about/image (1).png
new file mode 100644
index 00000000..0ced5059
Binary files /dev/null and b/v2/assets/about/image (1).png differ
diff --git a/v2/assets/about/image.png b/v2/assets/about/image.png
new file mode 100644
index 00000000..196b4389
Binary files /dev/null and b/v2/assets/about/image.png differ
diff --git a/v2/assets/about/no-code.jpg b/v2/assets/about/no-code.jpg
new file mode 100644
index 00000000..fdf54211
Binary files /dev/null and b/v2/assets/about/no-code.jpg differ
diff --git a/v2/assets/community/Building the Decentralized Generative AI Tech Stack.png b/v2/assets/community/Building the Decentralized Generative AI Tech Stack.png
new file mode 100644
index 00000000..2d77a6e3
Binary files /dev/null and b/v2/assets/community/Building the Decentralized Generative AI Tech Stack.png differ
diff --git a/v2/assets/community/Eric Shreck Gif.gif b/v2/assets/community/Eric Shreck Gif.gif
new file mode 100644
index 00000000..d046da7d
Binary files /dev/null and b/v2/assets/community/Eric Shreck Gif.gif differ
diff --git a/v2/assets/community/Hero_90_Youtube.png b/v2/assets/community/Hero_90_Youtube.png
new file mode 100644
index 00000000..0d6c193b
Binary files /dev/null and b/v2/assets/community/Hero_90_Youtube.png differ
diff --git a/v2/assets/community/Hero_Blogging.png b/v2/assets/community/Hero_Blogging.png
new file mode 100644
index 00000000..dc9df26d
Binary files /dev/null and b/v2/assets/community/Hero_Blogging.png differ
diff --git a/v2/assets/community/Hero_Calendar.png b/v2/assets/community/Hero_Calendar.png
new file mode 100644
index 00000000..1a220e29
Binary files /dev/null and b/v2/assets/community/Hero_Calendar.png differ
diff --git a/v2/assets/community/Hero_Discord (1).png b/v2/assets/community/Hero_Discord (1).png
new file mode 100644
index 00000000..97a50e7d
Binary files /dev/null and b/v2/assets/community/Hero_Discord (1).png differ
diff --git a/v2/assets/community/Hero_Discord.png b/v2/assets/community/Hero_Discord.png
new file mode 100644
index 00000000..9012ad76
Binary files /dev/null and b/v2/assets/community/Hero_Discord.png differ
diff --git a/v2/assets/community/Hero_Events.png b/v2/assets/community/Hero_Events.png
new file mode 100644
index 00000000..e7208245
Binary files /dev/null and b/v2/assets/community/Hero_Events.png differ
diff --git a/v2/assets/community/Hero_Follow (1).png b/v2/assets/community/Hero_Follow (1).png
new file mode 100644
index 00000000..aad9b419
Binary files /dev/null and b/v2/assets/community/Hero_Follow (1).png differ
diff --git a/v2/assets/community/Hero_Follow.png b/v2/assets/community/Hero_Follow.png
new file mode 100644
index 00000000..aad9b419
Binary files /dev/null and b/v2/assets/community/Hero_Follow.png differ
diff --git a/v2/assets/community/Hero_Forum.png b/v2/assets/community/Hero_Forum.png
new file mode 100644
index 00000000..7383c45d
Binary files /dev/null and b/v2/assets/community/Hero_Forum.png differ
diff --git a/v2/assets/community/Hero_Github.png b/v2/assets/community/Hero_Github.png
new file mode 100644
index 00000000..7e262adf
Binary files /dev/null and b/v2/assets/community/Hero_Github.png differ
diff --git a/v2/assets/community/Hero_LinkedIn (1).png b/v2/assets/community/Hero_LinkedIn (1).png
new file mode 100644
index 00000000..98a4ff31
Binary files /dev/null and b/v2/assets/community/Hero_LinkedIn (1).png differ
diff --git a/v2/assets/community/Hero_LinkedIn.png b/v2/assets/community/Hero_LinkedIn.png
new file mode 100644
index 00000000..6453d52e
Binary files /dev/null and b/v2/assets/community/Hero_LinkedIn.png differ
diff --git a/v2/assets/community/Hero_Medium.png b/v2/assets/community/Hero_Medium.png
new file mode 100644
index 00000000..ffdb553b
Binary files /dev/null and b/v2/assets/community/Hero_Medium.png differ
diff --git a/v2/assets/community/Hero_Meeting.png b/v2/assets/community/Hero_Meeting.png
new file mode 100644
index 00000000..d375e91b
Binary files /dev/null and b/v2/assets/community/Hero_Meeting.png differ
diff --git a/v2/assets/community/Hero_Newsletter.png b/v2/assets/community/Hero_Newsletter.png
new file mode 100644
index 00000000..46029aea
Binary files /dev/null and b/v2/assets/community/Hero_Newsletter.png differ
diff --git a/v2/assets/community/Hero_Reddit.png b/v2/assets/community/Hero_Reddit.png
new file mode 100644
index 00000000..085b5be0
Binary files /dev/null and b/v2/assets/community/Hero_Reddit.png differ
diff --git a/v2/assets/community/Hero_Telegram.png b/v2/assets/community/Hero_Telegram.png
new file mode 100644
index 00000000..7d446243
Binary files /dev/null and b/v2/assets/community/Hero_Telegram.png differ
diff --git a/v2/assets/community/Hero_Telegran.png b/v2/assets/community/Hero_Telegran.png
new file mode 100644
index 00000000..185edab5
Binary files /dev/null and b/v2/assets/community/Hero_Telegran.png differ
diff --git a/v2/assets/community/Hero_X (1).png b/v2/assets/community/Hero_X (1).png
new file mode 100644
index 00000000..b7b6a178
Binary files /dev/null and b/v2/assets/community/Hero_X (1).png differ
diff --git a/v2/assets/community/Hero_X.png b/v2/assets/community/Hero_X.png
new file mode 100644
index 00000000..9d0be116
Binary files /dev/null and b/v2/assets/community/Hero_X.png differ
diff --git a/v2/assets/community/Hero_Yotube.png b/v2/assets/community/Hero_Yotube.png
new file mode 100644
index 00000000..1081eaab
Binary files /dev/null and b/v2/assets/community/Hero_Yotube.png differ
diff --git a/v2/assets/community/Hero_Youtube (1).png b/v2/assets/community/Hero_Youtube (1).png
new file mode 100644
index 00000000..7374586e
Binary files /dev/null and b/v2/assets/community/Hero_Youtube (1).png differ
diff --git a/v2/assets/community/Hero_Youtube.png b/v2/assets/community/Hero_Youtube.png
new file mode 100644
index 00000000..635ca8d7
Binary files /dev/null and b/v2/assets/community/Hero_Youtube.png differ
diff --git "a/v2/assets/community/Introducing Livepeer Cascade - A Vision For Livepeer\342\200\231s Future in the Age of Real-Time AI Video.png" "b/v2/assets/community/Introducing Livepeer Cascade - A Vision For Livepeer\342\200\231s Future in the Age of Real-Time AI Video.png"
new file mode 100644
index 00000000..282155e3
Binary files /dev/null and "b/v2/assets/community/Introducing Livepeer Cascade - A Vision For Livepeer\342\200\231s Future in the Age of Real-Time AI Video.png" differ
diff --git a/v2/assets/community/api-reference.jpg b/v2/assets/community/api-reference.jpg
new file mode 100644
index 00000000..13440be7
Binary files /dev/null and b/v2/assets/community/api-reference.jpg differ
diff --git a/v2/assets/community/hosted.jpg b/v2/assets/community/hosted.jpg
new file mode 100644
index 00000000..d5f275eb
Binary files /dev/null and b/v2/assets/community/hosted.jpg differ
diff --git a/v2/assets/community/image (1).png b/v2/assets/community/image (1).png
new file mode 100644
index 00000000..0ced5059
Binary files /dev/null and b/v2/assets/community/image (1).png differ
diff --git a/v2/assets/community/image.png b/v2/assets/community/image.png
new file mode 100644
index 00000000..196b4389
Binary files /dev/null and b/v2/assets/community/image.png differ
diff --git a/v2/assets/community/no-code.jpg b/v2/assets/community/no-code.jpg
new file mode 100644
index 00000000..fdf54211
Binary files /dev/null and b/v2/assets/community/no-code.jpg differ
diff --git a/v2/assets/developers/Building the Decentralized Generative AI Tech Stack.png b/v2/assets/developers/Building the Decentralized Generative AI Tech Stack.png
new file mode 100644
index 00000000..2d77a6e3
Binary files /dev/null and b/v2/assets/developers/Building the Decentralized Generative AI Tech Stack.png differ
diff --git a/v2/assets/developers/Eric Shreck Gif.gif b/v2/assets/developers/Eric Shreck Gif.gif
new file mode 100644
index 00000000..d046da7d
Binary files /dev/null and b/v2/assets/developers/Eric Shreck Gif.gif differ
diff --git "a/v2/assets/developers/Introducing Livepeer Cascade - A Vision For Livepeer\342\200\231s Future in the Age of Real-Time AI Video.png" "b/v2/assets/developers/Introducing Livepeer Cascade - A Vision For Livepeer\342\200\231s Future in the Age of Real-Time AI Video.png"
new file mode 100644
index 00000000..282155e3
Binary files /dev/null and "b/v2/assets/developers/Introducing Livepeer Cascade - A Vision For Livepeer\342\200\231s Future in the Age of Real-Time AI Video.png" differ
diff --git a/v2/assets/developers/api-reference.jpg b/v2/assets/developers/api-reference.jpg
new file mode 100644
index 00000000..13440be7
Binary files /dev/null and b/v2/assets/developers/api-reference.jpg differ
diff --git a/v2/assets/developers/hosted.jpg b/v2/assets/developers/hosted.jpg
new file mode 100644
index 00000000..d5f275eb
Binary files /dev/null and b/v2/assets/developers/hosted.jpg differ
diff --git a/v2/assets/developers/image (1).png b/v2/assets/developers/image (1).png
new file mode 100644
index 00000000..0ced5059
Binary files /dev/null and b/v2/assets/developers/image (1).png differ
diff --git a/v2/assets/developers/image.png b/v2/assets/developers/image.png
new file mode 100644
index 00000000..196b4389
Binary files /dev/null and b/v2/assets/developers/image.png differ
diff --git a/v2/assets/developers/no-code.jpg b/v2/assets/developers/no-code.jpg
new file mode 100644
index 00000000..fdf54211
Binary files /dev/null and b/v2/assets/developers/no-code.jpg differ
diff --git a/v2/assets/hero/Hero_Livepeer_Full.png b/v2/assets/hero/Hero_Livepeer_Full.png
new file mode 100644
index 00000000..b9a08577
Binary files /dev/null and b/v2/assets/hero/Hero_Livepeer_Full.png differ
diff --git a/v2/assets/hero/Hero_Livepeer_Full_sml.png b/v2/assets/hero/Hero_Livepeer_Full_sml.png
new file mode 100644
index 00000000..cc9589b8
Binary files /dev/null and b/v2/assets/hero/Hero_Livepeer_Full_sml.png differ
diff --git a/v2/assets/hero/hero_about.png b/v2/assets/hero/hero_about.png
new file mode 100644
index 00000000..6c873234
Binary files /dev/null and b/v2/assets/hero/hero_about.png differ
diff --git a/v2/assets/hero/hero_community.png b/v2/assets/hero/hero_community.png
new file mode 100644
index 00000000..37ca43b7
Binary files /dev/null and b/v2/assets/hero/hero_community.png differ
diff --git a/v2/assets/hero/hero_delegators.png b/v2/assets/hero/hero_delegators.png
new file mode 100644
index 00000000..f4d44c84
Binary files /dev/null and b/v2/assets/hero/hero_delegators.png differ
diff --git a/v2/assets/hero/hero_developer.png b/v2/assets/hero/hero_developer.png
new file mode 100644
index 00000000..9c8e72d1
Binary files /dev/null and b/v2/assets/hero/hero_developer.png differ
diff --git a/v2/assets/hero/hero_developer1.png b/v2/assets/hero/hero_developer1.png
new file mode 100644
index 00000000..feebc4ed
Binary files /dev/null and b/v2/assets/hero/hero_developer1.png differ
diff --git a/v2/assets/hero/hero_developer_logo.png b/v2/assets/hero/hero_developer_logo.png
new file mode 100644
index 00000000..74519fd0
Binary files /dev/null and b/v2/assets/hero/hero_developer_logo.png differ
diff --git a/v2/assets/hero/hero_gateways.png b/v2/assets/hero/hero_gateways.png
new file mode 100644
index 00000000..978231fb
Binary files /dev/null and b/v2/assets/hero/hero_gateways.png differ
diff --git a/v2/assets/hero/hero_gpu.png b/v2/assets/hero/hero_gpu.png
new file mode 100644
index 00000000..f45929de
Binary files /dev/null and b/v2/assets/hero/hero_gpu.png differ
diff --git a/v2/assets/hero/hero_help.png b/v2/assets/hero/hero_help.png
new file mode 100644
index 00000000..864d9ae2
Binary files /dev/null and b/v2/assets/hero/hero_help.png differ
diff --git a/v2/assets/hero/hero_logo_developer.png b/v2/assets/hero/hero_logo_developer.png
new file mode 100644
index 00000000..682f56ff
Binary files /dev/null and b/v2/assets/hero/hero_logo_developer.png differ
diff --git a/v2/assets/hero/hero_logo_developer_sml.png b/v2/assets/hero/hero_logo_developer_sml.png
new file mode 100644
index 00000000..8604989c
Binary files /dev/null and b/v2/assets/hero/hero_logo_developer_sml.png differ
diff --git a/v2/assets/hero/hero_logo_new.png b/v2/assets/hero/hero_logo_new.png
new file mode 100644
index 00000000..34e0f383
Binary files /dev/null and b/v2/assets/hero/hero_logo_new.png differ
diff --git a/v2/assets/hero/hero_opportunity.png b/v2/assets/hero/hero_opportunity.png
new file mode 100644
index 00000000..ccd00b0a
Binary files /dev/null and b/v2/assets/hero/hero_opportunity.png differ
diff --git a/v2/assets/hero/hero_partner.png b/v2/assets/hero/hero_partner.png
new file mode 100644
index 00000000..d8d0590d
Binary files /dev/null and b/v2/assets/hero/hero_partner.png differ
diff --git a/v2/assets/hero/hero_reference.png b/v2/assets/hero/hero_reference.png
new file mode 100644
index 00000000..63f43b2e
Binary files /dev/null and b/v2/assets/hero/hero_reference.png differ
diff --git a/v2/assets/hero/hero_researchers.png b/v2/assets/hero/hero_researchers.png
new file mode 100644
index 00000000..8aa2c1e4
Binary files /dev/null and b/v2/assets/hero/hero_researchers.png differ
diff --git a/v2/assets/hero/hero_showcase.png b/v2/assets/hero/hero_showcase.png
new file mode 100644
index 00000000..41580daa
Binary files /dev/null and b/v2/assets/hero/hero_showcase.png differ
diff --git a/v2/assets/hero/hero_word_NEW.png b/v2/assets/hero/hero_word_NEW.png
new file mode 100644
index 00000000..b6dbdfb3
Binary files /dev/null and b/v2/assets/hero/hero_word_NEW.png differ
diff --git a/v2/assets/hero/hero_word_developer.png b/v2/assets/hero/hero_word_developer.png
new file mode 100644
index 00000000..51eb69d9
Binary files /dev/null and b/v2/assets/hero/hero_word_developer.png differ
diff --git a/v2/assets/home/Building the Decentralized Generative AI Tech Stack.png b/v2/assets/home/Building the Decentralized Generative AI Tech Stack.png
new file mode 100644
index 00000000..2d77a6e3
Binary files /dev/null and b/v2/assets/home/Building the Decentralized Generative AI Tech Stack.png differ
diff --git a/v2/assets/home/Eric Shreck Gif.gif b/v2/assets/home/Eric Shreck Gif.gif
new file mode 100644
index 00000000..d046da7d
Binary files /dev/null and b/v2/assets/home/Eric Shreck Gif.gif differ
diff --git a/v2/assets/home/Hero_Images/hero_about.png b/v2/assets/home/Hero_Images/hero_about.png
new file mode 100644
index 00000000..6c873234
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_about.png differ
diff --git a/v2/assets/home/Hero_Images/hero_community.png b/v2/assets/home/Hero_Images/hero_community.png
new file mode 100644
index 00000000..37ca43b7
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_community.png differ
diff --git a/v2/assets/home/Hero_Images/hero_delegators.png b/v2/assets/home/Hero_Images/hero_delegators.png
new file mode 100644
index 00000000..f4d44c84
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_delegators.png differ
diff --git a/v2/assets/home/Hero_Images/hero_developer.png b/v2/assets/home/Hero_Images/hero_developer.png
new file mode 100644
index 00000000..9c8e72d1
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_developer.png differ
diff --git a/v2/assets/home/Hero_Images/hero_developer1.png b/v2/assets/home/Hero_Images/hero_developer1.png
new file mode 100644
index 00000000..feebc4ed
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_developer1.png differ
diff --git a/v2/assets/home/Hero_Images/hero_developer_logo.png b/v2/assets/home/Hero_Images/hero_developer_logo.png
new file mode 100644
index 00000000..74519fd0
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_developer_logo.png differ
diff --git a/v2/assets/home/Hero_Images/hero_gateways.png b/v2/assets/home/Hero_Images/hero_gateways.png
new file mode 100644
index 00000000..978231fb
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_gateways.png differ
diff --git a/v2/assets/home/Hero_Images/hero_gpu.png b/v2/assets/home/Hero_Images/hero_gpu.png
new file mode 100644
index 00000000..f45929de
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_gpu.png differ
diff --git a/v2/assets/home/Hero_Images/hero_help.png b/v2/assets/home/Hero_Images/hero_help.png
new file mode 100644
index 00000000..864d9ae2
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_help.png differ
diff --git a/v2/assets/home/Hero_Images/hero_logo_developer.png b/v2/assets/home/Hero_Images/hero_logo_developer.png
new file mode 100644
index 00000000..682f56ff
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_logo_developer.png differ
diff --git a/v2/assets/home/Hero_Images/hero_logo_developer_sml.png b/v2/assets/home/Hero_Images/hero_logo_developer_sml.png
new file mode 100644
index 00000000..8604989c
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_logo_developer_sml.png differ
diff --git a/v2/assets/home/Hero_Images/hero_logo_new.png b/v2/assets/home/Hero_Images/hero_logo_new.png
new file mode 100644
index 00000000..34e0f383
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_logo_new.png differ
diff --git a/v2/assets/home/Hero_Images/hero_opportunity.png b/v2/assets/home/Hero_Images/hero_opportunity.png
new file mode 100644
index 00000000..ccd00b0a
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_opportunity.png differ
diff --git a/v2/assets/home/Hero_Images/hero_partner.png b/v2/assets/home/Hero_Images/hero_partner.png
new file mode 100644
index 00000000..d8d0590d
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_partner.png differ
diff --git a/v2/assets/home/Hero_Images/hero_reference.png b/v2/assets/home/Hero_Images/hero_reference.png
new file mode 100644
index 00000000..63f43b2e
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_reference.png differ
diff --git a/v2/assets/home/Hero_Images/hero_research.png b/v2/assets/home/Hero_Images/hero_research.png
new file mode 100644
index 00000000..dd73c37d
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_research.png differ
diff --git a/v2/assets/home/Hero_Images/hero_researchers.png b/v2/assets/home/Hero_Images/hero_researchers.png
new file mode 100644
index 00000000..8aa2c1e4
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_researchers.png differ
diff --git a/v2/assets/home/Hero_Images/hero_showcase.png b/v2/assets/home/Hero_Images/hero_showcase.png
new file mode 100644
index 00000000..41580daa
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_showcase.png differ
diff --git a/v2/assets/home/Hero_Images/hero_word_NEW.png b/v2/assets/home/Hero_Images/hero_word_NEW.png
new file mode 100644
index 00000000..b6dbdfb3
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_word_NEW.png differ
diff --git a/v2/assets/home/Hero_Images/hero_word_developer.png b/v2/assets/home/Hero_Images/hero_word_developer.png
new file mode 100644
index 00000000..51eb69d9
Binary files /dev/null and b/v2/assets/home/Hero_Images/hero_word_developer.png differ
diff --git "a/v2/assets/home/Introducing Livepeer Cascade - A Vision For Livepeer\342\200\231s Future in the Age of Real-Time AI Video.png" "b/v2/assets/home/Introducing Livepeer Cascade - A Vision For Livepeer\342\200\231s Future in the Age of Real-Time AI Video.png"
new file mode 100644
index 00000000..282155e3
Binary files /dev/null and "b/v2/assets/home/Introducing Livepeer Cascade - A Vision For Livepeer\342\200\231s Future in the Age of Real-Time AI Video.png" differ
diff --git a/v2/assets/home/Livepeer-Logo-Full-Dark.svg b/v2/assets/home/Livepeer-Logo-Full-Dark.svg
new file mode 100644
index 00000000..0fa35534
--- /dev/null
+++ b/v2/assets/home/Livepeer-Logo-Full-Dark.svg
@@ -0,0 +1,16 @@
+
diff --git a/v2/assets/home/Livepeer-Logo-Full-Light.svg b/v2/assets/home/Livepeer-Logo-Full-Light.svg
new file mode 100644
index 00000000..5a414a41
--- /dev/null
+++ b/v2/assets/home/Livepeer-Logo-Full-Light.svg
@@ -0,0 +1,16 @@
+
diff --git a/v2/assets/home/livepeer logo.png b/v2/assets/home/livepeer logo.png
new file mode 100644
index 00000000..a8fce5ca
Binary files /dev/null and b/v2/assets/home/livepeer logo.png differ
diff --git a/v2/assets/home/livepeer_evolution_slide.png b/v2/assets/home/livepeer_evolution_slide.png
new file mode 100644
index 00000000..196b4389
Binary files /dev/null and b/v2/assets/home/livepeer_evolution_slide.png differ
diff --git a/v2/assets/home/whitepaper_diagram.png b/v2/assets/home/whitepaper_diagram.png
new file mode 100644
index 00000000..0ced5059
Binary files /dev/null and b/v2/assets/home/whitepaper_diagram.png differ
diff --git a/v2/assets/logo/dark.svg b/v2/assets/logo/dark.svg
new file mode 100644
index 00000000..245d63ba
--- /dev/null
+++ b/v2/assets/logo/dark.svg
@@ -0,0 +1,14 @@
+
diff --git a/v2/assets/logo/light.svg b/v2/assets/logo/light.svg
new file mode 100644
index 00000000..82c99695
--- /dev/null
+++ b/v2/assets/logo/light.svg
@@ -0,0 +1,14 @@
+
diff --git a/v2/assets/orchestrators/Building the Decentralized Generative AI Tech Stack.png b/v2/assets/orchestrators/Building the Decentralized Generative AI Tech Stack.png
new file mode 100644
index 00000000..2d77a6e3
Binary files /dev/null and b/v2/assets/orchestrators/Building the Decentralized Generative AI Tech Stack.png differ
diff --git a/v2/assets/orchestrators/Eric Shreck Gif.gif b/v2/assets/orchestrators/Eric Shreck Gif.gif
new file mode 100644
index 00000000..d046da7d
Binary files /dev/null and b/v2/assets/orchestrators/Eric Shreck Gif.gif differ
diff --git "a/v2/assets/orchestrators/Introducing Livepeer Cascade - A Vision For Livepeer\342\200\231s Future in the Age of Real-Time AI Video.png" "b/v2/assets/orchestrators/Introducing Livepeer Cascade - A Vision For Livepeer\342\200\231s Future in the Age of Real-Time AI Video.png"
new file mode 100644
index 00000000..282155e3
Binary files /dev/null and "b/v2/assets/orchestrators/Introducing Livepeer Cascade - A Vision For Livepeer\342\200\231s Future in the Age of Real-Time AI Video.png" differ
diff --git a/v2/assets/orchestrators/api-reference.jpg b/v2/assets/orchestrators/api-reference.jpg
new file mode 100644
index 00000000..13440be7
Binary files /dev/null and b/v2/assets/orchestrators/api-reference.jpg differ
diff --git a/v2/assets/orchestrators/hosted.jpg b/v2/assets/orchestrators/hosted.jpg
new file mode 100644
index 00000000..d5f275eb
Binary files /dev/null and b/v2/assets/orchestrators/hosted.jpg differ
diff --git a/v2/assets/orchestrators/image (1).png b/v2/assets/orchestrators/image (1).png
new file mode 100644
index 00000000..0ced5059
Binary files /dev/null and b/v2/assets/orchestrators/image (1).png differ
diff --git a/v2/assets/orchestrators/image.png b/v2/assets/orchestrators/image.png
new file mode 100644
index 00000000..196b4389
Binary files /dev/null and b/v2/assets/orchestrators/image.png differ
diff --git a/v2/assets/orchestrators/no-code.jpg b/v2/assets/orchestrators/no-code.jpg
new file mode 100644
index 00000000..fdf54211
Binary files /dev/null and b/v2/assets/orchestrators/no-code.jpg differ
diff --git a/v2/assets/products/daydream-logo-dark.svg b/v2/assets/products/daydream-logo-dark.svg
new file mode 100644
index 00000000..7c870505
--- /dev/null
+++ b/v2/assets/products/daydream-logo-dark.svg
@@ -0,0 +1,32 @@
+
+
\ No newline at end of file
diff --git a/v2/assets/products/livepeer-studio-logo.svg b/v2/assets/products/livepeer-studio-logo.svg
new file mode 100644
index 00000000..c273c464
--- /dev/null
+++ b/v2/assets/products/livepeer-studio-logo.svg
@@ -0,0 +1,22 @@
+
diff --git a/v2/assets/products/streamplace-cube.png b/v2/assets/products/streamplace-cube.png
new file mode 100644
index 00000000..d5eddb3d
Binary files /dev/null and b/v2/assets/products/streamplace-cube.png differ
diff --git a/v2/assets/products/streamplace-logo.svg b/v2/assets/products/streamplace-logo.svg
new file mode 100644
index 00000000..36ccf44f
--- /dev/null
+++ b/v2/assets/products/streamplace-logo.svg
@@ -0,0 +1,29 @@
+
diff --git a/v2/assets/site/favicon/apple-touch-icon.png b/v2/assets/site/favicon/apple-touch-icon.png
new file mode 100644
index 00000000..81c47ff0
Binary files /dev/null and b/v2/assets/site/favicon/apple-touch-icon.png differ
diff --git a/v2/assets/site/favicon/favicon-96x96.png b/v2/assets/site/favicon/favicon-96x96.png
new file mode 100644
index 00000000..48ca97ee
Binary files /dev/null and b/v2/assets/site/favicon/favicon-96x96.png differ
diff --git a/v2/assets/site/favicon/favicon.ico b/v2/assets/site/favicon/favicon.ico
new file mode 100644
index 00000000..62dd3311
Binary files /dev/null and b/v2/assets/site/favicon/favicon.ico differ
diff --git a/v2/assets/site/favicon/favicon.svg b/v2/assets/site/favicon/favicon.svg
new file mode 100644
index 00000000..60d6d1ea
--- /dev/null
+++ b/v2/assets/site/favicon/favicon.svg
@@ -0,0 +1,21 @@
+
\ No newline at end of file
diff --git a/v2/assets/site/favicon/site.webmanifest b/v2/assets/site/favicon/site.webmanifest
new file mode 100644
index 00000000..ccf313a3
--- /dev/null
+++ b/v2/assets/site/favicon/site.webmanifest
@@ -0,0 +1,21 @@
+{
+ "name": "MyWebSite",
+ "short_name": "MySite",
+ "icons": [
+ {
+ "src": "/web-app-manifest-192x192.png",
+ "sizes": "192x192",
+ "type": "image/png",
+ "purpose": "maskable"
+ },
+ {
+ "src": "/web-app-manifest-512x512.png",
+ "sizes": "512x512",
+ "type": "image/png",
+ "purpose": "maskable"
+ }
+ ],
+ "theme_color": "#ffffff",
+ "background_color": "#ffffff",
+ "display": "standalone"
+}
\ No newline at end of file
diff --git a/v2/assets/site/favicon/web-app-manifest-192x192.png b/v2/assets/site/favicon/web-app-manifest-192x192.png
new file mode 100644
index 00000000..ac462cc0
Binary files /dev/null and b/v2/assets/site/favicon/web-app-manifest-192x192.png differ
diff --git a/v2/assets/site/favicon/web-app-manifest-512x512.png b/v2/assets/site/favicon/web-app-manifest-512x512.png
new file mode 100644
index 00000000..0fa9860e
Binary files /dev/null and b/v2/assets/site/favicon/web-app-manifest-512x512.png differ
diff --git a/v2/assets/site/images/404-desolate.jpeg b/v2/assets/site/images/404-desolate.jpeg
new file mode 100644
index 00000000..b6997186
Binary files /dev/null and b/v2/assets/site/images/404-desolate.jpeg differ
diff --git a/v2/assets/site/logos/Livepeer-Logo-Full-Dark.svg b/v2/assets/site/logos/Livepeer-Logo-Full-Dark.svg
new file mode 100644
index 00000000..0fa35534
--- /dev/null
+++ b/v2/assets/site/logos/Livepeer-Logo-Full-Dark.svg
@@ -0,0 +1,16 @@
+
diff --git a/v2/assets/site/logos/Livepeer-Logo-Full-Light.svg b/v2/assets/site/logos/Livepeer-Logo-Full-Light.svg
new file mode 100644
index 00000000..5a414a41
--- /dev/null
+++ b/v2/assets/site/logos/Livepeer-Logo-Full-Light.svg
@@ -0,0 +1,16 @@
+
diff --git a/v2/assets/site/logos/Livepeer-Logo-Symbol-Dark.svg b/v2/assets/site/logos/Livepeer-Logo-Symbol-Dark.svg
new file mode 100644
index 00000000..f50505a2
--- /dev/null
+++ b/v2/assets/site/logos/Livepeer-Logo-Symbol-Dark.svg
@@ -0,0 +1,3 @@
+
diff --git a/v2/assets/site/logos/Livepeer-Logo-Symbol-Light.svg b/v2/assets/site/logos/Livepeer-Logo-Symbol-Light.svg
new file mode 100644
index 00000000..3ea275c4
--- /dev/null
+++ b/v2/assets/site/logos/Livepeer-Logo-Symbol-Light.svg
@@ -0,0 +1,3 @@
+
diff --git a/v2/assets/technical/Architecture_go-livepeer_DeepWiki.htm b/v2/assets/technical/Architecture_go-livepeer_DeepWiki.htm
new file mode 100644
index 00000000..7507b65e
--- /dev/null
+++ b/v2/assets/technical/Architecture_go-livepeer_DeepWiki.htm
@@ -0,0 +1,2915 @@
+
+
+Architecture | livepeer/go-livepeer | DeepWiki
This page provides an overview of the Livepeer node architecture, explaining the key components and their interactions within the go-livepeer codebase. The document focuses on the internal software architecture of Livepeer nodes and how they communicate with each other in the network. For information about the overall Livepeer protocol design, see the Overview page.
+
Core Components
+
Livepeer consists of several key node types that work together to form a decentralized video processing network. The following diagram illustrates the high-level architecture and interactions between these components:
The large number of configuration options allows for flexible deployment models, from simple single-node setups to complex distributed architectures.
+
Summary
+
The Livepeer architecture is designed around a distributed system of nodes with specialized responsibilities. The broadcaster ingests and segments video, the orchestrator manages transcoding jobs, the transcoder performs the actual video processing, and the redeemer handles payment ticket redemption. These components work together to provide a decentralized video streaming platform with economic incentives for participants.
\ No newline at end of file
diff --git a/v2/assets/technical/DeepWiki_TA-Flows.htm b/v2/assets/technical/DeepWiki_TA-Flows.htm
new file mode 100644
index 00000000..9f921ee8
--- /dev/null
+++ b/v2/assets/technical/DeepWiki_TA-Flows.htm
@@ -0,0 +1,2997 @@
+
+
+livepeer/go-livepeer | DeepWiki
This page provides a comprehensive introduction to the go-livepeer repository, which implements the Livepeer protocol - a decentralized video streaming network with crypto-token incentives. The go-livepeer codebase enables running various node types that form the Livepeer network ecosystem.
+
Purpose and Scope
+
Go-livepeer implements a live video-streaming network protocol that is fully decentralized, highly scalable, and crypto-token incentivized. The scope of this repository includes:
+
+
Implementation of all Livepeer network node types (Broadcaster/Gateway, Orchestrator, Transcoder, Redeemer, AI Worker)
+
Video ingest via RTMP and HTTP push protocols
+
Video segmentation, transcoding, and delivery
+
Probabilistic micropayment system for compensating network participants
+
Ethereum blockchain integration for staking, rewards, and payments
The Livepeer network consists of several node types, each with specific responsibilities:
+
+
+
Broadcaster/Gateway Node: Acts as the entry point for video streams, handling video ingest, segmentation, and distribution to Orchestrators. Also serves transcoded content to viewers via HLS.
+
+
+
Orchestrator Node: Coordinates the transcoding process, receiving segmented video from Broadcasters, selecting appropriate Transcoders, verifying results, and managing payments.
+
+
+
Transcoder Node: Performs the actual video transcoding work, converting video segments to different formats and resolutions.
+
+
+
Redeemer Node: Specialized service that handles redeeming winning payment tickets on the Ethereum blockchain.
+
+
+
AI Worker Node: Performs AI-based media processing, extending Livepeer's capabilities beyond traditional video transcoding.
The go-livepeer codebase is organized around several key components:
+
+
LivepeerNode
+
The LivepeerNode struct defined in core/livepeernode.go112-165 is the central component that can operate as different node types based on configuration. It contains fields and methods common to all node types, as well as type-specific components.
+
type LivepeerNode struct {
+// Common fields
+ Eth eth.LivepeerEthClient
+ WorkDir string
+ NodeType NodeType
+ Database *common.DB
+
+// Node-specific fields
+ Sender pm.Sender // For Broadcaster
+ Transcoder Transcoder // For Transcoder
+ TranscoderManager *RemoteTranscoderManager // For Orchestrator
+ OrchestratorPool common.OrchestratorPool // For Broadcaster
+// ... other fields
+}
The video processing pipeline in go-livepeer involves several stages:
+
+
+
Ingest: Video is ingested via RTMP (gotRTMPStreamHandler) or HTTP push (HandlePush) in server/mediaserver.go395-459
+
+
+
Segmentation: The continuous video stream is segmented into discrete chunks using the RTMP segmenter or processed directly from HTTP push
+
+
+
Session Management: The BroadcastSessionsManager selects appropriate Orchestrators using a selection algorithm based on price, performance, and reputation
+
+
+
Transcoding: Selected Orchestrators receive video segments along with payment tickets, then assign transcoding work to Transcoders
+
+
+
Verification: Orchestrators optionally verify transcoded results using fast verification techniques to ensure quality and accuracy
+
+
+
Delivery: Transcoded segments are returned to the Broadcaster, inserted into HLS playlists, and made available for playback
Go-livepeer implements a probabilistic micropayment system to enable efficient off-chain payments with minimal on-chain transactions:
+
+
+
Ticket Creation: The Broadcaster creates payment tickets with a low probability of winning but high face value
+
+
+
Ticket Submission: Tickets are attached to video segments and sent to Orchestrators
+
+
+
Ticket Validation: Orchestrators validate tickets and identify winners
+
+
+
Ticket Redemption: Winning tickets (a small percentage) are sent to the Redeemer service, which redeems them on-chain
+
+
+
Max Float Management: The system manages "max float" values, which represent the maximum amount an Orchestrator can claim from a Broadcaster
+
+
+
This approach allows for many "payment attempts" to be made off-chain, with only winning tickets requiring on-chain processing, dramatically reducing gas costs and increasing scalability.
The node can be started with the appropriate combination of flags based on the desired node type and configuration.
+
Conclusion
+
Go-livepeer implements a comprehensive decentralized video processing network with specialized node types working together to provide transcoding services. This overview has covered the main components, architectural patterns, and key systems. Additional details on specific aspects can be found in the other wiki pages.
\ No newline at end of file
diff --git a/v2/assets/technical/protocol-overview.html b/v2/assets/technical/protocol-overview.html
new file mode 100644
index 00000000..559491da
--- /dev/null
+++ b/v2/assets/technical/protocol-overview.html
@@ -0,0 +1,106 @@
+
+
+
Application error: a client-side exception has occurred while loading localhost (see the browser console for more information).
+
+### Recent Discord Conversations
+
+
+
+
diff --git a/v2/pages/00_home/home/livepeer-tl-dr.mdx b/v2/pages/00_home/home/livepeer-tl-dr.mdx
new file mode 100644
index 00000000..9083f1e6
--- /dev/null
+++ b/v2/pages/00_home/home/livepeer-tl-dr.mdx
@@ -0,0 +1,101 @@
+---
+title: 'Livepeer TL;DR'
+description: '2 minute overview of Livepeer'
+sidebarTitle: 'Livepeer TL;DR'
+og:image: '../../images/home/Eric Shreck Gif.gif'
+---
+
+import { url, title, caption, embedUrl } from '/snippets/variables.mdx'
+import { tldrTitles, tldrList } from '/snippets/variables/home.mdx'
+import {
+ YouTubeVideo,
+ YouTubeVideoDownload,
+ CardVideo,
+} from '/snippets/components/video.jsx'
+import {
+ GotoLink,
+ GotoCard,
+ DownloadLink,
+} from '/snippets/components/links.jsx'
+import { Image } from '/snippets/components/image.jsx'
+import {
+ StepList,
+ StepLinkList,
+ UpdateList,
+ UpdateLinkList,
+ IconList,
+ BasicList,
+} from '/snippets/components/lists.jsx'
+
+Livepeer is an inclusive and welcoming global community with a diverse and talented group of people.
+
+From DJs, creators, developers, founders, network contributors and enterprise clients — it takes a village to build a cutting-edge open video streaming & AI platform!
+
+Get started on your journey by reading about Livepeer and joining the community on Discord to get involved.
+
+
+
+
+
+
+
+## Livepeer Video Overview
+
+Watch Co-Founder & CTO Doug Petkanics talk about Livepeer for a quick primer on
+its Video & AI capabilities and how Livepeer is transforming real-time video AI.
+Explore the future of live video with Doug Petkanics, founder of Livepeer.
+
+
+
+In this episode of "Pitch, Build, Scale", Doug shares his journey from early startups to building Livepeer’s decentralized video infrastructure, which slashes streaming costs and empowers developers to escape cloud monopolies.
+
+We dig into Daydream, Livepeer’s real-time AI video tool that transforms livestreams on the fly with text prompts, and why decentralized compute is key to innovation.
+
+Doug reveals:
+The economics of live video and how decentralization changes the game.
+Why Daydream’s real-time AI transforms creative workflows.
+How regulatory fears threaten AI progress—and how decentralization preserves open innovation.
+The grand experiment of building a community-owned video infrastructure network.
+
+
+
+
+
+## Why Livepeer?
+
+Livepeer offers a decentralised, open-source platform for video streaming and AI that dramatically reduces costs by utilising idle compute resources.
+
+It provides:
+
+- **Transparency** via blockchain verification
+- **Scalability** for high-demand workloads
+- **AI integration** and modular machine-learning pipelines
+- **Developer tools** for fast innovation
+- **Earnings** for GPU operators and LPT holders
+
+By empowering a distributed ecosystem, Livepeer disrupts traditional centralised streaming platforms.
+
+
+
+
+
+## What You Can Do On Livepeer
+
+Here's a quick breakdown of what you can accomplish with Livepeer:
+
+
diff --git a/v2/pages/00_home/home/trending-at-livepeer.mdx b/v2/pages/00_home/home/trending-at-livepeer.mdx
new file mode 100644
index 00000000..3c8e26fb
--- /dev/null
+++ b/v2/pages/00_home/home/trending-at-livepeer.mdx
@@ -0,0 +1,172 @@
+---
+title: 'Trending Topics'
+sidebarTitle: 'Trending Topics'
+---
+
+## Trending
+
+import { YouTubeVideo } from '/snippets/components/video.jsx'
+
+
+ Use automation & AI to aggregate latest Livepeer product drops, guides and
+ discord/forum questions
+
+
+
+ will pull in the latest youtube videos via an automation & automatically
+ pre-fill 5 cards
+
+
+#### Eric Tang | Live in Lisbon
+
+
+
+
+
+
+
+
+
+
+#### Live in Lisbon Livepeer Summit 2025 Recap
+
+October 2025, something special happened in the heart of Portugal: builders, core contributors, and ecosystem visionaries came together for two action-packed days dedicated to moving the Livepeer network forward.
+
+## :download: [Transcript](https://download.com)
+
+#### Watercooler Chat | November 24 2025
+
+
+
+:link: Link?
+
+:download: [Transcript](https://download.com)
+
+---
+
+#### Livepeer Fireside | November 12 2025
+
+
+
+:download: [Transcript](https://download.com)
+
+---
+
+### Latest on Twitter
+
+
+Generate a static Twitter oEmbed screenshot and link to the tweet -> another automation
+
+
+
+
+### Recent Blogs
+
+
+ Links to latest articles
+ [https://blog.livepeer.org/](https://blog.livepeer.org/) Pull in images and
+ title to the card section
+
+
+
+
+
+
+### Recent Discord Conversations
+
+
+
+
diff --git a/v2/pages/00_home/home/trending-layout-tests.mdx b/v2/pages/00_home/home/trending-layout-tests.mdx
new file mode 100644
index 00000000..af8a3d36
--- /dev/null
+++ b/v2/pages/00_home/home/trending-layout-tests.mdx
@@ -0,0 +1,86 @@
+---
+title: 'Test Automations'
+sidebarTitle: 'Test Automations'
+---
+
+ WIP: Testing n8n automations
+
+import { PostCard, CardColumnsPostLayout } from '/snippets/components/cards.jsx'
+import { forumData } from '/snippets/automationData/forum/forumData.jsx'
+
+Automation that links the latest forum posts
+
+## Latest Forum Topics [Cards in Card]
+
+
+
+
+
+## Latest Forum Topics [Just Cards. 2 col layout]
+
+
+
+
+
+
+
+
+
+## Latest Forum Topics [Truncated MDX ONLY]
+
+### [It's time to ACT! Accumulation & the Treasury Ceiling](https://forum.livepeer.org/t/3153)
+
+_By b3nnn (@b3nnn)_
+
+The onchain treasury was designed to provide sustainable public goods funding. It has supported many important and strategic contributions to the Livepeer Ecosystem. The AI SPE, Streamplace, Agent SPE and Cloud have all received funds and made important contributions.
+
+The treasury is key to supporting strategic investments to improve UX for stakeholders, effectively manage protocol security, and fund other capital and resource needs for this exciting phase of the project.
+
+As of now, the onchain treasury is currently not accumulating LPT. I intend to post a LIP to turn on the treasury rewards again at their initial values:
+
+- `treasuryRewardCutRate`: 10%
+- `treasuryBalanceCeiling`: 750000 LPT
+
+---
+
+### [Pre-proposal: IDOL - Improving Dex / Onchain Liquidity](https://forum.livepeer.org/t/3151)
+
+_By b3nnn (@b3nnn)_
+
+**TLDR**
+
+We propose to address known UX issues and ease and costs to participate by increasing DEX liquidity. Arrakis offers an optimal solution for our specific needs, and we are requesting 250,000 LPT for deployment to a Uniswap v4 pool which will significantly reduce slippage for ecosystem participants.
+
+**The Ask**
+
+We are asking for 250,000 LPT (approx. $1M in USD value) to be held in a multisig controlled by the Livepeer Foundation, to be deployed via an onchain vault with Arrakis as a concentrated pool on Uniswap v4.
+
+Management of concentrated liquidity on Uniswap V4 allows for larger trades with minimal price impact, improving the overall trading experience.
+
+---
+
+### [Transformation SPE Release Notes](https://forum.livepeer.org/t/3142)
+
+_By Mehrdad (@Mehrdad)_
+
+Release notes are a way to share work being completed by the Transformation SPE and its various contributors.
+
+---
+
+### [Transcoder Campaign: organic-node.eth](https://forum.livepeer.org/t/1970)
+
+_By Ron (@ron)_
+
+Hello fellow video enthusiast and web3 supporters,
+
+Thanks for your time in reading my post. (organic-node.eth) Node has been active for about 6 months and everyday has been a great learning experience. My node has been highly reliable with 4 Orchestrators across the globe.
+
+Stake here: **organic-node.eth**
diff --git a/v2/pages/00_home/project-showcase/industry-verticals.mdx b/v2/pages/00_home/project-showcase/industry-verticals.mdx
new file mode 100644
index 00000000..6d0d0d05
--- /dev/null
+++ b/v2/pages/00_home/project-showcase/industry-verticals.mdx
@@ -0,0 +1,103 @@
+---
+title: 'Industry Applications'
+sidebartitle: 'Industry Applications'
+---
+
+Video is integral to the success of many of the applications we use daily.
+
+ Example Copy Only.. still todo
+### Livepeer Domains
+
+-> The verticals livepeer works for
+
+Livepeer is built for everyone.
+
+
+
+## **Products that wouldn’t exist without video**
+
+
+
+
+
+
+
+
+
+
+
+ TikTok
+
+
Short-form social video sharing
+
+
+
+ Twitch (live game streaming)
+
+
+
+
+
+ Zoom (real-time video conferencing)
+
+
+
+
+
+
+1. **TikTok** (short-form social video sharing)
+2. **Zoom** (real-time video conferencing)
+3. **Twitch** (live game streaming)
+4. **YouTube** (open video hosting + creator monetisation)
+5. **FaceTime/Google Meet** (consumer video calling)
+6. **Peloton** (live video-driven fitness classes)
+7. **Ring/Nest Cam** (real-time camera security)
+8. **Telehealth apps** (video-first remote medical consultations)
+9. **Online education platforms** like Coursera/Udacity (video-based learning)
+10. **Virtual events platforms** (Devcon/ETH CC streaming, powered by infrastructures like Livepeer)
+
+### **Verticals where video is now essential**
+
+1. **Social media** — video posts, livestreams, creator economy apps.
+2. **Events & conferences -** hybrid attendance, global livestreaming.
+3. **Creators & entertainment** — podcasts, tutorials, livestream shows.
+4. **Education** — recorded lectures, interactive classrooms.
+5. **Gaming & esports** — live game broadcasts and VOD clips.
+6. **E-commerce** — product demos, livestream shopping.
+7. **Health & telemedicine** — remote care via video consults.
+8. **Security & monitoring** — real-time camera feeds, analytics.
+9. **Work & collaboration** — remote meetings, async video updates.
+10. **AI-generated media** — generative video, captions, upscaling.
+
+- **Social Media**
+ - Video posts
+ - Livestreams
+ - Creator economy apps
+- **Events & Conferences**
+ - Hybrid attendance
+ - Global livestreaming
+- **Creators & Entertainment**
+ - Podcasts
+ - Tutorials
+ - Livestream shows
+- **Education**
+ - Recorded lectures
+ - Interactive classrooms
+- **Gaming & Esports**
+ - Live game broadcasts
+ - VOD clips
+- **E-commerce**
+ - Product demos
+ - Livestream shopping
+- **Health & Telemedicine**
+ - Remote care via video consults
+- **Security & Monitoring**
+ - Real-time camera feeds
+ - Analytics
+- **Work & Collaboration**
+ - Remote meetings
+ - Async video updates
+- **AI-generated Media**
+ - Generative video
+ - Captions
+ - Upscaling
diff --git a/v2/pages/00_home/project-showcase/livepeer-applications.mdx b/v2/pages/00_home/project-showcase/livepeer-applications.mdx
new file mode 100644
index 00000000..c1e24491
--- /dev/null
+++ b/v2/pages/00_home/project-showcase/livepeer-applications.mdx
@@ -0,0 +1,7 @@
+---
+title: 'Livepeer Applications'
+sidebarTitle: 'Livepeer Applications'
+description: 'A showcase of real-world applications for Livepeer'
+---
+
+Coming Soon
diff --git a/v2/pages/00_home/project-showcase/projects-built-on-livepeer.mdx b/v2/pages/00_home/project-showcase/projects-built-on-livepeer.mdx
new file mode 100644
index 00000000..792268d5
--- /dev/null
+++ b/v2/pages/00_home/project-showcase/projects-built-on-livepeer.mdx
@@ -0,0 +1,31 @@
+---
+title: 'Projects Built on Livepeer'
+sidebarTitle: 'Built on Livepeer'
+description: "A collection of ecosystem projects using Livepeer - Be inspired!"
+---
+
+Livepeer creates an open, competitive marketplace for reliable, low-cost video streaming and AI pipelines.
+
+Tokenisation (using crypto payment rails) enables monetisation for network participants & provides a payment mechanism for the creator economy
+
+
+ Insert Card Layout here & enable an automation for users to add projects via a
+ form
+
+
+### Creators
+
+MetaDJ -> [https://www.instagram.com/reel/DPd6RUsErGF/](https://www.instagram.com/reel/DPd6RUsErGF/)
+
+### Events
+
+- ETH Community events (find out which)
+
+### Social Good
+
+- Streaming in prisons
+
+### Social Media
+
+- Lens
+- Bluesky
diff --git a/v2/pages/00_home/tab-index.mdx b/v2/pages/00_home/tab-index.mdx
new file mode 100644
index 00000000..c929d939
--- /dev/null
+++ b/v2/pages/00_home/tab-index.mdx
@@ -0,0 +1,38 @@
+# Table of contents
+
+## Home
+
+* [Welcome to the Livepeer Doc's!](README.md)
+* [Livepeer TL;DR](home/livepeer-tl-dr.md)
+* [Trending at Livepeer](home/trending-at-livepeer.md)
+
+## Documentation Guide
+
+* [Documentation Overview](documentation-guide/documentation-overview.md)
+* [Documentation Guide](documentation-guide/documentation-guide.md)
+* [Doc's Features & AI Integrations](documentation-guide/docs-features-and-ai-integrations.md)
+* [Contribute to the Doc's](documentation-guide/contribute-to-the-docs.md)
+
+## Get Started
+
+* [Use Livepeer](get-started/use-livepeer.md)
+* [Stream Video (quickstart)](get-started/stream-video-quickstart.md)
+* [Livepeer AI (quickstart)](get-started/livepeer-ai-quickstart.md)
+
+## Changelog
+
+* [Page 1](changelog/page-1.md)
+
+## Reference
+
+* [FAQ](reference/faq.md)
+* [Livepeer Terminology & Definitions](reference/livepeer-terminology-and-definitions.md)
+* [Resource Index](reference/resource-index.md)
+
+## Contact & Support
+
+* [Get Help](contact-and-support/get-help.md)
+
+## Documentation Versions
+
+* [v1](documentation-versions/v1.md)
diff --git a/v2/pages/01_about/about-livepeer/livepeer-ecosystem.mdx b/v2/pages/01_about/about-livepeer/livepeer-ecosystem.mdx
new file mode 100644
index 00000000..96aed92d
--- /dev/null
+++ b/v2/pages/01_about/about-livepeer/livepeer-ecosystem.mdx
@@ -0,0 +1,163 @@
+---
+title: 'Livepeer Ecosystem'
+sidebarTitle: 'Livepeer Ecosystem'
+description: "Livepeer has grown into a robust network over 8 years. Here's your guide to finding who you need and what the ecosystem offers!"
+---
+
+### Overview
+
+This page serves as a guide to understanding Livepeer's Organisational Structure & Plans
+
+- Livepeer Inc.
+ - Core Teams & Function
+- Livepeer Foundation
+ - Core Teams & Function
+- Livepeer Network
+ - gateways, orchestrators, delegators
+- Livepeer Ecosystem Projects
+ - use livepeer: daydream etc.
+- Livepeer Partner Companies
+ - Do more with Livepeer with our partners -> storage, security etc.
+- Livepeer Enterprise
+
+
+
+### Livepeer Ecosystem
+
+ Mermaid Embedded Fowchart Example Only
+```mermaid
+flowchart TB
+ A[Livepeer Inc.]:::main --> B[Livepeer Foundation]:::main
+ A --> C[Livepeer Network]:::main
+ A --> D[Livepeer Ecosystem Projects]:::main
+ A --> E[Livepeer Partner Companies]:::main
+ A --> F[Livepeer Enterprise]:::main
+
+classDef main fill:#197a4d,stroke:#15803D,stroke-width:2px,color:#fff
+
+````
+
+### Livepeer Inc.
+
+```mermaid
+flowchart TD
+ subgraph Inc["Livepeer Inc."]
+ B1[AI SPE]
+ B2[Cloud SPE]
+ end
+ style Inc fill:#197a4d,stroke:#15803D,stroke-width:2px,color:#fff
+ style B1 fill:#07C983,stroke:#197a4d,color:#000
+ style B2 fill:#07C983,stroke:#197a4d,color:#000
+````
+
+### Livepeer Foundation
+
+```mermaid
+flowchart TD
+ subgraph Foundation["Livepeer Foundation"]
+ C1[Strategic Objectives]
+ C2[Initiatives]
+ C3[Task Forces]
+ C4[Operations]
+ end
+ style Foundation fill:#197a4d,stroke:#15803D,stroke-width:2px,color:#fff
+ style C1 fill:#07C983,stroke:#197a4d,color:#000
+ style C2 fill:#07C983,stroke:#197a4d,color:#000
+ style C3 fill:#07C983,stroke:#197a4d,color:#000
+ style C4 fill:#07C983,stroke:#197a4d,color:#000
+```
+
+### Livepeer Network
+
+```mermaid
+flowchart TD
+ subgraph Network["Livepeer Network"]
+ D1[Gateways]
+ D2[Orchestrators]
+ D3[Delegators]
+ D4[Storage]
+ end
+ style Network fill:#197a4d,stroke:#15803D,stroke-width:2px,color:#fff
+ style D1 fill:#07C983,stroke:#197a4d,color:#000
+ style D2 fill:#07C983,stroke:#197a4d,color:#000
+ style D3 fill:#07C983,stroke:#197a4d,color:#000
+ style D4 fill:#07C983,stroke:#197a4d,color:#000
+```
+
+### Livepeer Ecosystem Projects
+
+```mermaid
+flowchart TD
+ subgraph EcoProjects["Livepeer Ecosystem Projects"]
+ E1[Daydream]
+ E2[Other Projects]
+ end
+ style EcoProjects fill:#197a4d,stroke:#15803D,stroke-width:2px,color:#fff
+ style E1 fill:#07C983,stroke:#197a4d,color:#000
+ style E2 fill:#07C983,stroke:#197a4d,color:#000
+```
+
+### Livepeer Partner Companies
+
+```mermaid
+flowchart TD
+ subgraph Partners["Livepeer Partner Companies"]
+ F1[Storage Partners]
+ F2[Security Partners]
+ end
+ style Partners fill:#197a4d,stroke:#15803D,stroke-width:2px,color:#fff
+ style F1 fill:#07C983,stroke:#197a4d,color:#000
+ style F2 fill:#07C983,stroke:#197a4d,color:#000
+```
+
+### Livepeer Enterprise
+
+```mermaid
+flowchart TD
+ subgraph Enterprise["Livepeer Enterprise"]
+ G1[Enterprise Services]
+ end
+ style Enterprise fill:#197a4d,stroke:#15803D,stroke-width:2px,color:#fff
+ style G1 fill:#07C983,stroke:#197a4d,color:#000
+```
+
+### Livepeer Inc.
+
+- AI SPE
+- Cloud SPE
+
+### Livepeer Foundation
+
+The [Livepeer Foundation](https://forum.livepeer.org/t/launching-the-livepeer-foundation/2849) was launched in April 2025 with the mission:
+
+> \[...] to steward the long-term vision, ecosystem growth, and core development of the network.
+
+Broadly speaking, the Livepeer Foundation makes decisions in the following areas:
+
+1. Define strategic objectives for Livepeer
+2. Design initiatives to accelerate or steer progress towards objectives
+3. Drawing on available resources, recruit and coordinate task forces to execute on initiatives
+4. Foundation operations
+
+### Livepeer Network
+
+-
+- Storage
+-
+
+
+### Livepeer Ecosystem Projects
+
+
+
+### Livepeer Partner Companies
+
+
+
+### Decentralising Livepeer
+
+
+
+# Livepeer Ecosystem
+
+ Set up a github for self-registering as an ecosystem project
diff --git a/v2/pages/01_about/about-livepeer/livepeer-evolution.mdx b/v2/pages/01_about/about-livepeer/livepeer-evolution.mdx
new file mode 100644
index 00000000..6cd6ce9d
--- /dev/null
+++ b/v2/pages/01_about/about-livepeer/livepeer-evolution.mdx
@@ -0,0 +1,30 @@
+---
+title: 'Livpeer Evolution'
+sidebarTitle: 'Livepeer Evolution'
+---
+
+
+ Might want to create upgradeable version or link to a github sourch of truth.
+ Example Layout only here
+
+
+
+## Livepeer Evolution
+...From founding to current to future
+What's shaped Livepeer & What does the future look like
+
+
+### Key Achievements
+
+
+ Founded
+ More info
+ .... ....
+ PMF
+
+
+
+## Future of Livepeer
+Roadmap Milestones would be good & invite community to build the future with us / takes a village ...
+
+... image quote here -> the future is what we create today ..
\ No newline at end of file
diff --git a/v2/pages/01_about/about-livepeer/livepeer-overview.mdx b/v2/pages/01_about/about-livepeer/livepeer-overview.mdx
new file mode 100644
index 00000000..ae961806
--- /dev/null
+++ b/v2/pages/01_about/about-livepeer/livepeer-overview.mdx
@@ -0,0 +1,61 @@
+---
+title: 'Livepeer Overview'
+sidebarTitle: 'Livepeer Overview'
+description: 'A brief overview of Livepeer and its mission.'
+---
+
+import { YouTubeVideo } from '/snippets/components/video.jsx'
+import { Image } from '/snippets/components/image.jsx'
+import { GotoLink, GotoCard } from '/snippets/components/links.jsx'
+
+
+
+
+ This page is a work in progress.
+ TODO: Copy Edits
+
+
+# Livepeer Overview
+Livepeer is a full-stack platform for video streaming & AI. The video streaming software is underpinned by a network of actors that perform the work needed to compute, transcode & orchestrate video & AI jobs in the Livepeer network.
+
+{/* # Livepeer Founders
+Livepeer was founded by Doug Petkanics (CTO) and Eric Tang (CEO) in 2017.
+ Insert intro's here */}
+
+# Livepeer Story
+Livepeer was [founded](https://medium.com/livepeer-blog/the-livepeer-development-stack-technology-behind-live-streaming-built-on-ethereum-d6a06158d5e2) in 2017 by Doug Petkanics (CTO) and Eric Tang (CEO). The duo aimed to build a scalable, secure, and cost-effective alternative to centralised broadcasting services. Livepeer’s end goal is to [serve](https://medium.com/livepeer-blog/livepeer-for-beginners-3b49945c24a7?source=collection_home---------163----------------------------) as the infrastructure service layer for decentralised streaming. & AI, [making](https://livepeer.org/primer) video streaming more reliable and affordable, & AI more accessible.
+
+
+
+
+
+# Livepeer Vision
+The vision for Livepeer is to evolve from decentralized video infrastructure to become the open GPU network that powers real-time AI and world models, establishing itself as the AI infrastructure layer for an interactive, intelligent world.Core Pillars & Messaging
+
+
+
+## Core Mission
+
+The network's strategy is built upon a foundation of core value propositions and messaging pillars:
+
+- **Core Pillars**
+ - **Real-time Performance / Performance at Scale:** Industry-standard low latency optimized for real-time video AI and media, enabling sub-second inference and proven scalability.
+ - **Cost Efficiency:** Access to GPU compute at 5–10x lower cost through an open marketplace with transparent on-chain economics and a pay-per-use model.
+ - **Automagic Scalability:** The ability to scale capacity up or down dynamically in real-time via an elastic network supply, smart routing, and incentivized idle GPU utilization.
+ - **Openness & Community:** Permissionless, open-source, community-driven infrastructure that provides global access, on-chain verifiable compute, and rewards all participants.
+
+ NOTES ONLY BELOW HERE
+
+- **Brand Essence & Messaging**
+- **Brand Essence:** “Open video infrastructure for the AI-powered internet.”
+- **Tagline/Slogan:** “Powering open video for the AI era.”
+- **Key Messages:** The brand emphasizes a confident, clear, mission-driven, and builder-first tone with example language like: “Build real-time AI that runs at the speed of thought.” and “Compute without compromise.”
+
diff --git a/v2/pages/01_about/about-livepeer/why-livepeer.mdx b/v2/pages/01_about/about-livepeer/why-livepeer.mdx
new file mode 100644
index 00000000..ddf48ee6
--- /dev/null
+++ b/v2/pages/01_about/about-livepeer/why-livepeer.mdx
@@ -0,0 +1,20 @@
+---
+title: 'Why Livepeer'
+sidebarTitle: 'Why Livepeer'
+---
+
+## Livepeer Offers
+
+- On-demand, open-access, real-time video broadcasting at a fraction of the price of cloud equivalents
+- On-demand, open-access AI pipelines
+
+## Livepeer Advantages
+
+- 60% cheaper than cloud for video broadcasting
+- Built-in redundancy & network resilience (thanks to a distributed open access compute)
+- Lower latency (thanks to global distributed nodes - your neighbour might be running the compute you're using!)
+- On-demand pricing - only pay for what you use - forever.
+- Open Software (forever - developers can rest easy knowing their businesses will never be at risk of APIs getting closed-sourced)
+- Verifiable and auditable jobs (which AI loves)
+- Permissionless, open network - you don't need to talk to sales to try it out or join the innvoation economy
+-
diff --git a/v2/pages/01_about/faq-about.mdx b/v2/pages/01_about/faq-about.mdx
new file mode 100644
index 00000000..489d09e0
--- /dev/null
+++ b/v2/pages/01_about/faq-about.mdx
@@ -0,0 +1,22 @@
+---
+title: 'FAQ'
+sidebarTitle: 'FAQ'
+description: 'Frequently Asked Questions'
+---
+
+Roadmap: https://roadmap.livepeer.org/roadmap
+
+
+# FAQ
+
+Coming Soon
+
+Concepts:
+Protocol vs Network
+Protocol: Rules that govern actor coordination & incentives to optimise for desired behaviours (ie performing work) and disincentivise harmful actions (ie. false work)
+Most protocols take the philosophy of self-interested parties acting in their own best interests. This is often called game theory in web3.
+
+
+Technical Architecture:
+Diagram - interactions & flows between actors
+
diff --git a/v2/pages/01_about/livepeer-network/actor-overview.mdx b/v2/pages/01_about/livepeer-network/actor-overview.mdx
new file mode 100644
index 00000000..36068e06
--- /dev/null
+++ b/v2/pages/01_about/livepeer-network/actor-overview.mdx
@@ -0,0 +1,136 @@
+---
+title: 'Actors Overview'
+sidebarTitle: 'Actors Overview'
+description: 'An overview of the Livepeer protocol actors.'
+---
+
+import { GotoCard } from '/snippets/components/links.jsx'
+
+Actors are the main participants in the protocol who make up the core functions of the network.
+
+Explainer here...
+
+## Key Concepts & Definitions
+**Developer**
+
+A developer is anyone building with Livepeer, usually via hosted services.
+They only become gateway operators if they need direct protocol access.
+
+Developers may build on top of the protocol, but most will use hosted services,
+not run infrastructure.
+
+Only developers who want full protocol-level access will choose to run a gateway node.
+
+Developer Journey Examples
+
table or diagram
+
+**Gateway Operator / Gateway**
+
+A gateway is a Livepeer node run by an operator—not a hosted product.
+Running a gateway = interacting directly with the protocol.
+
+Gateway Developer Journey Examples
+
+
+
+
+Together, they form the backbone of the Livepeer AI video pipeline.
+
+```mermaid
+sequenceDiagram
+ participant App as Application
+ participant GW as Gateway
+ participant ORC as Orchestrator
+
+ App->>GW: Submit job (model, parameters, video frames)
+ GW->>ORC: Route job to best GPU
+ ORC->>GW: Return processed frames/output
+ GW->>App: Send results back to user
+```
+
+
+
+| Role | Function | Performs GPU Work? | External-Facing? |
+| ---------------- | ---------------------------------------------- | ------------------ | ---------------- |
+| **Gateway** | Job intake, pricing, routing, capability match | ❌ No | ✅ Yes |
+| **Orchestrator** | GPU compute, inference, transcoding, BYOC | ✅ Yes | ❌ No |
+
+
+## Gateway Responsibilities
+
+Gateways act as the front door to the network:
+
+- Receive jobs from applications
+- Determine required model, pipeline, or GPU
+- Select the best orchestrator based on performance and pricing
+- Route the workload with low latency
+- Return results to the client
+- Publish marketplace offerings (models, pipelines, cost per frame, etc.)
+
+Gateways provide _service intelligence_, not compute.
+
+---
+
+## Orchestrator Responsibilities
+
+Orchestrators are GPU operators who run:
+
+- Real-time AI inference
+- Daydream / ComfyStream pipelines
+- BYOC containers
+- Traditional transcoding
+
+They provide:
+
+- GPU horsepower
+- Model execution
+- Deterministic and verifiable output
+- Performance guarantees
+
+They do not expose external APIs directly—Gateways handle that.
+
diff --git a/v2/pages/01_about/livepeer-network/livepeer-actors/delegators.mdx b/v2/pages/01_about/livepeer-network/livepeer-actors/delegators.mdx
new file mode 100644
index 00000000..f6dce745
--- /dev/null
+++ b/v2/pages/01_about/livepeer-network/livepeer-actors/delegators.mdx
@@ -0,0 +1,14 @@
+# Delegators
+
+How to Delegate Livepeer Tokens (LPT) on the Livepeer Network
+https://www.youtube.com/watch?v=fWKwmGoWa2g&t=205s
+
+Livepeer token holders receive ETH and LPT for delegating their tokens on the Livepeer network. Here is a quick walkthrough on how to delegate LPT using the Livepeer Explorer (explorer.livepeer.org).
+
+00:00 Introduction
+00:12 Connect wallet
+00:40 Bridge to Arbitrum
+01:15 Move LPT & ETH to layer 2
+03:25 Connect to Livepeer Explorer
+04:12 Pick an orchestrator
+05:11 Review & delegate
diff --git a/v2/pages/01_about/livepeer-network/livepeer-actors/end-users.mdx b/v2/pages/01_about/livepeer-network/livepeer-actors/end-users.mdx
new file mode 100644
index 00000000..028129a1
--- /dev/null
+++ b/v2/pages/01_about/livepeer-network/livepeer-actors/end-users.mdx
@@ -0,0 +1,4 @@
+
+
+# End Users
+
diff --git a/v2/pages/01_about/livepeer-network/livepeer-actors/gateways.mdx b/v2/pages/01_about/livepeer-network/livepeer-actors/gateways.mdx
new file mode 100644
index 00000000..f22be018
--- /dev/null
+++ b/v2/pages/01_about/livepeer-network/livepeer-actors/gateways.mdx
@@ -0,0 +1,442 @@
+---
+title: 'Gateways'
+sidebarTitle: 'Gateways'
+---
+
+ Review and Edit Page
+
+ Diagram of actors here
+
+### About Gateways
+
+Gateways are Livepeer’s off-chain coordination layer: the nodes that applications connect to in order to submit real-time AI and video compute jobs.
+
+Instead of talking directly to orchestrators, apps send workloads to a Gateway, which handles service discovery, capability matching, pricing, and low-latency routing.
+
+The Gateway selects the best orchestrator (GPU compute node) based on GPU capacity, model support, performance, and availability, ensuring efficient execution of AI inference, transcoding, and BYOC pipelines.
+
+Gateways expose their offered services and enable a competitive
+marketplace while orchestrators focus solely on GPU compute - running the job!
+
+Put simply:
+applications → Gateways → orchestrators → results!
+
+Gateways are off-chain service nodes that sit between applications and orchestrators. They provide the entry point for real workloads (AI inference, transcoding, BYOC containers) to reach the decentralized GPU network.
+
+### Gateway Workflow
+
+
+ (Daydream, ComfyUI, StreamDiffusionTD, BYOC Pipelines)"]
+ B["Gateway - Job Intake - Pricing - Capability Match - Routing"]
+ C["Orchestrator - GPU Execution - Transcoding - AI Inference - BYOC Containers"]
+ D["Application Receives Output"]
+
+ A -->|API Call| B
+ B -->|Dispatch Job| C
+ C -->|Results| D
+
+`} />
+
+
+
+### Gateway Services
+
+- Accept jobs
+- Match to orchestrators
+- Expose capabilities, pricing, model support
+- Enable a marketplace
+- Provide APIs (for Daydream, BYOC, ComfyStream, StreamDiffusionTD)
+
+Without gateways, developers would need to directly manage GPU node discovery, pricing, and routing — which defeats the purpose of a decentralized compute network
+
+
+From -> https://github.com/videoDAC/livepeer-gateway?tab=readme-ov-file
+
+They are not block producers, not orchestrators, and not on-chain components.
+They are an infrastructure role that apps connect to for low-latency coordination.
+
+### Why Gateways Exist
+
+Across the transcripts and ecosystem discussions, gateways consistently appear in one context:
+
+Gateways solve the “coordination layer” problem
+
+Orchestrators handle compute (GPU jobs).
+
+Gateways handle:
+
+- Job intake
+- Routing
+- Pricing
+- Matching workloads to the right orchestrator
+- Providing an interface for applications
+
+## Why Gateways Matter
+
+As Livepeer transitions into a high-demand, real-time AI network, Gateways become essential infrastructure. They enable:
+
+- Low-latency workflows for Daydream, ComfyStream, and other real-time AI video tools
+- Dynamic GPU routing for inference-heavy workloads
+- A decentralized marketplace of compute capabilities
+- Flexible integration via the BYOC pipeline model
+
+Gateways simplify the developer experience while preserving the decentralization, performance, and competitiveness of the Livepeer network.
+
+# Understanding Gateways
+
+Gateways are the entry point for applications into the Livepeer decentralized compute network. They provide the coordination layer that connects real-time AI and video workloads to the orchestrators who perform the GPU compute.
+
+---
+
+## What Gateways Do
+
+Gateways handle all service-level logic required to operate a scalable, low-latency AI video network:
+
+- **Job Intake**
+ They receive workloads from applications using Livepeer APIs, PyTrickle, or BYOC integrations.
+
+- **Capability & Model Matching**
+ Gateways determine which orchestrators support the required GPU, model, or pipeline.
+
+- **Routing & Scheduling**
+ They dispatch jobs to the optimal orchestrator based on performance, availability, and pricing.
+
+- **Marketplace Exposure**
+ Gateway operators can publish the services they offer, including supported models, pipelines, and pricing structures.
+
+Gateways do _not_ perform GPU compute. Instead, they focus on coordination and service routing.
+
+---
+
+## Relationship to Orchestrators
+
+Orchestrators are GPU operators who execute the actual workload—transcoding, AI inference, or BYOC containers. Gateways route jobs _to_ orchestrators, collect results, and return them to the application.
+
+**Applications → Gateway → Orchestrator → Gateway → Application**
+
+This separation allows:
+
+- Clean abstraction for developers
+- Efficient load balancing
+- Competition and specialization across operators
+- Support for a broad range of real-time AI pipelines
+
+---
+
+## Summary
+
+Gateways are the coordination and routing layer of the Livepeer ecosystem. They expose capabilities, price services, accept workloads, and dispatch them to orchestrators for GPU execution. This design enables a scalable, low-latency, AI-ready decentralized compute marketplace.
+
+### CALLOUT YOU CAN RUN A GATEWAY & EARN!
+
+ Random Notes only below here
+
+
+
+ This is referenced directly in Peter Schroedl's talk, where he describes the
+ Gateway + Orchestrator stack as the system PyTrickle connects into, enabling
+ apps to run arbitrary AI pipelines via Livepeer.
+
Gateways appear again in the marketplace discussion:
+
+
+ "Gateway operators [should] display or publicize what they're offering…
+ pricing, capabilities… orchestrators and gateways meet in the marketplace
+ concept."
+
+
+
This shows that gateways are the commercial / service-facing nodes.
+
+# Gateway vs Orchestrator: What’s the Difference?
+
+Livepeer uses two core node types—**Gateways** and **Orchestrators**—that work together to provide real-time AI video compute at scale. Although closely connected, they serve entirely different purposes. This page breaks down how they differ and why both roles matter for a decentralized compute marketplace.
+
+---
+
+## Overview
+
+| Role | Function | Performs GPU Work? | External-Facing? |
+| ---------------- | ---------------------------------------------- | ------------------ | ---------------- |
+| **Gateway** | Job intake, pricing, routing, capability match | ❌ No | ✅ Yes |
+| **Orchestrator** | GPU compute, inference, transcoding, BYOC | ✅ Yes | ❌ No |
+
+Gateways coordinate.
+Orchestrators compute.
+
+Together, they form the backbone of the Livepeer AI video pipeline.
+
+---
+
+## Gateway Responsibilities
+
+Gateways act as the front door to the network:
+
+- Receive jobs from applications
+- Determine required model, pipeline, or GPU
+- Select the best orchestrator based on performance and pricing
+- Route the workload with low latency
+- Return results to the client
+- Publish marketplace offerings (models, pipelines, cost per frame, etc.)
+
+Gateways provide _service intelligence_, not compute.
+
+---
+
+## Orchestrator Responsibilities
+
+Orchestrators are GPU operators who run:
+
+- Real-time AI inference
+- Daydream / ComfyStream pipelines
+- BYOC containers
+- Traditional transcoding
+
+They provide:
+
+- GPU horsepower
+- Model execution
+- Deterministic and verifiable output
+- Performance guarantees
+
+They do not expose external APIs directly—Gateways handle that.
+
+---
+
+## How They Work Together
+
+```mermaid
+sequenceDiagram
+ participant App as Application
+ participant GW as Gateway
+ participant ORC as Orchestrator
+
+ App->>GW: Submit job (model, parameters, video frames)
+ GW->>ORC: Route job to best GPU
+ ORC->>GW: Return processed frames/output
+ GW->>App: Send results back to user
+```
+
+## Why This Architecture Matters
+
+Decentralized competition — Gateways and orchestrators can specialize
+
+Better developer UX — Apps talk only to Gateways
+
+Better performance — Routing optimizes for GPU availability & latency
+
+Alignment — Orchestrators focus on compute; Gateways focus on services
+
+## Summary
+
+Gateways = service routers
+
+Orchestrators = GPU compute workers
+
+---
+
+# ✅ **3. Marketplace Architecture Page**
+
+_Mntlify-ready, polished, usable as a top-level docs page_
+
+````md
+# Marketplace Architecture
+
+The Livepeer Marketplace is an emerging ecosystem layer where Gateways and Orchestrators publicly advertise, price, and compete on real-time AI video services. This marketplace transforms Livepeer from a raw GPU network into a discoverable, composable, and economically aligned infrastructure layer.
+
+---
+
+## Why a Marketplace?
+
+As Livepeer shifts toward real-time AI video (Daydream, ComfyStream, BYOC pipelines), the network needs:
+
+- Service discovery
+- Capability matching
+- Transparent pricing
+- Quality and performance competition
+- A way for builders to choose providers intentionally
+
+Gateways and Orchestrators participate jointly to make this possible.
+
+---
+
+## Marketplace Participants
+
+### **Gateway Operators**
+
+Gateways publish:
+
+- Supported models (e.g., diffusion, ControlNet, IPAdapter)
+- Supported pipelines (ComfyStream workflows, BYOC containers)
+- Pricing (per frame, per second, per inference)
+- Geographic/latency characteristics
+- Performance metrics
+
+Gateways serve as the “service storefront.”
+
+---
+
+### **Orchestrator Operators**
+
+Orchestrators contribute:
+
+- GPU capacity (A40, 4090, L40S, etc.)
+- Model acceleration (TensorRT, Torch Compile)
+- Latency and throughput guarantees
+- Historical reliability/performance scores
+
+Orchestrators are the “supply side” of compute.
+
+---
+
+## Marketplace Workflow
+
+```mermaid
+flowchart TD
+
+ A[Application Developer] --> B[Gateway Marketplace Capabilities, Models, Pricing]
+
+ B -->|Select Gateway| C[Gateway Routing, Scheduling]
+
+ C -->|Match GPU Supply| D[Orchestrator GPU Execution]
+
+ D --> C --> A
+
+
+Key Marketplace Features
+1. Capability Discovery
+
+Gateways and orchestrators list:
+
+AI model support
+
+Versioning and model weights
+
+Pipeline compatibility
+
+GPU type and compute class
+
+Applications can programmatically choose the best provider.
+
+2. Dynamic Pricing
+
+Pricing can vary by:
+
+GPU class
+
+Model complexity
+
+Latency SLA
+
+Throughput requirements
+
+Region
+
+Gateways expose pricing APIs for transparent selection.
+
+3. Performance Competition
+
+Orchestrators compete on:
+
+Speed
+
+Reliability
+
+GPU quality
+
+Cost efficiency
+
+Gateways compete on:
+
+Routing quality
+
+Supported features
+
+Latency
+
+Developer ecosystem fit
+
+This creates a healthy decentralized market.
+
+4. BYOC Integration
+
+Any container-based pipeline can be brought into the marketplace:
+
+Run custom AI models
+
+Run ML workflows
+
+Execute arbitrary compute
+
+Support enterprise workloads
+
+Gateways advertise BYOC offerings; orchestrators execute containers.
+
+Marketplace Benefits
+
+Developer choice — choose the best model, price, and performance
+
+Economic incentives — better nodes earn more work
+
+Scalability — network supply grows independently of demand
+
+Innovation unlock — new models and pipelines can be added instantly
+
+Decentralization — no single operator controls the workload flow
+
+Summary
+
+The Marketplace turns Livepeer into a competitive, discoverable, real-time AI compute layer.
+Gateways expose services.
+Orchestrators execute them.
+Applications choose the best fit.
+
+This architecture enables Livepeer to scale into a global provider of real-time AI video infrastructure.
+```
+````
diff --git a/v2/pages/01_about/livepeer-network/livepeer-actors/orchestrators.mdx b/v2/pages/01_about/livepeer-network/livepeer-actors/orchestrators.mdx
new file mode 100644
index 00000000..67354d88
--- /dev/null
+++ b/v2/pages/01_about/livepeer-network/livepeer-actors/orchestrators.mdx
@@ -0,0 +1,4 @@
+
+
+# Orchestrators
+
diff --git a/v2/pages/01_about/livepeer-network/livepeer-governance.mdx b/v2/pages/01_about/livepeer-network/livepeer-governance.mdx
new file mode 100644
index 00000000..bf56f282
--- /dev/null
+++ b/v2/pages/01_about/livepeer-network/livepeer-governance.mdx
@@ -0,0 +1,17 @@
+---
+title: 'Livepeer Governance'
+sidebarTitle: 'Livepeer Governance'
+description: 'Learn about the Livepeer Governance Model.'
+---
+
+Livepeer is committed to open-source, transparent, community governance.
+
+
+
+
+Quick Links
+
+Discord: [https://discord.com/channels/423160867534929930/686685097935503397](https://discord.com/channels/423160867534929930/686685097935503397)
+
+RFPs
+
diff --git a/v2/pages/01_about/livepeer-network/livepeer-token-economics.mdx b/v2/pages/01_about/livepeer-network/livepeer-token-economics.mdx
new file mode 100644
index 00000000..1498104c
--- /dev/null
+++ b/v2/pages/01_about/livepeer-network/livepeer-token-economics.mdx
@@ -0,0 +1,44 @@
+---
+title: 'Livepeer Token'
+sidebarTitle: 'Livepeer Token'
+description: 'Learn about the Livepeer Token and its role in coordinating actor behaviour and securing the Livepeer Network.'
+---
+
+ Incorrect, Old content.
+
+
+See more on the LPT Token here [https://www.livepeer.org/lpt](https://www.livepeer.org/lpt)
+
+
+
+
+Livepeer is a utility token used to power & secure the decentralised Livepeer Network, enabling reliable, cost-efficient, powerful AI and video streaming functions.
+
+One of the biggest competitive advantages of Livepeer is its decentralisation - creating free markets and competitive pricing. This network of decentralised nodes, orchestrators, gateways and broadcasters, and the flow of payments in the network for doing useful work, is underpinned by the Livepeer Token (LPT)
+
+#### Actors
+
+* **Broadcaster (payer)** → submits jobs (video/AI) and funds them using **Probabilistic Micropayments (PM) tickets**.
+* **Orchestrator (validator/worker coordinator)** → stakes LPT (self-stake + delegated), wins work, forwards segments to…
+* **Transcoder (work executor)** → performs compute (encode/transcode/inference) for the orchestrator.
+* **Delegator (capital provider)** → bonds LPT to an orchestrator, shares its rewards & fees.
+* GPU Providers are paid for running AI Jobs
+
+**Flow:**
+
+Broadcaster → (PM tickets/segments) → Orchestrator → (tasks) → Transcoder → (results) → Broadcaster.
+
+**Economic weight flows:**
+
+Delegators → (bonded LPT) → Orchestrator → (rewards/fees split back) → Delegators.
+
+
+
+#### Economic Functions -> Staking, Rewards, Fees & Slashing
+
+
+
+
+
+#### Governance
+
diff --git a/v2/pages/01_about/livepeer-protocol/livepeer-whitepaper.mdx b/v2/pages/01_about/livepeer-protocol/livepeer-whitepaper.mdx
new file mode 100644
index 00000000..9fa0f2b0
--- /dev/null
+++ b/v2/pages/01_about/livepeer-protocol/livepeer-whitepaper.mdx
@@ -0,0 +1,20 @@
+---
+title: 'Livepeer Whitepaper'
+sidebarTitle: 'Whitepaper'
+---
+
+import WhitepaperContent from '/snippets/external/whitepaper.mdx'
+import { ExternalContent } from '/snippets/components/external-content.jsx'
+
+
+ View the Livepeer Whitepaper on Github
+
+
+Below is the Livepeer Whitepaper.
+
+
+
+
\ No newline at end of file
diff --git a/v2/pages/01_about/livepeer-protocol/protocol-overview.mdx b/v2/pages/01_about/livepeer-protocol/protocol-overview.mdx
new file mode 100644
index 00000000..3e7ae5d5
--- /dev/null
+++ b/v2/pages/01_about/livepeer-protocol/protocol-overview.mdx
@@ -0,0 +1,164 @@
+---
+title: 'Protocol Overview'
+sidebarTitle: 'Protocol Overview'
+---
+
+# Overview
+
+Livepeer is a full-stack platform for video streaming & AI. The video streaming software is underpinned by a network of actors that perform the work needed to compute, transcode & orchestrate video & AI jobs in the Livepeer network.
+
+The Livepeer Protocol is the underlying code that enforces the mechanisms and rules to ensure the reliability, cooperation and coordination of these decentralised actors.
+
+# Core Concepts
+
+## Livepeer Protocol
+The protocol is the ruleset + on-chain logic governing:
+- staking
+- delegation
+- inflation & rewards
+- orchestrator selection
+- slashing
+- probabilistic payments
+- verification rules
+
+The economic and coordination layer that enforces correct behavior.
+
+## Livepeer Network
+The network is the actual running system of machines performing work:
+- Orchestrators (GPU nodes)
+- Transcoders / Workers
+- Gateways
+- Broadcasters
+- Verification processes
+- Job routing
+- Real-time AI & video compute
+
+It is the live, operational decentralized GPU mesh running video + AI jobs.
+
+
+## Protocol vs Network
+| Layer | Description |
+| --------------------- | ----------------------------------------------------------------------------- |
+| **Livepeer Protocol** | On-chain crypto-economic incentives & coordination; staking; payments. |
+| **Livepeer Network** | Off-chain nodes performing real-time work (transcoding, inference, routing). |
+| **Relationship** | The network *runs* the compute; the protocol *governs, secures, and pays* it. |
+
+ Fix UGHH (brainsotrm)
+**Bad Analogy Yikes**
+Protocol = the constitution
+Network = the population + infrastructure living under that constitution
+
+The protocol governs.
+The network performs the work.
+
+The protocol determines the rules of the game
+The network is the players & participants.
+
+# On-chain vs Off-chain
+Livepeer protocol = Arbitrum One (L2)
+Livepeer token (LPT) = Ethereum mainnet (L1)
+Livepeer network (GPU nodes + gateways) = off-chain execution layer
+
+# Livepeer Actors
+A Livepeer actor is any role or entity that participates in the Livepeer protocol or network and performs actions defined by the system.
+In Livepeer architecture, “actor” is a formal category used to describe participants with distinct responsibilities, incentives, and interactions.
+Actors are fundamental to describing how the network functions end-to-end.
+
+INSERT LIVEPEER ACTOR DIAGRAM HERE \[THIS ONE LOOKS OLD (whitpaper)
+
+
+
+
+
+
+#### Broadcasters (deprecated -> Gateway)
+
+Who: The users and builders of the network.
+
+What they do:
+
+#### Orchestrators (GPU Nodes)
+aka: Transcoders / Workers
+
+Who:
+
+What they do:
+
+#### Gateways
+aka: Broadcasters
+
+Who:
+
+What they do:
+
+#### Delegators
+
+Who:
+
+What they do:
+
+Historical Livepeer Actors:
+1. Orchestrator
+
+GPU node that performs transcoding / AI jobs, earns fees + staking rewards.
+
+2. Transcoder (Worker)
+
+Child processes or machines managed by an orchestrator to perform compute.
+
+3. Broadcaster
+
+Client submitting jobs (video or AI) into the network.
+
+4. Delegator
+
+LPT holder who stakes to an orchestrator.
+
+
+
+3. Broadcaster (now a behavior, not an actor)
+
+In modern Livepeer, which has expanded beyond just video transcoding:
+
+A gateway acts as a broadcaster when submitting video
+A service (e.g., Studio) can also be a broadcaster
+The term is no longer treated as a standalone actor
+Broadcaster is no longer considered its own actor - it’s now a function performed by a gateway or service, not a role a user operates.
+
+“Broadcaster” is now just a function gateways perform, not a user-facing or protocol-facing actor
+
+4. Worker (legacy)
+
+Workers are still used, but only inside GPU node setups.
+
+Workers are not protocol actors
+
+They do not appear on-chain
+
+They are implementation detail for orchestrator/GPU Node setups
+
+5. Delegator (protocol-defined actor)
+
+They stake LPT
+
+They help secure the network
+
+They share in inflation + orchestrator rewards
+
+Protocol Actors
+
+GPU Node (Orchestrator) — supply-side compute provider
+
+Delegator — stake from demand side
+
+## Network / Execution Actors
+
+Gateway Node — submits and manages jobs (AI/video)
+
+Worker — internal compute role (not user-facing)
+
+Behaviors (not actors anymore)
+
+Broadcaster — any gateway/service sending video or AI jobs
+
+Transcoder — a type of worker behavior
\ No newline at end of file
diff --git a/v2/pages/01_about/livepeer-protocol/technical-overview.mdx b/v2/pages/01_about/livepeer-protocol/technical-overview.mdx
new file mode 100644
index 00000000..8c07c607
--- /dev/null
+++ b/v2/pages/01_about/livepeer-protocol/technical-overview.mdx
@@ -0,0 +1,84 @@
+---
+title: 'Technical Overview'
+sidebarTitle: 'Technical Overview'
+---
+
+import { GotoCard, GotoLink } from '/snippets/components/links.jsx'
+
+Livepeer is a decentralized infrastructure protocol that allows users to upload, transcode, and serve video content & run AI pipelines. It operates on a network with different node types including Gateways (formerly Broadcasters), Orchestrators, and Transcoders. The protocol uses smart contracts deployed on Ethereum Mainnet and Arbitrum Mainnet, with the native token LPT (Livepeer Token). Since the Confluence upgrade, the protocol primarily runs on Arbitrum Mainnet.
+
+## Protocol Technical Architecture
+
+TODO
+
+Definitely want image here
+
+## Protocol References
+
+Aggregate from from internal Livepeer Notions, Prev site & deepwiki
+
+### A/B/C TEST LAYOUTS
+
+**Expandable**
+
+
+
+
+
+
+
+ Whether the user is over 21 years old
+
+
+
+
+**Steps**
+
+
+
+
+
+
+ See all current contract addresses for the deployed protocol
+
+
+ See all current contract addresses for the deployed protocol
+
+
+
+**Basic Link**
+
+
+
+**Link Cards**
+
+
+
+### Links
+
+To remove... notes only
+Internal
+
+- [Reward Calc]("https://www.notion.so/livepeer/Livepeer-Protocol-Reward-Calculation-2320a34856878026adb0e7bcb7521661)
+- [Reward Accumulation]("https://www.notion.so/livepeer/Livepeer-Rewards-Accumulation-Mechanism-23e0a348568780199f26f8cbc3c2d231")
+- [Migration Report]("https://www.notion.so/livepeer/Livepeer-L1-L2-Migration-Report-Complete-Technical-Overview-2b10a348568780a28b59df9d8710bff9")
+
+Docs Current
+
+-
diff --git a/v2/pages/01_about/livepeer-protocol/technical-roadmap.mdx b/v2/pages/01_about/livepeer-protocol/technical-roadmap.mdx
new file mode 100644
index 00000000..696ac478
--- /dev/null
+++ b/v2/pages/01_about/livepeer-protocol/technical-roadmap.mdx
@@ -0,0 +1,6 @@
+# Technical Roadmap
+
+Roadmap:
+https://blog.livepeer.org/introducing-livepeer-cascade-a-vision-for-livepeers-future-in-the-age-of-real-time-ai-video/
+
+https://blog.livepeer.org/a-real-time-update-to-the-livepeer-network-vision/
diff --git a/v2/pages/01_about/tab-index.mdx b/v2/pages/01_about/tab-index.mdx
new file mode 100644
index 00000000..d3e0868f
--- /dev/null
+++ b/v2/pages/01_about/tab-index.mdx
@@ -0,0 +1,67 @@
+---
+title: 'About Index'
+---
+
+
+ Fix this. Not sure where the Tab Index should go & display must be better
+
+
+## Table of contents
+
+- ### [Quick Links](README.md)
+ -
+ -
+ - [Research](livepeer-protocol/research/README.md)
+
+## About Home
+
+- [Jump in](about-home/jump-in/README.md)
+ - [About Livepeer](about-home/jump-in/about-livepeer/README.md)
+ - [Livepeer Story](about-livepeer/about-livepeer/livepeer-story.md)
+ - [Livepeer Vision](about-livepeer/about-livepeer/livepeer-vision.md)
+ -
+- [Sections](about-home/sections/README.md)
+ - [About Livepeer](about-home/sections/about-livepeer/README.md)
+ - [Livepeer Story](about-livepeer/about-livepeer/livepeer-story.md)
+ - [Livepeer Vision](about-livepeer/about-livepeer/livepeer-vision.md)
+ -
+ -
+ -
+ - [Research](livepeer-protocol/research/README.md)
+
+## About Livepeer
+
+- [About Livepeer](about-livepeer/about-livepeer/README.md)
+ - [Livepeer Story](about-livepeer/about-livepeer/livepeer-story.md)
+ - [Livepeer Vision](about-livepeer/about-livepeer/livepeer-vision.md)
+ - [Why Livepeer?](about-livepeer/about-livepeer/why-livepeer.md)
+ - [Livepeer Ecosystem](about-livepeer/about-livepeer/livepeer-ecosystem/README.md)
+ - [Livepeer Ecosystem](about-livepeer/about-livepeer/livepeer-ecosystem/livepeer-ecosystem.md)
+ - [Livepeer Roadmap](about-livepeer/about-livepeer/livepeer-roadmap.md)
+
+## Project Showcase
+
+- [Projects Built on Livepeer](project-showcase/projects-built-on-livepeer.md)
+- [Industry Applications](project-showcase/industry-applications.md)
+
+## Livepeer Protocol
+
+- [Livepeer Protocol](livepeer-protocol/livepeer-protocol/README.md)
+ - [Technical Overview](livepeer-protocol/livepeer-protocol/technical-overview.md)
+ - [Livepeer Whitepaper](livepeer-protocol/livepeer-protocol/livepeer-whitepaper.md)
+- [Livepeer Actors](livepeer-protocol/livepeer-actors/README.md)
+ - [Gateways](livepeer-protocol/livepeer-actors/gateways.md)
+ - [Orchestrators](livepeer-protocol/livepeer-actors/orchestrators.md)
+ - [Delegators](livepeer-protocol/livepeer-actors/delegators.md)
+ - [End Users](livepeer-protocol/livepeer-actors/end-users.md)
+- [Livepeer Token Economics](livepeer-protocol/livepeer-token-economics.md)
+- [Technical Roadmap](livepeer-protocol/technical-roadmap.md)
+- [Livepeer Governance](livepeer-protocol/livepeer-governance.md)
+- [Research](livepeer-protocol/research/README.md)
+ - [Livepeer Whitepaper](livepeer-protocol/research/livepeer-whitepaper.md)
+
+## Concepts (move to references)
+
+- [Livepeer 101](concepts-move-to-references/livepeer-101.md)
+- [Livepeer Core Concepts](concepts-move-to-references/livepeer-core-concepts.md)
+- [Brief History of Video](concepts-move-to-references/brief-history-of-video.md)
diff --git a/v2/pages/02_community/README.mdx b/v2/pages/02_community/README.mdx
new file mode 100644
index 00000000..11b0fd27
--- /dev/null
+++ b/v2/pages/02_community/README.mdx
@@ -0,0 +1,57 @@
+# Community Hub
+
+## Livepeer Socials
+
+## Follow all quick links
+
+### Social Media
+
+- [Follow Livepeer on X](https://x.com/livepeer)
+- [Follow Livepeer People & Projects List on X](https://x.com/i/lists/YOUR_LIST_ID)
+- [Follow Livepeer on LinkedIn](https://www.linkedin.com/company/livepeer/)
+- [Subscribe to YouTube](https://youtube.com/@livepeer)
+- [Subscribe to the mirror blog](https://mirror.xyz/livepeer.eth)
+- [Subscribe to the paragraph blog](https://paragraph.com/@livepeer-2) -> Is this the [Main Blog Site](https://blog.livepeer.org) publisher?
+- [Subscribe to the medium blog](https://mirror.xyz/livepeer.eth)
+- [Subscribe to the newsletter](#newsletter)
+- [Get notified of Livepeer Events](https://luma.com/livepeer)
+- [Join Telegram](https://t.me/livepeer)
+- [Join Reddit](https://reddit.com/r/livepeer)
+- [Visit GitHub](https://github.com/livepeer)
+- [Event Calendar](https://luma.com/livepeer)
+- [Join Discord](https://discord.gg/livepeer)
+- [Join the Forum](https://forum.livepeer.org)
+
+## Subscribe to Github Updates
+
+- [Main Repo](https://github.com/livepeer)
+- [Livepeer Awesome Repo](https://github.com/livepeer/awesome-livepeer)
+- [Livepeer Docs Repo](https://github.com/livepeer/docs)
+
+## Subscribe to other product updates
+
+- [Livepeer Studio](https://livepeer.com/studio)
+- [Daydream](https://daydream.live)
+- [Livepeer Explorer](https://livepeer.com/explorer)
+- [Streamcaster](https://stream.place/about)
+- [Frameworks](https://frameworks.network/about)
+- [Embody](https://embody.zone/)
+
+## Stay Informed of the Latest
+
+- Subscribe to [mirror blog](https://mirror.xyz/livepeer.eth)
+- Subscribe to [main blog](https://blog.livepeer.org)
+- Subscribe to [paragraph blog](https://paragraph.com/@livepeer-2)
+- Subscribe to [medium blog](https://medium.com/livepeer-blog)
+- Subscribe to [newsletter](#newsletter)
+- Subscribe to [YouTube](https://youtube.com/@livepeer)
+- Subscribe to [Luma events](https://luma.com/livepeer)
+
+## Interactive Community Meetings & Help Forums
+
+- **[Discord Community](https://discord.gg/livepeer)** - Get help & get involved
+- **[Livepeer Forum](https://forum.livepeer.org)** - Get help and get involved
+- **Livestreamed Community Meetings** - Participate & get help
+ - Livepeer Fireside - on Discord (streamed to YT?)
+ - Watercooler Chat - on Discord (streamed to YT?)
+ - Treasury Talk ?
diff --git a/v2/pages/02_community/SUMMARY.mdx b/v2/pages/02_community/SUMMARY.mdx
new file mode 100644
index 00000000..96832712
--- /dev/null
+++ b/v2/pages/02_community/SUMMARY.mdx
@@ -0,0 +1,22 @@
+# Table of contents
+
+## Livepeer Community
+
+* [Community Hub](README.md)
+* [Livepeer Hot Topics & Updates](livepeer-community/livepeer-hot-topics-and-updates.md)
+* [Media Kit](livepeer-community/media-kit.md)
+
+## Livepeer News & Socials
+
+* [Livepeer Socials](livepeer-news-and-socials/livepeer-socials.md)
+* [Livepeer Blogs & News](livepeer-news-and-socials/livepeer-blogs-and-news.md)
+
+## Events & Community Hours
+
+* [Events Calendar](events-and-community-hours/events-calendar.md)
+* [Interactive Community Steams](events-and-community-hours/interactive-community-steams.md)
+
+## Livepeer HUBs
+
+* [Livepeer Partner Hub](livepeer-hubs/livepeer-partner-hub.md)
+* [Livepeer Builder Hub](livepeer-hubs/livepeer-builder-hub.md)
diff --git a/v2/pages/02_community/_move_me/livepeer-hubs/livepeer-builder-hub.mdx b/v2/pages/02_community/_move_me/livepeer-hubs/livepeer-builder-hub.mdx
new file mode 100644
index 00000000..1422c629
--- /dev/null
+++ b/v2/pages/02_community/_move_me/livepeer-hubs/livepeer-builder-hub.mdx
@@ -0,0 +1,2 @@
+# Livepeer Builder Hub
+
diff --git a/v2/pages/02_community/_move_me/livepeer-hubs/livepeer-partner-hub.mdx b/v2/pages/02_community/_move_me/livepeer-hubs/livepeer-partner-hub.mdx
new file mode 100644
index 00000000..737b0e4c
--- /dev/null
+++ b/v2/pages/02_community/_move_me/livepeer-hubs/livepeer-partner-hub.mdx
@@ -0,0 +1,10 @@
+
+
+# Livepeer Partner Hub
+
+
+
+## Livepeer Partnerships
+
+
diff --git a/v2/pages/03_developers/ai-inference-on-livepeer/livepeer-ai/overview-ai-on-livepeer.mdx b/v2/pages/03_developers/ai-inference-on-livepeer/livepeer-ai/overview-ai-on-livepeer.mdx
new file mode 100644
index 00000000..0722430e
--- /dev/null
+++ b/v2/pages/03_developers/ai-inference-on-livepeer/livepeer-ai/overview-ai-on-livepeer.mdx
@@ -0,0 +1,14 @@
+---
+title: 'Overview: AI on Livepeer'
+---
+
+# Overview: AI on Livepeer
+
+As one of the earliest decentralised physical infrastructure networks (DePIN), Livepeer is in a unique position to utilise its network of GPU nodes to run AI workloads.
+
+
+
+
+
+Livepeer Founder Eric Tang demonstrating the capability for real-time avatar animation from a Livestream video input. [Ref: [Introducing Livepeer Cascade](https://mirror.xyz/livepeer.eth/bCruUtv0PJWWlFxfbCMATGM_h15hUncwvyFW1A3z7Ag) - Nov 2024]
+
diff --git a/v2/pages/03_developers/ai-inference-on-livepeer/livepeer-ai/realtime-ai.mdx b/v2/pages/03_developers/ai-inference-on-livepeer/livepeer-ai/realtime-ai.mdx
new file mode 100644
index 00000000..466b5418
--- /dev/null
+++ b/v2/pages/03_developers/ai-inference-on-livepeer/livepeer-ai/realtime-ai.mdx
@@ -0,0 +1,4 @@
+
+
+# Realtime AI
+
diff --git a/v2/pages/03_developers/ai-inference-on-livepeer/livepeer-ai/using-ai-on-livepeer.mdx b/v2/pages/03_developers/ai-inference-on-livepeer/livepeer-ai/using-ai-on-livepeer.mdx
new file mode 100644
index 00000000..06df7292
--- /dev/null
+++ b/v2/pages/03_developers/ai-inference-on-livepeer/livepeer-ai/using-ai-on-livepeer.mdx
@@ -0,0 +1,4 @@
+
+
+# Using AI on Livepeer
+
diff --git a/v2/pages/03_developers/ai-inference-on-livepeer/page-2.mdx b/v2/pages/03_developers/ai-inference-on-livepeer/page-2.mdx
new file mode 100644
index 00000000..1dbccb19
--- /dev/null
+++ b/v2/pages/03_developers/ai-inference-on-livepeer/page-2.mdx
@@ -0,0 +1,2 @@
+# Page 2
+
diff --git a/v2/pages/03_developers/builder-opportunities/dev-programs.mdx b/v2/pages/03_developers/builder-opportunities/dev-programs.mdx
new file mode 100644
index 00000000..52064ace
--- /dev/null
+++ b/v2/pages/03_developers/builder-opportunities/dev-programs.mdx
@@ -0,0 +1,27 @@
+---
+title: 'Dev Programs'
+sidebarTitle: 'Dev Programs'
+---
+
+This page is intended as a guide for startup projects building on Livepeer, OSS Developers looking to contribute and community member participation pathways.
+
+
+Need more info
+
+
+### Hackathons
+
+...
+
+### Dev Programs
+
+...
+
+### Treasury ?
+
+
+**Other ?**
+
+- Livepeer Developer Paths
+- Funding for Startups
+
diff --git a/v2/pages/03_developers/builder-opportunities/livepeer-rfps.mdx b/v2/pages/03_developers/builder-opportunities/livepeer-rfps.mdx
new file mode 100644
index 00000000..345dbfac
--- /dev/null
+++ b/v2/pages/03_developers/builder-opportunities/livepeer-rfps.mdx
@@ -0,0 +1,15 @@
+---
+title: 'Livepeer RFPs'
+sidebarTitle: 'Livepeer RFPs'
+---
+
+## RFPs Overview
+...
+
+## Current RFPs
+...
+
+## Grants
+
+- Grant process
+
diff --git a/v2/pages/03_developers/builder-opportunities/oss-contributions.mdx b/v2/pages/03_developers/builder-opportunities/oss-contributions.mdx
new file mode 100644
index 00000000..0c2c9980
--- /dev/null
+++ b/v2/pages/03_developers/builder-opportunities/oss-contributions.mdx
@@ -0,0 +1,4 @@
+
+
+# OSS Contributions
+
diff --git a/v2/pages/03_developers/building-on-livepeer/developer-guide.mdx b/v2/pages/03_developers/building-on-livepeer/developer-guide.mdx
new file mode 100644
index 00000000..d521c9fc
--- /dev/null
+++ b/v2/pages/03_developers/building-on-livepeer/developer-guide.mdx
@@ -0,0 +1,151 @@
+---
+title: 'Developer Guide'
+sidebarTitle: 'Developer Guide'
+description: 'A guide to building on Livepeer for video streaming and AI pipelines'
+---
+
+
+## Overview
+
+Anyone building software that uses Livepeer compute, contributes to the Livepeer Protocol, or builds tooling for network operators is a developer.
+
+This section is for those folks looking to ...
+
+The easiest way to use AI or video is to use a hosted service such as Daydream or Livepeer Studio.
+If you want to develop directly on the protocol… you'll start by running your own gateway node.
+
+ Test Diagram 1: Possible Definitions
+```mermaid
+flowchart LR
+ classDef title fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px
+ classDef node fill:##0d0d0d,color:#fff,stroke:#2d9a67,stroke-width:1px
+ classDef role fill:#0d0d0d,color:#fff,stroke:#2d9a67,stroke-width:1px
+
+ A[Developer Umbrella Term]:::title --> B[Uses Third-Party Gateway Studio, Daydream, External API]:::node
+ A --> C[Runs Own Gateway Node]:::node
+ A --> D[Builds Protocol Extensions e.g., Liquid Staking, Smart Contracts]:::node
+ A --> E[Builds Tooling for GPU Node Operators Monitoring, Automation]:::node
+
+ B --> B1[Not a Protocol Actor Consumes Livepeer indirectly]:::node
+ C --> C1[Assumes Gateway Role Consumes Livepeer Network directly]:::node
+ D --> D1[Protocol Integrator Interacts with Livepeer Protocol]:::node
+ E --> E1[Ecosystem Contributor Supports GPU Nodes]:::node
+```
+
+ Test Diagram 2: Possible Journeys
+```mermaid
+flowchart LR
+ classDef title fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px
+ classDef node fill:#0d0d0d,color:#fff,stroke:#2d9a67,stroke-width:1px
+ classDef role fill:#0d0d0d,color:#fff,stroke:#2d9a67,stroke-width:1px
+
+ A[Developer / Builder Umbrella Term]:::title
+
+ A --> B1[I build applications that consume video/AI compute]:::node
+ A --> C1[I want to run infrastructure or operate a node]:::node
+ A --> D1[I want to extend Livepeer Protocol or write smart contracts]:::node
+ A --> E1[I build tooling for operators or data analysis dashboards]:::node
+ A --> F1[I want to contribute socially govern, educate, or organize]:::node
+
+ B1 --> B2[Application Developer Uses a Hosted Gateway]:::role
+ B1 --> B3[Gateway Operator Runs own Gateway Node]:::role
+ C1 --> C2[GPU Node Operator Provides compute to network]:::role
+ D1 --> D2[Protocol Developer Builds staking derivatives]:::role
+ E1 --> E2[Tooling Engineer Observability and analysis]:::role
+ F1 --> F2[Community Builder Education and governance]:::role
+```
+
+
+ Testing developer Journey
+
+
+## What do you want to do?
+ TESTING: Landing Page for Developer Persona
+-> choose your own adventure here.
+
+
+
+ Broadcast Real-Time Video
+
+
+ Run AI Pipelines on Livepeer
+
+
+ Build Your Own App
+
+
+ Integrate With Livepeer
+
+
+ Placeholder - Build your own platorm
+
+
+ Contribute to the Ecosystem as an OSS Developer
+
+ Be a founder
+
+ Win Hacks
+
+
+ Find Grants, RFPs & Other Opportunities
+
+
+
+
+What are the possible persona journeys.
+
+
+
+
+Developer Mapping:
+- Using a hosted gateway → Application Developer
+- Running their own gateway → Gateway Operator
+- Extending protocol contracts → Protocol Developer
+- Building node tooling → Tooling / Data Engineer
+- Helping grow ecosystem → Community / Governance Builder
+
diff --git a/v2/pages/03_developers/building-on-livepeer/developer-journey.mdx b/v2/pages/03_developers/building-on-livepeer/developer-journey.mdx
new file mode 100644
index 00000000..c74508c0
--- /dev/null
+++ b/v2/pages/03_developers/building-on-livepeer/developer-journey.mdx
@@ -0,0 +1,30 @@
+---
+title: 'Developer Journey'
+sidebarTitle: 'Developer Journey'
+description: 'A guide to building on Livepeer for video streaming and AI pipelines'
+---
+
+| Stage | Name | Purpose | Outcomes |
+|-------|------|---------|----------|
+| 0 | Awareness | Understand Livepeer, compute model, ecosystem roles | Clarity on Protocol → Network → Apps; basic mental model |
+| 1 | Orientation | Identify which builder persona fits their goals | Path chosen: App Dev, Gateway Operator, GPU Node, Protocol Dev, Tooling, Community |
+| 2 | Activation | Perform first meaningful action in chosen path | "First win" achieved: app built, node deployed, contract written, tool created |
+| 3 | Progression | Increase expertise and contribution | Contributions, optimizations, mentoring, advanced workflows |
+| 4 | Hero | Become a leader/steward in the ecosystem | Operate at scale, publish tools, author proposals, run programs |
+
+
+```mermaid
+flowchart TD
+ classDef stage fill:#0d0d0d,color:#fff,stroke:#2d9a67,stroke-width:1px;
+ classDef phase fill:#0d0d0d,color:#fff,stroke:#2d9a67,stroke-width:1px;
+
+ A["Stage 0: Awareness What is Livepeer?"]:::stage --> B["Stage 1: Orientation Choose builder path"]:::stage
+ B --> C["Stage 2: Activation First wins"]:::stage
+ C --> D["Stage 3: Progression Deepening skills"]:::stage
+ D --> E["Stage 4: Hero Ecosystem leadership"]:::stage
+
+ B --> B1["Paths: • Application Developer • Gateway Operator • GPU Node Operator • Protocol Developer • Tooling Developer • Community Builder"]:::phase
+ C --> C1["Each path executes its first real success milestone"]:::phase
+ D --> D1["Contribute, optimize, mentor, build advanced infra"]:::phase
+ E --> E1["Heroes lead apps, gateways, nodes, protocol, tooling, gov"]:::phase
+```
\ No newline at end of file
diff --git a/v2/pages/03_developers/building-on-livepeer/quick-starts/README.mdx b/v2/pages/03_developers/building-on-livepeer/quick-starts/README.mdx
new file mode 100644
index 00000000..43b834ee
--- /dev/null
+++ b/v2/pages/03_developers/building-on-livepeer/quick-starts/README.mdx
@@ -0,0 +1,6 @@
+
+
+# Quick Starts
+
+ {/* { "group": "Quickstart: Livepeer Real-time Video", "pages": [] },
+ { "group": "Quickstart: Livepeer AI Pipelines", "pages": [] }, */}
\ No newline at end of file
diff --git a/v2/pages/03_developers/building-on-livepeer/quick-starts/livepeer-ai.mdx b/v2/pages/03_developers/building-on-livepeer/quick-starts/livepeer-ai.mdx
new file mode 100644
index 00000000..55b9f8f2
--- /dev/null
+++ b/v2/pages/03_developers/building-on-livepeer/quick-starts/livepeer-ai.mdx
@@ -0,0 +1,4 @@
+
+
+# Livepeer AI
+
diff --git a/v2/pages/03_developers/building-on-livepeer/quick-starts/video-streaming.mdx b/v2/pages/03_developers/building-on-livepeer/quick-starts/video-streaming.mdx
new file mode 100644
index 00000000..f4eca403
--- /dev/null
+++ b/v2/pages/03_developers/building-on-livepeer/quick-starts/video-streaming.mdx
@@ -0,0 +1,4 @@
+
+
+# Video Streaming
+
diff --git a/v2/pages/03_developers/developer-home.mdx b/v2/pages/03_developers/developer-home.mdx
new file mode 100644
index 00000000..6abf7cfa
--- /dev/null
+++ b/v2/pages/03_developers/developer-home.mdx
@@ -0,0 +1,64 @@
+---
+title: 'Developer Portal'
+sidebarTitle: 'Developer Home'
+tag: Start Here
+description: 'Welcome To The Developer Portal: Explore, Navigate, Build'
+---
+
+## Developer Portal: Map
+
+**Definition**
+Developers are...
+
+**Quick Intro**
+Get Situated
+
+## Developer Portal: Choose Your Mission
+Your Journey Starts Here / More "normal" Wording for AI/SEO
+
+
+
+..
+
+
+..
+
+
+ Developer Level up: Deploy your own Gateway on the Livepeer Protocol.
+
+
+.
+
+
+ .
+
+
+
+---
+
+?Gateway Portal FAQs
+
+
+## Gateway Portal Jump Pad
+Bit irrelevant after the missions
+Jump to
+- [What's a Gateway?](#whats-a-gateway)
+- [Gateway Services & Providers](#gateway-services--providers)
+- [Run a Gateway](#run-a-gateway)
+- [Gateway Tools & Dashboards](#gateway-tools--dashboards)
+- [Gateway Guides & Resources](#gateway-guides--resources)
\ No newline at end of file
diff --git a/v2/pages/03_developers/developer-platforms/all-ecosystem/ecosystem-products.mdx b/v2/pages/03_developers/developer-platforms/all-ecosystem/ecosystem-products.mdx
new file mode 100644
index 00000000..e69de29b
diff --git a/v2/pages/03_developers/developer-platforms/builder-hub.mdx b/v2/pages/03_developers/developer-platforms/builder-hub.mdx
new file mode 100644
index 00000000..dccf13c7
--- /dev/null
+++ b/v2/pages/03_developers/developer-platforms/builder-hub.mdx
@@ -0,0 +1,156 @@
+---
+title: 'Builders HUB'
+description: Platforms & Products that make using Livepeer easy in your applications
+sidebarTitle: Builders HUB
+tag: Bookmark Me
+---
+
+ WIP Section
+
+ This index should potentially be dynamic. This would require some scripting,
+ but could become an automated gateways HUB.
+
+
+import { GotoLink } from '/snippets/components/links.jsx'
+
+
+
+# Developer Platforms
+
+
+ Ideally we want a sortable and filterable table with tags and cateogries.
+ It\'sprobably best to embed this from elsewhere for full functionality
+
+
+
+
+
+
+
+
+ Daydream provides the tools to build with open world models and real-time AI, and the community where creatives, builders, and researchers advance the field together.
+
+
+
+
+
+
+
+
+ Livepeer Studio is a developer-friendly gateway and toolkit for the Livepeer decentralized video infrastructure.
+
+ Livepeer Studio offers easy-to-use APIs and dashboards for builders to add scalable, cost-efficient, and censorship-resistant live streaming and video-on-demand (VOD) features to applications.
+
+ Unlock Innovation with Livepeer Studio's Next-Generation APIs:
+ - Increase Engagement with Live Streaming
+ - Ensure integrity for video on demand
+ - Optimize Workflows with Transcode API
+
+
+
+
+
+
+ Frameworks: Full-Stack Video Infrastructure { } Open stack • Live video processing • Flexible deployments}
+ icon="cloud-binary"
+ href="./frameworks/frameworks"
+ arrow
+ cta="Learn More About Frameworks"
+ >
+
+
+ The only streaming platform that combines full self-hosting capabilities with hosted processing, backed by unique features you won’t find anywhere else.
+
+ The MistServer team is on a mission to democratize video infrastructure by leveraging decentralized protocols and open source technology -> creating a streaming infrastructure that doesn't lock you in.
+
+ Run it yourself, use Frameworks' hosted services, or mix and match.
+
+ Uncloud your infrastructure.
+
+
+
+
+
+
+
+
+ Streamplace is building open-source infrastructure to bring high-quality
+ video experiences to the AT Protocol ecosystem, while preserving user
+ sovereignty and content authenticity.
+
+
+
+
+
+
+
+ See all platforms available to builders in the Livepeer Ecosystem
+
+
+
+## All Products & Platforms
+
+Embed a list from somewhere
+
+### Links
+
+#### Daydream
+
+https://daydream.live/
+** Open-source community and toolkit for world models and real-time AI video **
+
+Daydream provides the tools to build with open world models and real-time AI, and the community where creatives, builders, and researchers advance the field together.
+
+#### Stream.place
+
+https://stream.place/about
+** The video layer for decentralized social networks **
+
+Streamplace is building open-source infrastructure to bring high-quality video experiences to the AT Protocol ecosystem, while preserving user sovereignty and content authenticity.
+
+#### Frameworks
+
+https://frameworks.network/
+** Full-Stack Video Infrastructure: Open stack • Live video processing • Flexible deployments **
+
+The only streaming platform that combines full self-hosting capabilities with hosted processing, backed by unique features you won’t find anywhere else.
+
+We're building the streaming infrastructure that doesn't lock you in. Need custom features? Build them yourself or let us help. Switch providers? Your infrastructure comes with you. Cloud bills spiraling? Run it yourself with our open source stack.
+
+Built by the MistServer team and subsidized by the Livepeer treasury, we're on a mission to democratize video infrastructure by leveraging decentralized protocols and open source technology.
+
+Run it yourself, use our hosted services, or mix and match. Uncloud your infrastructure.
+
+#### Embody Avatars
+
+https://embody.zone/
+** Enterprise-grade AI avatars for real-time telepresence and content creation.Scale your communication. Eliminate boundaries. **
diff --git a/v2/pages/03_developers/developer-platforms/daydream/daydream.mdx b/v2/pages/03_developers/developer-platforms/daydream/daydream.mdx
new file mode 100644
index 00000000..b845b532
--- /dev/null
+++ b/v2/pages/03_developers/developer-platforms/daydream/daydream.mdx
@@ -0,0 +1,2 @@
+# Daydream
+
diff --git a/v2/pages/03_developers/developer-platforms/frameworks/frameworks.mdx b/v2/pages/03_developers/developer-platforms/frameworks/frameworks.mdx
new file mode 100644
index 00000000..1738920b
--- /dev/null
+++ b/v2/pages/03_developers/developer-platforms/frameworks/frameworks.mdx
@@ -0,0 +1,3 @@
+# Frameworks SPE
+
+https://www.youtube.com/watch?v=DKBRp0U-RKw&t=1s
diff --git a/v2/pages/03_developers/developer-platforms/livepeer-studio/livepeer-studio.mdx b/v2/pages/03_developers/developer-platforms/livepeer-studio/livepeer-studio.mdx
new file mode 100644
index 00000000..c4290400
--- /dev/null
+++ b/v2/pages/03_developers/developer-platforms/livepeer-studio/livepeer-studio.mdx
@@ -0,0 +1,4 @@
+
+
+# Livepeer Studio
+
diff --git a/v2/pages/03_developers/developer-platforms/streamplace/streamplace-architecture.mdx b/v2/pages/03_developers/developer-platforms/streamplace/streamplace-architecture.mdx
new file mode 100644
index 00000000..02fef6e8
--- /dev/null
+++ b/v2/pages/03_developers/developer-platforms/streamplace/streamplace-architecture.mdx
@@ -0,0 +1,199 @@
+---
+title: 'Streamplace Architecture'
+description: 'Detailed architecture showing Streamplace, Livepeer, Orchestrators, provenance, and user layers.'
+---
+
+---
+
+Streamplace sits between decentralized social applications and the Livepeer Network to provide a **full ingestion → provenance → transcoding → distribution** pipeline.
+
+This page consolidates the full architectural model, including:
+
+- Streamplace SPE responsibilities
+- Node & SDK architecture
+- C2PA + Ethereum provenance flow
+- Livepeer broadcaster + orchestrator roles
+- User playback and verification
+
+---
+
+# 🧩 High-Level Architecture Diagram
+
+```mermaid
+flowchart TB
+
+ subgraph DAO[Livepeer Foundation / DAO]
+ T[Treasury Grants & Governance]
+ end
+
+ subgraph SPE[Streamplace SPE]
+ S1[Node / SDK / APIs]
+ S2[Metadata Schema]
+ S3[C2PA + Ethereum Signatures]
+ end
+
+ subgraph Social[Decentralized Social Apps]
+ U1[AT Protocol Apps]
+ U2[Fediverse Clients]
+ U3[Web3 Video Platforms]
+ end
+
+ subgraph Node[Streamplace Node]
+ N1[Ingest WHIP/WHEP/RTMP]
+ N2[Segment MP4 (1s)]
+ N3[Embed Metadata + Rights]
+ N4[Apply Provenance]
+ end
+
+ subgraph Livepeer[Livepeer Network]
+ B[Broadcaster]
+ O[Orchestrators - GPU]
+ V[Verifiability Layer]
+ end
+
+ subgraph Playback[Playback Layer]
+ P[HLS/WebRTC Player]
+ end
+
+ DAO --> SPE
+ Social --> Node
+ SPE --> Node
+ Node --> Livepeer
+ Livepeer --> Playback
+```
+
+---
+
+# 🧠 Architecture Layer Explanations
+
+## 1. **Livepeer Foundation / DAO (Funding Layer)**
+
+The Livepeer Treasury funds Streamplace as a **Special Purpose Entity** to deliver:
+
+- open-source video infrastructure
+- provenance systems
+- a node + SDK usable by any decentralized social app
+
+This ensures long-term sustainability and alignment with public-goods principles.
+
+---
+
+## 2. **Streamplace SPE Layer**
+
+Streamplace’s responsibilities include:
+
+- designing and maintaining the **streaming node**
+- providing developer **SDKs + APIs**
+- managing the **metadata schema** (`place.stream.metadata.*`)
+- developing the **C2PA + Ethereum provenance pipeline**
+
+This layer ships infrastructure—not a hosted platform.
+
+---
+
+## 3. **Application / Client Layer (Decentralized Social Apps)**
+
+Apps integrate the Streamplace SDK to:
+
+- start livestreams
+- configure metadata (rights, warnings, policies)
+- authenticate creators via wallets or identity systems
+
+Examples:
+
+- AT Protocol apps
+- Fediverse clients
+- Web3 creator tools
+
+---
+
+## 4. **Streamplace Node Layer (Ingest & Provenance)**
+
+The Streamplace Node performs the bulk of technical heavy lifting:
+
+### Ingest
+
+Supports:
+
+- WHIP / WHEP
+- RTMP
+- Browser WebRTC
+
+### Segmentation
+
+Splits video into **1-second MP4 segments**.
+
+### Provenance
+
+Each segment receives:
+
+- **C2PA manifest**
+- **Ethereum signature** for identity binding
+
+### Metadata Embedding
+
+Attaches:
+
+- content rights
+- distribution policy
+- content warnings
+- playback configuration
+
+---
+
+## 5. **Livepeer Network Layer**
+
+Once Streamplace packages segments, it hands off video to Livepeer.
+
+**Broadcaster Role:**
+
+- receives signed segments
+- dispatches them to orchestrators
+
+**Orchestrators:**
+
+- GPU-accelerated transcoding
+- ABR (multi-bitrate) generation
+- may include environment metadata
+
+**Verifiability Layer:**
+
+- ensures correct transcoding
+- enables trust-minimized delivery
+
+---
+
+## 6. **Distribution Layer (Streamplace Output)**
+
+Streamplace reconstructs:
+
+- HLS manifests
+- WebRTC session outputs
+- metadata-enriched playback structures
+
+It also ensures:
+
+- provenance integrity is preserved end-to-end
+- distributionPolicy rules are enforced
+
+---
+
+## 7. **Playback Layer (User-Facing)**
+
+Users receive:
+
+- HLS or WebRTC streams
+- metadata, warnings, rights displays
+- verifiable provenance (C2PA + Ethereum)
+
+This makes video **trustworthy, rights-aware, and censorship-resistant**.
+
+---
+
+# 🔗 Related Pages
+
+- [Overview](/streamplace/overview)
+- [How Streamplace Works](/streamplace/how-it-works)
+- [Provenance & Metadata](/streamplace/provenance)
+- [Funding Model](/streamplace/funding)
+- [Developer Integration Guide](/streamplace/integration)
diff --git a/v2/pages/03_developers/developer-platforms/streamplace/streamplace-funding-model.mdx b/v2/pages/03_developers/developer-platforms/streamplace/streamplace-funding-model.mdx
new file mode 100644
index 00000000..2e54b8d1
--- /dev/null
+++ b/v2/pages/03_developers/developer-platforms/streamplace/streamplace-funding-model.mdx
@@ -0,0 +1,106 @@
+---
+title: 'SPE Funding Model'
+description: "Understanding Streamplace's role and responsibilities as a Special Purpose Entity (SPE) funded by the Livepeer ecosystem."
+---
+
+---
+
+Streamplace operates as a **Special Purpose Entity (SPE)** within the Livepeer ecosystem. SPEs are publicly funded teams responsible for building **critical, open-source, public-goods infrastructure** that strengthens and expands the Livepeer Network.
+
+This page explains:
+
+- What an SPE is
+- How funding flows from the Livepeer Treasury
+- How Streamplace uses this funding
+- Why the SPE model exists
+
+---
+
+# 🏛️ What Is an SPE?
+
+A **Special Purpose Entity** is a mission-driven engineering or operational team funded by the Livepeer ecosystem to deliver:
+
+- Long-term infrastructure
+- Open-source software
+- Network-level capabilities
+- Public goods that benefit creators, developers, and node operators
+
+Streamplace is an SPE specifically focused on **decentralized video infrastructure, provenance systems, and SDKs for social/Web3 applications**.
+
+---
+
+# 💸 Funding Flow Diagram
+
+```mermaid
+flowchart TD
+ A[Livepeer DAO / Treasury] --> B[Streamplace SPE]
+ B --> C[Open-source Infrastructure]
+ C --> D[Ecosystem Developers]
+ D --> E[Users / Viewers]
+```
+
+---
+
+# 📦 What Streamplace Delivers as an SPE
+
+Treasury funding enables Streamplace to maintain and improve:
+
+### **1. Streamplace Node**
+
+- ingest (WHIP/WHEP/RTMP)
+- segmentation
+- provenance embedding (C2PA + Ethereum)
+- transcoding dispatch
+
+### **2. SDK & APIs**
+
+Developer-friendly tools for:
+
+- livestreaming
+- metadata configuration
+- playback integrations
+- social app embedding
+
+### **3. Metadata & Provenance Standards**
+
+A complete schema for:
+
+- rights
+- content warnings
+- distribution policy
+- replay and episode metadata
+
+### **4. Public-Goods Infrastructure**
+
+Everything Streamplace builds is:
+
+- **open-source**
+- **transparent**
+- **ecosystem-owned**
+- **permissionless** to adopt
+
+---
+
+# 🔥 Why the SPE Model Exists
+
+SPEs ensure that Livepeer can sustainably fund complex, long-term projects without relying on:
+
+- venture capital
+- centralized operators
+- closed-source business models
+
+The SPE model creates:
+
+- stable capacity for critical network work
+- transparent accountability
+- ecosystem resilience
+- healthy decentralization
+
+---
+
+# 📚 Related Pages
+
+- [Streamplace Overview](/streamplace/overview)
+- [Architecture](/streamplace/architecture)
+- [Provenance & Metadata](/streamplace/provenance)
+- [Developer Integration Guide](/streamplace/integration)
diff --git a/v2/pages/03_developers/developer-platforms/streamplace/streamplace-guide.mdx b/v2/pages/03_developers/developer-platforms/streamplace/streamplace-guide.mdx
new file mode 100644
index 00000000..3f7fc0e7
--- /dev/null
+++ b/v2/pages/03_developers/developer-platforms/streamplace/streamplace-guide.mdx
@@ -0,0 +1,109 @@
+---
+title: 'How Streamplace Works'
+description: 'A step-by-step explanation of ingest, segmentation, provenance, transcoding, and delivery.'
+---
+
+---
+
+Streamplace transforms livestreams into **verifiable, rights-aware, decentralized video pipelines** that plug directly into the Livepeer Network.
+
+Below is the full end-to-end workflow.
+
+---
+
+## 🧩 End-to-End Flow Diagram
+
+```mermaid
+flowchart TD
+ A[User Livestreams / Social App] --> B[Streamplace Node]
+ B --> C[Segment MP4s (1s)]
+ C --> D[C2PA Manifest + Ethereum Signature]
+ D --> E[Send to Livepeer Broadcaster]
+ E --> F[Orchestrators Transcode GPU]
+ F --> G[Return ABR Streams]
+ G --> H[Streamplace Manifests + Metadata]
+ H --> I[Viewers Watch + Verify Provenance]
+```
+
+---
+
+## 🔍 Step-by-Step Breakdown
+
+### **1. Ingest**
+
+Streamplace supports multiple ingestion methods:
+
+- WHIP / WHEP
+- RTMP
+- Browser-native WebRTC
+
+These inputs feed directly into the Streamplace Node.
+
+---
+
+### **2. Segmentation**
+
+Streamplace splits incoming video into **1-second MP4 segments**, enabling:
+
+- per-segment authentication
+- fine-grained metadata control
+- efficient transcoding dispatch
+- modular VOD assembly
+
+---
+
+### **3. Provenance Layer**
+
+Every segment receives:
+
+- a **C2PA content authenticity manifest**, and
+- an **Ethereum signature** linked to creator identity.
+
+This ensures integrity, provability, and non-repudiation for every part of the video.
+
+---
+
+### **4. Transcoding via Livepeer**
+
+Streamplace dispatches segments to the **Livepeer decentralized GPU network**:
+
+- orchestrators transcode segments
+- multi-bitrate (ABR) outputs are generated
+- provenance is preserved end-to-end
+
+---
+
+### **5. Manifest Reconstruction**
+
+Streamplace rebuilds:
+
+- HLS manifests
+- WebRTC streams
+- metadata-rich playback structures
+
+Segments, signatures, metadata, and playback context are merged into a single coherent output.
+
+---
+
+### **6. Playback & Verification**
+
+Users receive:
+
+- HLS or WebRTC outputs
+- provenance-aware video streams
+- automatic rights, warnings, and attribution
+
+Players can independently verify:
+
+- C2PA manifests
+- Ethereum signatures
+- rights & distribution policies
+
+---
+
+## 📚 Related Pages
+
+- [Overview](/streamplace/overview)
+- [Architecture](/streamplace/architecture)
+- [Provenance & Metadata](/streamplace/provenance)
+- [Integration Guide](/streamplace/integration)
diff --git a/v2/pages/03_developers/developer-platforms/streamplace/streamplace-integration.mdx b/v2/pages/03_developers/developer-platforms/streamplace/streamplace-integration.mdx
new file mode 100644
index 00000000..53d69133
--- /dev/null
+++ b/v2/pages/03_developers/developer-platforms/streamplace/streamplace-integration.mdx
@@ -0,0 +1,128 @@
+---
+title: 'Developer Integration Guide'
+description: 'How to integrate Streamplace into decentralized social apps, Web3 platforms, and Livepeer-powered video pipelines.'
+---
+
+---
+
+# Developer Integration Guide
+
+This guide explains how developers can integrate Streamplace into their decentralized applications. Streamplace provides a complete **ingest → provenance → transcoding → distribution** pipeline that plugs directly into the Livepeer Network.
+
+You get:
+
+- livestreaming
+- metadata & rights management
+- provenance (C2PA + Ethereum signatures)
+- seamless transcoding through Livepeer
+- HLS/WebRTC playback
+
+---
+
+# 🚀 Quick Start
+
+## 1. Install the Streamplace Node
+
+```bash
+curl -s https://get.stream.place/install | bash
+```
+
+## 2. Start a Livestream
+
+```bash
+streamplace stream start --source webcam
+```
+
+## 3. Add Metadata
+
+Configure content rights, warnings, and distribution policies:
+
+```json
+{
+ "contentRights": "CC-BY-4.0",
+ "contentWarnings": ["flashing lights"],
+ "distributionPolicy": {
+ "retainSegments": true,
+ "allowSyndication": true
+ }
+}
+```
+
+## 4. Use the Streamplace SDK
+
+```ts
+import { StreamplaceClient } from '@streamplace/sdk'
+
+const sp = new StreamplaceClient()
+const stream = await sp.createStream()
+```
+
+---
+
+# 🧩 How Streamplace Integrates With Livepeer
+
+Streamplace does **not** perform transcoding itself. Instead, it:
+
+1. Segments and signs each MP4 chunk (1s)
+2. Embeds metadata + provenance
+3. Sends segments to Livepeer broadcasters
+4. Orchestrators on the Livepeer Network handle GPU transcoding
+5. Streamplace rebuilds manifests and prepares playback outputs
+
+This offloads all compute-heavy work to the **decentralized GPU market**.
+
+---
+
+# 📦 Playback Integration
+
+Streamplace provides playback endpoints:
+
+- **HLS manifests**
+- **WebRTC sessions**
+
+Players can:
+
+- verify C2PA manifests
+- verify Ethereum signatures
+- display rights/warnings automatically
+
+Example UI component (React):
+
+```jsx
+
+```
+
+---
+
+# 🔧 Integration Patterns
+
+## 🤝 1. Social Networks (AT Protocol, Fediverse)
+
+- user livestream creation
+- automatic rights/warning surfacing
+- provenance-aware feeds
+
+## 🎥 2. Creator Platforms
+
+- per-video ownership proofs
+- automated licensing and credit display
+
+## 📰 3. Journalism & Fact-Checking
+
+- verifiable provenance for every segment
+- tamper detection built into playback
+
+## 🏛️ 4. Community-Run Video Platforms
+
+- self-hosted node + distributed moderation
+- metadata-driven distribution rules
+
+---
+
+# 📚 Related Pages
+
+- [Streamplace Overview](/streamplace/overview)
+- [How Streamplace Works](/streamplace/how-it-works)
+- [Architecture](/streamplace/architecture)
+- [Provenance & Metadata](/streamplace/provenance)
+- [SPE Funding Model](/streamplace/funding)
diff --git a/v2/pages/03_developers/developer-platforms/streamplace/streamplace-provenance.mdx b/v2/pages/03_developers/developer-platforms/streamplace/streamplace-provenance.mdx
new file mode 100644
index 00000000..38327dc1
--- /dev/null
+++ b/v2/pages/03_developers/developer-platforms/streamplace/streamplace-provenance.mdx
@@ -0,0 +1,132 @@
+---
+title: 'Provenance & Metadata'
+description: 'How C2PA manifests, Ethereum signatures, and the Streamplace metadata schema create verifiable, rights-aware video.'
+---
+
+---
+
+Streamplace is the first decentralized video infrastructure layer to combine:
+
+- **C2PA content authenticity manifests**
+- **Ethereum-based cryptographic signatures**
+- **A complete metadata system for rights, warnings, and distribution rules**
+
+This creates a _verifiable, tamper-evident, rights-aware video pipeline_ suitable for decentralized social networks, journalism, creator ecosystems, and Web3-native platforms.
+
+---
+
+# 🛡️ Why Provenance Matters
+
+Traditional video platforms provide no guarantees about:
+
+- Who created a video
+- Whether it has been altered
+- Whether rights or warnings attached to it are authentic
+
+Streamplace solves this by ensuring that **every single 1-second video segment carries cryptographic proof** of origin and policy.
+
+---
+
+# 🧬 Provenance Pipeline Diagram
+
+```mermaid
+flowchart LR
+ A[MP4 Segment (1s)] --> B[C2PA Manifest]
+ A --> C[Ethereum Signature]
+ B --> D[Composite Provenance]
+ C --> D
+ D --> E[Transcoding on Livepeer]
+ E --> F[Playback + Verification]
+```
+
+---
+
+# 🔐 C2PA Manifests
+
+Each segment includes a **C2PA (Content Credentials) manifest**, which:
+
+- Captures creator identity
+- Includes claims about rights, sources, edits, and warnings
+- Provides tamper-evident cryptographic sealing
+
+C2PA provenance is _standards-based_, making Streamplace output compatible with tooling used by:
+
+- Adobe
+- Microsoft
+- Nikon
+- The Content Authenticity Initiative
+
+Reference: [https://spec.c2pa.org/](https://spec.c2pa.org/)
+
+---
+
+# 🔏 Ethereum Signatures
+
+In addition to C2PA, Streamplace attaches **Ethereum signatures** that:
+
+- Bind creator identity to content
+- Integrate with Web3 identity systems
+- Allow on-chain verification
+
+This creates a _dual provenance layer_: open standards + decentralized identity.
+
+---
+
+# 🧱 Metadata Schema (Rights, Warnings, Policies)
+
+Streamplace defines a rich metadata system under `place.stream.metadata.*`.
+
+Key fields:
+
+- `contentRights` — licensing, attribution, copyright
+- `contentWarnings` — safety, graphic content, flashing lights, etc.
+- `distributionPolicy` — retention rules, syndication permissions, geography
+- `configuration` — playback preferences
+- `story/series` metadata — episode, chapter, continuity
+
+Docs: [https://stream.place/docs/video-metadata/metadata-record/](https://stream.place/docs/video-metadata/metadata-record/)
+
+---
+
+# 🌐 How Metadata + Provenance Survive Transcoding
+
+A major design innovation: **provenance persists even after Livepeer transcoding**.
+
+The process:
+
+1. Streamplace embeds provenance into each segment before sending to Livepeer.
+2. Orchestrators transcode segments without stripping provenance.
+3. Streamplace reconstructs manifests with provenance intact.
+4. Playback clients can verify signatures independently.
+
+This creates an **end-to-end authenticity chain**, even across decentralized compute.
+
+---
+
+# 🧩 Example Use Cases
+
+### **1. Decentralized Social Networks**
+
+Users get video with automatic rights, warnings, and authorship.
+
+### **2. Citizen Journalism**
+
+Segments can be independently verified for authenticity.
+
+### **3. Creator Economy Platforms**
+
+Rights metadata travels with content, enabling automatic attribution.
+
+### **4. Moderation Tools**
+
+Platforms can rely on embedded metadata instead of platform-owned signals.
+
+---
+
+# 📚 Related Pages
+
+- [Streamplace Overview](/streamplace/overview)
+- [How Streamplace Works](/streamplace/how-it-works)
+- [Architecture](/streamplace/architecture)
+- [SPE Funding Model](/streamplace/funding)
+- [Developer Integration Guide](/streamplace/integration)
diff --git a/v2/pages/03_developers/developer-platforms/streamplace/streamplace.mdx b/v2/pages/03_developers/developer-platforms/streamplace/streamplace.mdx
new file mode 100644
index 00000000..0be84a25
--- /dev/null
+++ b/v2/pages/03_developers/developer-platforms/streamplace/streamplace.mdx
@@ -0,0 +1,53 @@
+---
+title: 'Streamplace Overview'
+description: 'What Streamplace is, why it exists, and how it fits into the Livepeer Network.'
+sidebarTitle: 'Streamplace Overview'
+---
+
+Streamplace is a **Special Purpose Entity (SPE)** in the Livepeer ecosystem responsible for building a **public-goods, open-source decentralized video layer** for social networks, livestreaming platforms, and Web3-native apps.
+
+It provides:
+
+- A **livestream ingest + VOD pipeline**
+- **C2PA + Ethereum-based provenance** for every video segment
+- A **metadata schema** for rights, content warnings, and distribution policies
+- A **node + SDK** for easy integration into decentralized apps
+- A bridge into **Livepeer’s decentralized GPU network**
+
+---
+
+## ✨ Why Streamplace Exists
+
+Centralized video platforms own:
+
+- Identity
+- Audience
+- Distribution
+- Monetization
+
+Streamplace inverts that model with open, verifiable, permissionless infrastructure built for:
+
+- AT Protocol clients
+- Fediverse social apps
+- Web3 creators
+- Community-run video platforms
+
+---
+
+## 🎥 Embedded Introduction Video
+
+```mdx
+
+```
+
+> Replace `LIVEPEER_INTRO_VIDEO_ID` with the actual YouTube ID.
+
+---
+
+## 📚 Related Pages
+
+- [How Streamplace Works](/streamplace/how-it-works)
+- [Architecture](/streamplace/architecture)
+- [Provenance & Metadata](/streamplace/provenance)
+- [SPE Funding Model](/streamplace/funding)
+- [Developer Integration Guide](/streamplace/integration)
diff --git a/v2/pages/03_developers/developer-tools/dashboards.mdx b/v2/pages/03_developers/developer-tools/dashboards.mdx
new file mode 100644
index 00000000..306b5c50
--- /dev/null
+++ b/v2/pages/03_developers/developer-tools/dashboards.mdx
@@ -0,0 +1,20 @@
+---
+title: 'Community & Network Dashboards'
+description: 'Monitoring and analytics tools for the Livepeer network'
+sidebarTitle: 'Dashboards'
+---
+
+# Community & Network Dashboards
+
+- **Orchestrator Dashboards**: These provide a view of staking income, delegator statistics, and fee payouts for individual network nodes (orchestrators) that perform the video processing work.
+- **Livepeer.tools**: A popular community tool that offers visibility for LPT token holders (delegators) across different orchestrators, helping them make informed decisions about where to stake their tokens.
+- **Livepeer Explorer**: A general-purpose tool that allows users to track overall network activity, including the number of active nodes and ongoing bids for work.
+- **Grant Progress Tracking**: A dashboard proposed and implemented by the GovWorks SPE to provide transparency into how DAO grant funds are used and track project milestones.
+
+#### Livepeer Cloud vs. Livepeer Studio
+
+| Feature | Livepeer Cloud Dashboard | Livepeer Studio |
+|---------|--------------------------|-----------------|
+| Primary Goal | Increase network accessibility and adoption for a broader audience. | A production-ready platform for developers to build decentralized video apps via APIs and SDKs. |
+| User Focus | Non-crypto-native users and those who want a simple "test drive". | Developers, startups, and businesses requiring a full-featured, scalable solution. |
+| Complexity | Designed for simplicity, abstracts away blockchain complexities (like managing wallets) initially. | Offers advanced tools, APIs, and customization options for professional integration. |
\ No newline at end of file
diff --git a/v2/pages/03_developers/developer-tools/external-tooling.mdx b/v2/pages/03_developers/developer-tools/external-tooling.mdx
new file mode 100644
index 00000000..6eed74cf
--- /dev/null
+++ b/v2/pages/03_developers/developer-tools/external-tooling.mdx
@@ -0,0 +1,11 @@
+
+
+# External Tooling
+
+Tooling
+
+
+
+
+
+Dashboards & Monitoring
diff --git a/v2/pages/03_developers/developer-tools/gateways.mdx b/v2/pages/03_developers/developer-tools/gateways.mdx
new file mode 100644
index 00000000..6a030f96
--- /dev/null
+++ b/v2/pages/03_developers/developer-tools/gateways.mdx
@@ -0,0 +1,2 @@
+# Gateways
+
diff --git a/v2/pages/03_developers/developer-tools/livepeer-cloud.mdx b/v2/pages/03_developers/developer-tools/livepeer-cloud.mdx
new file mode 100644
index 00000000..30efae4c
--- /dev/null
+++ b/v2/pages/03_developers/developer-tools/livepeer-cloud.mdx
@@ -0,0 +1,24 @@
+---
+title: 'Livepeer Tools Dashboard'
+description: 'Livepeer Cloud'
+sidebarTitle: 'Livepeer Cloud'
+---
+
+
+ WIP Section: Fix definitions
+
+The Livepeer Cloud Tools Dashboard is a user interface and set of tools provided by the Livepeer Cloud initiative to enhance accessibility and provide analytics for users of the decentralized Livepeer network.
+
+The Livepeer Cloud Tools Dashboard serves as an entry point and monitoring tool, helping abstract the technical complexity of the underlying decentralized network for easier use and testing. You can access related resources through the [Livepeer Cloud website](https://livepeer.cloud) or the [Livepeer Studio platform](https://livepeer.studio) for building applications.
+
+ Add Image
+
+ Livepeer Tools Dashboard
+
+
+### Key Functions and Features
+Key features and components associated with the dashboard include:
+- **Public Broadcaster Access**: It provides a simple, free-to-use gateway to the Livepeer network for testing purposes, allowing users to experience decentralized streaming easily.
+- **Analytics & Metrics**: The dashboard offers visibility into network activity, providing metrics on usage, performance, and fees, which is useful for both broadcasters and node operators (orchestrators/transcoders).
+- **Performance Monitoring**: Specific dashboards, like the AI Performance Leaderboard, help users monitor the real-time performance and reliability of the various nodes (orchestrators) that provide AI and transcoding services on the network.
+- **Integration Support**: It is designed to work with existing media server workflows (like Owncast), aiming to bring Livepeer's benefits to users' existing tools rather than forcing a migration to an entirely new platform.
diff --git a/v2/pages/03_developers/developer-tools/livepeer-explorer.mdx b/v2/pages/03_developers/developer-tools/livepeer-explorer.mdx
new file mode 100644
index 00000000..336f63e3
--- /dev/null
+++ b/v2/pages/03_developers/developer-tools/livepeer-explorer.mdx
@@ -0,0 +1,24 @@
+---
+title: 'Livepeer Explorer'
+description: 'Monitor and manage your Livepeer network'
+sidebarTitle: 'Livepeer Explorer'
+---
+
+ WIP Section: Fix definitions
+
+The Livepeer Explorer is a web-based analytics and interaction tool that provides a gateway to the Livepeer network. It allows users to monitor network activity, track performance, and participate in the network's governance and staking processes.
+ Add Image
+
+
+ Livepeer Explorer
+
+
+### Key Functions and Features
+The Livepeer Explorer is designed for different network participants, including token holders (delegators) and node operators (orchestrators).
+
+- **Network Monitoring**: Users can track overall network activity, including the number of active orchestrator nodes, total LPT staked, and the estimated amount of video processing minutes performed.
+- **Staking and Delegation**: A primary function of the Explorer is to facilitate staking. LPT token holders who do not run a node can use the explorer to delegate their tokens to an orchestrator, thus helping to secure the network and earning a share of the rewards.
+- **Orchestrator Insights**: The explorer provides detailed information and performance metrics for individual orchestrator nodes, including yield estimates and fee structures. This helps delegators make informed decisions about which node to stake their LPT with.
+- **Gateway Insights**: The explorer provides detailed information and performance metrics for individual gateway nodes, including pricing, capabilities, and performance metrics. This helps developers make informed decisions about which gateway to use.
+- **Transaction Tracking**: It provides a real-time list of network transactions, such as fee claims, staking actions, and token delegations.
+- **Governance**: The Explorer allows LPT token holders to vote on proposals related to the network's future development and upgrades.
\ No newline at end of file
diff --git a/v2/pages/03_developers/developer-tools/tooling-hub.mdx b/v2/pages/03_developers/developer-tools/tooling-hub.mdx
new file mode 100644
index 00000000..be92e96c
--- /dev/null
+++ b/v2/pages/03_developers/developer-tools/tooling-hub.mdx
@@ -0,0 +1,18 @@
+---
+title: 'Tooling Hub'
+description: 'Tools for building on Livepeer'
+sidebarTitle: 'Tooling Hub'
+tag: Bookmark Me
+---
+
+ WIP Section
+
+ This index should potentially be dynamic. This would require some scripting,
+ but could become an automated gateways HUB.
+
+
+
+
+ Daydream provides the tools to build with open world models and real-time AI, and the community where creatives, builders, and researchers advance the field together.
+
+
diff --git a/v2/pages/03_developers/guides-and-resources/contribution-guide.mdx b/v2/pages/03_developers/guides-and-resources/contribution-guide.mdx
new file mode 100644
index 00000000..5eee1c80
--- /dev/null
+++ b/v2/pages/03_developers/guides-and-resources/contribution-guide.mdx
@@ -0,0 +1,2 @@
+# Contribution Guide
+
diff --git a/v2/pages/03_developers/guides-and-resources/developer-guides.mdx b/v2/pages/03_developers/guides-and-resources/developer-guides.mdx
new file mode 100644
index 00000000..404e0b61
--- /dev/null
+++ b/v2/pages/03_developers/guides-and-resources/developer-guides.mdx
@@ -0,0 +1,4 @@
+
+
+# Developer Guides
+
diff --git a/v2/pages/03_developers/guides-and-resources/developer-help.mdx b/v2/pages/03_developers/guides-and-resources/developer-help.mdx
new file mode 100644
index 00000000..76cd0500
--- /dev/null
+++ b/v2/pages/03_developers/guides-and-resources/developer-help.mdx
@@ -0,0 +1,17 @@
+
+
+# Developer Help
+
+A pipeline to office hours, guide to discord & forum channels
+
+
+
+### Getting help
+
+Discord
+
+Forum
+
+
+
+Ask at Livepeer Office Hours
diff --git a/v2/pages/03_developers/guides-and-resources/resources.mdx b/v2/pages/03_developers/guides-and-resources/resources.mdx
new file mode 100644
index 00000000..06f84ec5
--- /dev/null
+++ b/v2/pages/03_developers/guides-and-resources/resources.mdx
@@ -0,0 +1,2 @@
+# Resources
+
diff --git a/v2/pages/03_developers/livepeer-real-time-video/page-1.mdx b/v2/pages/03_developers/livepeer-real-time-video/page-1.mdx
new file mode 100644
index 00000000..6f8b4979
--- /dev/null
+++ b/v2/pages/03_developers/livepeer-real-time-video/page-1.mdx
@@ -0,0 +1,2 @@
+# Page 1
+
diff --git a/v2/pages/03_developers/livepeer-real-time-video/video-streaming-on-livepeer/README.mdx b/v2/pages/03_developers/livepeer-real-time-video/video-streaming-on-livepeer/README.mdx
new file mode 100644
index 00000000..c9eac196
--- /dev/null
+++ b/v2/pages/03_developers/livepeer-real-time-video/video-streaming-on-livepeer/README.mdx
@@ -0,0 +1,4 @@
+
+
+# Video Streaming on Livepeer
+
diff --git a/v2/pages/03_developers/livepeer-real-time-video/video-streaming-on-livepeer/frameworks-spe.mdx b/v2/pages/03_developers/livepeer-real-time-video/video-streaming-on-livepeer/frameworks-spe.mdx
new file mode 100644
index 00000000..3791e366
--- /dev/null
+++ b/v2/pages/03_developers/livepeer-real-time-video/video-streaming-on-livepeer/frameworks-spe.mdx
@@ -0,0 +1,4 @@
+
+
+# Frameworks SPE
+
diff --git a/v2/pages/03_developers/livepeer-real-time-video/video-streaming-on-livepeer/streamdiffusion.mdx b/v2/pages/03_developers/livepeer-real-time-video/video-streaming-on-livepeer/streamdiffusion.mdx
new file mode 100644
index 00000000..02caea1b
--- /dev/null
+++ b/v2/pages/03_developers/livepeer-real-time-video/video-streaming-on-livepeer/streamdiffusion.mdx
@@ -0,0 +1,4 @@
+
+
+# StreamDiffusion
+
diff --git a/v2/pages/03_developers/livepeer-real-time-video/video-streaming-on-livepeer/video-streaming-101.mdx b/v2/pages/03_developers/livepeer-real-time-video/video-streaming-on-livepeer/video-streaming-101.mdx
new file mode 100644
index 00000000..313aa231
--- /dev/null
+++ b/v2/pages/03_developers/livepeer-real-time-video/video-streaming-on-livepeer/video-streaming-101.mdx
@@ -0,0 +1,4 @@
+
+
+# Video Streaming 101
+
diff --git a/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-actors/README.mdx b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-actors/README.mdx
new file mode 100644
index 00000000..6d178eca
--- /dev/null
+++ b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-actors/README.mdx
@@ -0,0 +1,4 @@
+
+
+# Livepeer Actors
+
diff --git a/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-actors/delegators.mdx b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-actors/delegators.mdx
new file mode 100644
index 00000000..b8fb5df0
--- /dev/null
+++ b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-actors/delegators.mdx
@@ -0,0 +1,4 @@
+
+
+# Delegators
+
diff --git a/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-actors/end-users.mdx b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-actors/end-users.mdx
new file mode 100644
index 00000000..028129a1
--- /dev/null
+++ b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-actors/end-users.mdx
@@ -0,0 +1,4 @@
+
+
+# End Users
+
diff --git a/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-actors/gateways.mdx b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-actors/gateways.mdx
new file mode 100644
index 00000000..3811f61c
--- /dev/null
+++ b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-actors/gateways.mdx
@@ -0,0 +1,4 @@
+
+
+# Gateways
+
diff --git a/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-actors/orchestrators.mdx b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-actors/orchestrators.mdx
new file mode 100644
index 00000000..67354d88
--- /dev/null
+++ b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-actors/orchestrators.mdx
@@ -0,0 +1,4 @@
+
+
+# Orchestrators
+
diff --git a/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-governance.mdx b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-governance.mdx
new file mode 100644
index 00000000..773723c5
--- /dev/null
+++ b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-governance.mdx
@@ -0,0 +1,18 @@
+
+
+# Livepeer Governance
+
+Livepeer is committed to open-source, transparent, community governance.
+
+
+
+
+
+
+
+Quick Links
+
+Discord: [https://discord.com/channels/423160867534929930/686685097935503397](https://discord.com/channels/423160867534929930/686685097935503397)
+
+RFPs
+
diff --git a/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-protocol/README.mdx b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-protocol/README.mdx
new file mode 100644
index 00000000..6cc6869c
--- /dev/null
+++ b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-protocol/README.mdx
@@ -0,0 +1,45 @@
+---
+title: 'Livepeer Protocol'
+---
+
+# Livepeer Protocol
+
+Livepeer is a full-stack platform for video streaming & AI. The video streaming software is underpinned by a network of actors that perform the work needed to compute, transcode & orchestrate video & AI jobs in the Livepeer network.
+
+The Livepeer Protocol is the underlying code that enforces the mechanisms and rules to ensure the reliability, cooperation and coordination of these decentralised actors.
+
+### Livepeer Protocol Actors
+
+
+INSERT LIVEPEER ACTOR DIAGRAM HERE (THIS ONE LOOKS OLD - whitepaper)
+
+
+#### Broadcasters
+
+Who: The users and builders of the network.
+
+What they do:
+
+#### Orchestrators
+
+Who:
+
+What they do:
+
+#### Gateways
+
+Who:
+
+What they do:
+
+#### Nodes (GPUs)
+
+Who:
+
+What they do:
+
+#### Delegators
+
+Who:
+
+What they do:
diff --git a/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-protocol/livepeer-whitepaper.mdx b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-protocol/livepeer-whitepaper.mdx
new file mode 100644
index 00000000..1f45202d
--- /dev/null
+++ b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-protocol/livepeer-whitepaper.mdx
@@ -0,0 +1,4 @@
+
+
+# Livepeer Whitepaper
+
diff --git a/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-protocol/technical-overview.mdx b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-protocol/technical-overview.mdx
new file mode 100644
index 00000000..0427c826
--- /dev/null
+++ b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-protocol/technical-overview.mdx
@@ -0,0 +1,4 @@
+
+
+# Technical Overview
+
diff --git a/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-token-economics.mdx b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-token-economics.mdx
new file mode 100644
index 00000000..d81f23a5
--- /dev/null
+++ b/v2/pages/03_developers/moved-to-about-livepeer-protocol/livepeer-token-economics.mdx
@@ -0,0 +1,43 @@
+---
+title: 'Livepeer Token Economics'
+---
+
+# Livepeer Token Economics
+
+
+See more on the LPT Token here [https://www.livepeer.org/lpt](https://www.livepeer.org/lpt)
+
+
+
+
+Livepeer is a utility token used to power & secure the decentralised Livepeer Network, enabling reliable, cost-efficient, powerful AI and video streaming functions.
+
+One of the biggest competitive advantages of Livepeer is its decentralisation - creating free markets and competitive pricing. This network of decentralised nodes, orchestrators, gateways and broadcasters, and the flow of payments in the network for doing useful work, is underpinned by the Livepeer Token (LPT)
+
+#### Actors
+
+* **Broadcaster (payer)** → submits jobs (video/AI) and funds them using **Probabilistic Micropayments (PM) tickets**.
+* **Orchestrator (validator/worker coordinator)** → stakes LPT (self-stake + delegated), wins work, forwards segments to…
+* **Transcoder (work executor)** → performs compute (encode/transcode/inference) for the orchestrator.
+* **Delegator (capital provider)** → bonds LPT to an orchestrator, shares its rewards & fees.
+* GPU Providers are paid for running AI Jobs
+
+**Flow:**
+
+Broadcaster → (PM tickets/segments) → Orchestrator → (tasks) → Transcoder → (results) → Broadcaster.
+
+\
+**Economic weight flows:**
+
+Delegators → (bonded LPT) → Orchestrator → (rewards/fees split back) → Delegators.
+
+
+
+#### Economic Functions -> Staking, Rewards, Fees & Slashing
+
+
+
+
+
+#### Governance
+
diff --git a/v2/pages/03_developers/moved-to-about-livepeer-protocol/technical-roadmap.mdx b/v2/pages/03_developers/moved-to-about-livepeer-protocol/technical-roadmap.mdx
new file mode 100644
index 00000000..604080f5
--- /dev/null
+++ b/v2/pages/03_developers/moved-to-about-livepeer-protocol/technical-roadmap.mdx
@@ -0,0 +1,4 @@
+
+
+# Technical Roadmap
+
diff --git a/v2/pages/03_developers/technical-references/apis.mdx b/v2/pages/03_developers/technical-references/apis.mdx
new file mode 100644
index 00000000..add5dda5
--- /dev/null
+++ b/v2/pages/03_developers/technical-references/apis.mdx
@@ -0,0 +1,4 @@
+
+
+# APIs
+
diff --git a/v2/pages/03_developers/technical-references/awesome-livepeer.mdx b/v2/pages/03_developers/technical-references/awesome-livepeer.mdx
new file mode 100644
index 00000000..9c436ae1
--- /dev/null
+++ b/v2/pages/03_developers/technical-references/awesome-livepeer.mdx
@@ -0,0 +1,21 @@
+---
+title: 'Awesome Livepeer'
+sidebarTitle: 'Awesome Livepeer'
+---
+
+import AwesomeContent from '/snippets/external/awesome-livepeer-readme.mdx'
+import { ExternalContent } from '/snippets/components/external-content.jsx'
+
+
+ View Awesome Livepeer on Github
+
+
+## Awesome Livepeer
+Below is the README from Awesome Livepeer - a community-curated list of resources.
+
+
+
+
\ No newline at end of file
diff --git a/v2/pages/03_developers/technical-references/deepwiki.mdx b/v2/pages/03_developers/technical-references/deepwiki.mdx
new file mode 100644
index 00000000..268907e2
--- /dev/null
+++ b/v2/pages/03_developers/technical-references/deepwiki.mdx
@@ -0,0 +1,23 @@
+---
+title: DeepWiki
+sidebarTitle: DeepWiki
+---
+
+DeepWiki is a fantastic resource for exploring the Livepeer codebase.
+
+If you haven't heard of it before, DeepWiki - developed by Cognition AI (the creators of Devin AI) - is an AI-powered service that generates interactive, wiki-style documentation for GitHub repositories, turning codebases into accessible knowledge bases for developers to quickly understand architecture, functionality, and workflows through natural language Q&A.
+
+
+ View Livepeer Org Repo's on DeepWiki
+
+
+ As with all AI generated content, not everything on DeepWiki is accurate!
+
+
\ No newline at end of file
diff --git a/v2/pages/03_developers/technical-references/sdks.mdx b/v2/pages/03_developers/technical-references/sdks.mdx
new file mode 100644
index 00000000..0f3aff91
--- /dev/null
+++ b/v2/pages/03_developers/technical-references/sdks.mdx
@@ -0,0 +1,4 @@
+
+
+# SDKs
+
diff --git a/v2/pages/03_developers/technical-references/wiki.mdx b/v2/pages/03_developers/technical-references/wiki.mdx
new file mode 100644
index 00000000..c92a0bf6
--- /dev/null
+++ b/v2/pages/03_developers/technical-references/wiki.mdx
@@ -0,0 +1,49 @@
+---
+title: Livepeer Wiki
+sidebarTitle: Livepeer Wiki
+---
+
+import WikiContent from '/snippets/external/wiki-readme.mdx'
+
+
+ View the Livepeer Wiki on Github
+
+
+Below is the README from the Livepeer Wiki.
+
+
\ No newline at end of file
diff --git a/v2/pages/04_gateways/SUMMARY.mdx b/v2/pages/04_gateways/SUMMARY.mdx
new file mode 100644
index 00000000..0c8f068c
--- /dev/null
+++ b/v2/pages/04_gateways/SUMMARY.mdx
@@ -0,0 +1,14 @@
+# Table of contents
+
+## About Gateways
+
+- [Gateways](README.md)
+- [Choosing a gateway](about-gateways/choosing-a-gateway.md)
+
+## Gateway Tools
+
+- [Page 2](gateway-tools/page-2.md)
+
+## Run a Gateway
+
+- [Page 3](run-a-gateway/page-3.md)
diff --git a/v2/pages/04_gateways/_tests-to-delete/codemap.mdx b/v2/pages/04_gateways/_tests-to-delete/codemap.mdx
new file mode 100644
index 00000000..f7def882
--- /dev/null
+++ b/v2/pages/04_gateways/_tests-to-delete/codemap.mdx
@@ -0,0 +1,134 @@
+## Gateway Roles in Video Transcoding vs AI Pipelines
+This codemap illustrates how Livepeer Gateways serve as unified entry points for both traditional video transcoding and AI processing workflows. The traces show the dual architecture where [1a-1d] demonstrates gateway initialization with both BroadcastSessionsManager and AISessionManager, [2a-2d] traces the traditional transcoding pipeline through RTMP ingest to HLS output, [3a-3d] shows AI request routing through specialized session managers, [4a-4d] details the real-time live video AI pipeline with MediaMTX integration, [5a-5d] highlights the different payment models (segment-based vs pixel-based), and [6a-6d] shows how a single gateway can operate in multiple modes simultaneously.
+### 1. Gateway Initialization - Dual Capability Setup
+Shows how a single Gateway node is initialized to handle both traditional transcoding and AI workloads simultaneously
+### 1a. AI Session Manager Field (`mediaserver.go:117`)
+Gateway server includes AI-specific session manager alongside traditional components
+```text
+AISessionManager *AISessionManager
+```
+### 1b. AI Manager Initialization (`mediaserver.go:196`)
+Creates AI session manager during server setup with TTL configuration
+```text
+AISessionManager: NewAISessionManager(lpNode, AISessionManagerTTL),
+```
+### 1c. Broadcast Session Manager (`mediaserver.go:545`)
+Creates traditional transcoding session manager for video streams
+```text
+sessManager = NewSessionManager(ctx, s.LivepeerNode, params)
+```
+### 1d. AI Media Server Start (`mediaserver.go:204`)
+Starts AI-specific media server endpoints alongside traditional RTMP/HLS
+```text
+if err := startAIMediaServer(ctx, ls); err != nil {
+```
+### 2. Traditional Video Transcoding Pipeline
+Traces the flow of video transcoding from RTMP ingest through segment processing to HLS output
+### 2a. RTMP Publish Handler Setup (`mediaserver.go:223`)
+Registers RTMP stream ingestion handlers for transcoding
+```text
+s.LPMS.HandleRTMPPublish(createRTMPStreamIDHandler(ctx, s, nil), gotRTMPStreamHandler(s), endRTMPStreamHandler(s))
+```
+### 2b. Segment Processing Trigger (`mediaserver.go:432`)
+Kicks off transcoding process for each video segment
+```text
+go processSegment(context.Background(), cxn, seg, nil)
+```
+### 2c. Orchestrator Selection (`broadcast.go:610`)
+Selects transcoding orchestrators based on capabilities and verification needs
+```text
+sessions, calcPerceptualHash, verified := bsm.selectSessions(ctx)
+```
+### 2d. Segment Submission (`broadcast.go:52`)
+Submits segment to multiple orchestrators for transcoding and verification
+```text
+submitMultiSession(ctx, sess, seg, segPar, nonce, calcPerceptualHash, resc)
+```
+### 3. AI Request Processing Pipeline
+Shows how AI requests are routed through the AI session manager to specialized orchestrators
+### 3a. AI Endpoint Registration (`ai_mediaserver.go:80`)
+Registers AI-specific HTTP endpoints for various model types
+```text
+ls.HTTPMux.Handle("/text-to-image", oapiReqValidator(aiMediaServerHandle(ls, jsonDecoder[worker.GenTextToImageJSONRequestBody], processTextToImage)))
+```
+### 3b. AI Session Manager Usage (`ai_mediaserver.go:123`)
+AI requests use the dedicated AI session manager instead of broadcast manager
+```text
+sessManager: ls.AISessionManager,
+```
+### 3c. AI Orchestrator Selection (`ai_session.go:489`)
+Selects orchestrators based on AI model capabilities and warm/cold status
+```text
+sess := sel.Select(ctx)
+```
+### 3d. AI Request Processing (`ai_process.go:145`)
+Processes AI request through selected orchestrator with model-specific logic
+```text
+resp, err := processAIRequest(ctx, params, req)
+```
+### 4. Live Video AI Pipeline - Real-time Processing
+Demonstrates the specialized live video-to-video AI workflow with real-time streaming
+### 4a. Live Video AI Endpoint (`ai_mediaserver.go:92`)
+Specialized endpoint for real-time video-to-video AI processing
+```text
+ls.HTTPMux.Handle("POST /live/video-to-video/{stream}/start", ls.StartLiveVideo())
+```
+### 4b. MediaMTX Integration (`ai_mediaserver.go:601`)
+Uses MediaMTX for real-time video segmentation and streaming
+```text
+ms.RunSegmentation(ctx, mediaMTXInputURL, ssr.Read)
+```
+### 4c. Live AI Request Construction (`ai_mediaserver.go:618`)
+Builds live video AI request with pipeline parameters
+```text
+req := worker.GenLiveVideoToVideoJSONRequestBody{
+```
+### 4d. Live Video Special Handling (`ai_session.go:222`)
+Special session selection logic for real-time video AI with latency optimization
+```text
+if cap == core.Capability_LiveVideoToVideo {
+```
+### 5. Payment Processing Differences
+Highlights the different payment models between transcoding (per segment) and AI (per pixel)
+### 5a. Segment-based Payment (`broadcast.go:54`)
+Traditional transcoding uses per-segment payment tickets
+```text
+go submitSegment(ctx, sess, seg, segPar, nonce, calcPerceptualHash, resc)
+```
+### 5b. Pixel-based Calculation (`ai_process.go:218`)
+AI payments calculated based on output pixel count
+```text
+outPixels := int64(*req.Height) * int64(*req.Width) * int64(*req.NumImagesPerPrompt)
+```
+### 5c. AI Payment Preparation (`ai_process.go:220`)
+Prepares pixel-based payment headers for AI requests
+```text
+setHeaders, balUpdate, err := prepareAIPayment(ctx, sess, outPixels)
+```
+### 5d. Live AI Payment Interval (`ai_mediaserver.go:589`)
+Live video AI uses interval-based payment processing
+```text
+paymentProcessInterval: ls.livePaymentInterval,
+```
+### 6. Gateway Node Type Configuration
+Shows how the gateway supports multiple node types and capabilities
+### 6a. Broadcaster Node Type (`mediaserver.go:164`)
+Gateway operates as broadcaster for traditional transcoding
+```text
+case core.BroadcasterNode:
+```
+### 6b. AI Worker Field (`mediaserver.go:122`)
+Node includes AI worker capabilities alongside traditional components
+```text
+AIWorker AI
+```
+### 6c. Gateway Host Configuration (`mediaserver.go:164`)
+Gateway-specific host configuration for routing
+```text
+GatewayHost string
+```
+### 6d. Dual Mode Activation (`mediaserver.go:201`)
+Enables both transcoding and AI capabilities when conditions are met
+```text
+if lpNode.NodeType == core.BroadcasterNode && httpIngest {
+```
\ No newline at end of file
diff --git a/v2/pages/04_gateways/_tests-to-delete/layouts.mdx b/v2/pages/04_gateways/_tests-to-delete/layouts.mdx
new file mode 100644
index 00000000..87241390
--- /dev/null
+++ b/v2/pages/04_gateways/_tests-to-delete/layouts.mdx
@@ -0,0 +1,171 @@
+
+### Layout 1
+
+
+ Check hardware, network, and software requirements.
+
+
+ You'll set up:
+ - API server
+ - Routing engine
+ - Capability registry
+ - Pricing configuration
+
+ Gateways can be deployed via:
+ - Docker
+ - Kubernetes
+ - Bare-metal services
+
+
+
+ Gateways select orchestrators based on:
+ - GPU type (A40, 4090, L40S, etc.)
+ - Model compatibility
+ - Performance metrics
+ - Reliability scores
+ - Pricing
+
+ Gateways must maintain active communication channels with orchestrator nodes.
+
+
+
+ Your Gateway must declare:
+ - Supported models (diffusion, ControlNet, IPAdapter)
+ - Supported pipelines (ComfyStream, Daydream, BYOC containers)
+ - Region/latency zones
+ - Fallback and load-balancing rules
+
+
+
+ Pricing can be:
+ - Per frame
+ - Per second
+ - Per inference run
+ - Per GPU-minute (BYOC)
+
+ Gateways publish pricing via Marketplace APIs.
+
+
+
+ Once configured, Gateways submit:
+ - Name
+ - Regions
+ - Pricing structure
+ - Supported models
+ - Supported pipelines
+ - Performance benchmarks
+ - SLA guarantees
+
+ This enables applications to discover and select your node.
+
+
+
+ Gateways must track:
+ - Routing accuracy
+ - Latency
+ - Throughput
+ - Orchestrator stability
+
+ This ensures competitive placement in the Marketplace.
+
+
+
+
+
+### Layout 2 & 3
+
+
+```mermaid
+%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui' }}}%%
+flowchart TB
+ subgraph reqs["Pre-Reqs"]
+ A["Check Hardware Requirements"]
+ B["Check Network & Software Requirements"]
+ end
+
+ subgraph setup["Setup"]
+ C["Deploy Gateway Service"]
+ D["Connect to Orchestrators"]
+ end
+
+ subgraph config["Configuration"]
+ E["Configure Capabilities"]
+ F["Set Pricing"]
+ end
+
+ subgraph launch["Launch"]
+ G["Register in Marketplace"]
+ H["Monitor & Optimize"]
+ end
+
+ A --> B
+ B --> C
+ C --> D
+ D --> E
+ E --> F
+ F --> G
+ G --> H
+
+ classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px
+ style reqs fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style setup fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style config fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style launch fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+```
+
+
+
+
+ Check hardware, network, and software requirements.
+
+
+
+ Install the Livepeer Gateway software, deploy & connect to orchestrators.
+
+
+
+ Configure models, pipelines, regions, pricing, and more.
+
+
+
+ Price & publish offerings to the Marketplace.
+
+
+
+ Monitor performance, optimize routing & service quality.
+
+
+
+
+
+
+
+### Layout 4
+
+ ### Requirements
+
+ ### Setup
+
+
+ ### Configuration
+
+
+ ### Launch
+
+
+
diff --git a/v2/pages/04_gateways/_tests-to-delete/random-copy.mdx b/v2/pages/04_gateways/_tests-to-delete/random-copy.mdx
new file mode 100644
index 00000000..08f59b33
--- /dev/null
+++ b/v2/pages/04_gateways/_tests-to-delete/random-copy.mdx
@@ -0,0 +1,14 @@
+
+
+Orchestrators are GPU operators who execute the actual workload—transcoding, AI inference, or BYOC containers. Gateways route jobs _to_ orchestrators, collect results, and return them to the application.
+
+**Applications → Gateway → Orchestrator → Gateway → Application**
+
+This separation allows:
+
+- Clean abstraction for developers
+- Efficient load balancing
+- Competition and specialization across operators
+- Support for a broad range of real-time AI pipelines
+
+
\ No newline at end of file
diff --git a/v2/pages/04_gateways/_tests-to-delete/why.mdx b/v2/pages/04_gateways/_tests-to-delete/why.mdx
new file mode 100644
index 00000000..e26a6343
--- /dev/null
+++ b/v2/pages/04_gateways/_tests-to-delete/why.mdx
@@ -0,0 +1,196 @@
+#### Direct Usage & Platform Integration
+| Category | Reason | Business Explanation |
+| ------------------ | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| Direct Usage / Ops | Run your own workloads | Content providers run gateways to process their own video/AI workloads end-to-end, controlling ingestion, routing, retries, and delivery. |
+
+#### Reliability, Performance & QoS
+| Category | Reason | Business Explanation |
+| ----------- | ---------------------------------- | ----------------------------------------------------------------------------------------------------- |
+| Reliability | Enforce SLAs on orchestrators | Gateways select orchestrators, apply retries/failover, and enforce latency and uptime guarantees. |
+| Reliability | QoS enforcement & workload shaping | Gateways control routing, retries, failover, and latency-vs-cost trade-offs beyond protocol defaults. |
+
+#### Platform
+| Category | Reason | Business Explanation |
+| -------- | ------------------------- | ------------------------------------------------------------------------------- |
+| Platform | Embed in a larger product | Gateways act as internal infrastructure powering broader media or AI platforms. |
+
+#### Economics
+| Category | Reason | Business Explanation |
+| --------- | ------------------------------ | ------------------------------------------------------------------------------------------------------- |
+| Economics | Service-layer monetization | Service providers charge end users above orchestrator cost for reliability, compliance, or convenience. |
+| Economics | Avoid third-party gateway fees | Running your own gateway avoids routing fees, pricing risk, and policy constraints imposed by others. |
+
+#### Demand Control & Traffic Ownership
+| Category | Reason | Business Explanation |
+| -------------- | -------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
+| Demand Control | Demand aggregation & traffic ownership | Gateways own ingress, customer relationships, usage data, and traffic predictability across apps or customers. |
+| Demand Control | Workload normalization | Gateways smooth bursty demand into predictable, orchestrator-friendly workloads. |
+
+#### Performance
+| Category | Reason | Business Explanation |
+| ----------- | --------------------------- | --------------------------------------------------------------------------------------------------- |
+| Performance | Geographic request steering | Gateways route users to regionally optimal orchestrators to reduce latency and improve reliability. |
+
+#### Security & Compliance
+| Category | Reason | Business Explanation |
+| -------- | --------------------------------- | ------------------------------------------------------------------------------------------ |
+| Security | Enterprise policy enforcement | Gateways enforce IP allowlists, auth, rate limits, audit logs, and deterministic behavior. |
+| Security | Cost-explosion & abuse protection | Gateways block buggy or malicious clients before they generate runaway compute costs. |
+
+#### Product Differentiation & UX
+| Category | Reason | Business Explanation |
+| -------- | -------------------------------------- | ------------------------------------------------------------------------------------------------------- |
+| Product | Product differentiation above protocol | Custom APIs, SDKs, dashboards, billing abstractions, and AI workflow presets live at the gateway layer. |
+| Product | Stable API surface | Gateways shield customers from protocol or orchestrator churn via versioning and controlled change. |
+
+#### Observability & Feedback Loops
+| Category | Reason | Business Explanation |
+| ------------- | -------------------------- | ------------------------------------------------------------------------------------------------------ |
+| Observability | Analytics & feedback loops | Gateways see end-to-end request patterns, failures, latency, model performance, and customer behavior. |
+
+#### Strategy, Optionality & Ecosystem Power
+| Category | Reason | Business Explanation |
+| -------- | ---------------------- | -------------------------------------------------------------------------------------------------------- |
+| Strategy | Strategic independence | Running your own gateway avoids pricing, roadmap, availability, and censorship risk from other gateways. |
+| Strategy | Future optionality | Early gateway operators gain leverage if incentives or network economics evolve. |
+
+#### Ecosystem Influence
+| Category | Reason | Business Explanation |
+| --------- | ------------------- | -------------------------------------------------------------------------------------------------------------------- |
+| Ecosystem | Ecosystem influence | Gateways sit at a coordination choke-point that shapes standards, surfaces protocol gaps, and influences real usage. |
+
+
+
+
+
+
+
+
+
+
Category
+
Reason
+
Business Explanation
+
+
+
+
+
Direct Usage & Platform Integration
+
+
+
Direct Usage / Ops
+
Run your own workloads
+
Content providers run gateways to process their own video/AI workloads end-to-end, controlling ingestion, routing, retries, and delivery.
+
+
+
Reliability, Performance & QoS
+
+
+
Reliability
+
Enforce SLAs on orchestrators
+
Gateways select orchestrators, apply retries/failover, and enforce latency and uptime guarantees.
+
+
+
Reliability
+
QoS enforcement & workload shaping
+
Gateways control routing, retries, failover, and latency-vs-cost trade-offs beyond protocol defaults.
+
+
+
Platform
+
+
+
Platform
+
Embed in a larger product
+
Gateways act as internal infrastructure powering broader media or AI platforms.
+
+
+
Economics
+
+
+
Economics
+
Service-layer monetization
+
Service providers charge end users above orchestrator cost for reliability, compliance, or convenience.
+
+
+
Economics
+
Avoid third-party gateway fees
+
Running your own gateway avoids routing fees, pricing risk, and policy constraints imposed by others.
+
+
+
Demand Control & Traffic Ownership
+
+
+
Demand Control
+
Demand aggregation & traffic ownership
+
Gateways own ingress, customer relationships, usage data, and traffic predictability across apps or customers.
+
+
+
Demand Control
+
Workload normalization
+
Gateways smooth bursty demand into predictable, orchestrator-friendly workloads.
+
+
+
Performance
+
+
+
Performance
+
Geographic request steering
+
Gateways route users to regionally optimal orchestrators to reduce latency and improve reliability.
+
+
+
Security & Compliance
+
+
+
Security
+
Enterprise policy enforcement
+
Gateways enforce IP allowlists, auth, rate limits, audit logs, and deterministic behavior.
+
+
+
Security
+
Cost-explosion & abuse protection
+
Gateways block buggy or malicious clients before they generate runaway compute costs.
+
+
+
Product Differentiation & UX
+
+
+
Product
+
Product differentiation above protocol
+
Custom APIs, SDKs, dashboards, billing abstractions, and AI workflow presets live at the gateway layer.
+
+
+
Product
+
Stable API surface
+
Gateways shield customers from protocol or orchestrator churn via versioning and controlled change.
+
+
+
Observability & Feedback Loops
+
+
+
Observability
+
Analytics & feedback loops
+
Gateways see end-to-end request patterns, failures, latency, model performance, and customer behavior.
+
+
+
Strategy, Optionality & Ecosystem Power
+
+
+
Strategy
+
Strategic independence
+
Running your own gateway avoids pricing, roadmap, availability, and censorship risk from other gateways.
+
+
+
Strategy
+
Future optionality
+
Early gateway operators gain leverage if incentives or network economics evolve.
+
+
+
Ecosystem Influence
+
+
+
Ecosystem
+
Ecosystem influence
+
Gateways sit at a coordination choke-point that shapes standards, surfaces protocol gaps, and influences real usage.
+
+
+
+
diff --git a/v2/pages/04_gateways/about-gateways/gateway-architecture.mdx b/v2/pages/04_gateways/about-gateways/gateway-architecture.mdx
new file mode 100644
index 00000000..a725451f
--- /dev/null
+++ b/v2/pages/04_gateways/about-gateways/gateway-architecture.mdx
@@ -0,0 +1,120 @@
+---
+title: 'Gateway Architecture'
+sidebarTitle: 'Gateway Architecture'
+---
+
+
+ This page is a work in progress.
+ TODO: Overview, Edit, Streamline, Format, Style, Link to github / other
+ resources
+
+
+import { ScrollableDiagram } from '/snippets/components/zoomable-diagram.jsx'
+import { DoubleIconLink } from '/snippets/components/links.jsx'
+
+Livepeer Gateway Architecture is defined in the livepeer-go core codebase.
+
+
+## Gateway Technical Architecture
+
+
+```mermaid
+%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui' }}}%%
+flowchart TB
+ subgraph INPUT["Input Sources"]
+ direction LR
+ RTMP["RTMP Stream"]
+ HTTP["HTTP Upload"]
+ AI_REQ["AI Request"]
+ end
+
+ GATEWAY["Gateway Node LivepeerNode"]
+
+ INPUT --> GATEWAY
+
+ subgraph MANAGERS["Session Managers"]
+ direction LR
+ BSM["BroadcastSessionsManager Video Transcoding"]
+ ASM["AISessionManager AI Processing"]
+ end
+
+ GATEWAY --> BSM
+ GATEWAY --> ASM
+
+ subgraph VIDEO["Video Pipeline"]
+ SEG["Segment Processing"]
+ ORCH_V["Orchestrators Transcoding"]
+ HLS["HLS/DASH Output"]
+ end
+
+ subgraph AI["AI Pipeline"]
+ PROC["AI Processing"]
+ ORCH_AI["Orchestrators AI Models"]
+ OUT_AI["AI Output Images/Video"]
+ end
+
+ BSM --> SEG --> ORCH_V --> HLS
+ ASM --> PROC --> ORCH_AI --> OUT_AI
+
+ subgraph PAYMENT["Payment"]
+ direction LR
+ PAY_SEG["Per Segment"]
+ PAY_PIX["Per Pixel"]
+ end
+
+ ORCH_V --> PAY_SEG
+ ORCH_AI --> PAY_PIX
+
+ classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px
+ classDef video fill:#1a1a1a,color:#fff,stroke:#3b82f6,stroke-width:2px
+ classDef ai fill:#1a1a1a,color:#fff,stroke:#a855f7,stroke-width:2px
+ class RTMP,HTTP,BSM,SEG,ORCH_V,HLS,PAY_SEG video
+ class AI_REQ,ASM,PROC,ORCH_AI,OUT_AI,PAY_PIX ai
+ style INPUT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style MANAGERS fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style VIDEO fill:#0d0d0d,stroke:#3b82f6,stroke-width:1px
+ style AI fill:#0d0d0d,stroke:#a855f7,stroke-width:1px
+ style PAYMENT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+```
+
+
+
+### Flow Diagram
+
+
+ (Daydream, ComfyUI, BYOC)"] -->|Job Request| B["Gateway Job Intake, Pricing, Capability Match"]
+ B -->|Route Job| C["Orchestrator GPU Compute, AI Inference, Transcoding"]
+ C -->|Results| B
+ B -->|Response| A `}
+ />
+
+
+
+
+### Layered Architecture
+
+(Web, Mobile, TouchDesigner)"]
+ end
+ subgraph GW[Gateway Layer]
+ G1[Job Intake]
+ G2[Capability Discovery]
+ G3[Pricing & Marketplace]
+ G4[Routing / Scheduling]
+ end
+ subgraph ORC[Orchestrator Layer]
+ O1[GPU Worker]
+ O2[AI Models / BYOC Containers]
+ O3[Transcoder]
+ end
+ X --> G1
+ G1 --> O1
+ O1 --> G1
+ G1 --> X `}
+/>
+
diff --git a/v2/pages/04_gateways/about-gateways/gateway-economics.mdx b/v2/pages/04_gateways/about-gateways/gateway-economics.mdx
new file mode 100644
index 00000000..c5cff91c
--- /dev/null
+++ b/v2/pages/04_gateways/about-gateways/gateway-economics.mdx
@@ -0,0 +1,141 @@
+---
+title: 'Gateway Economics'
+description: 'Learn about the economics of running a Livepeer Gateway'
+sidebarTitle: 'Gateway Economics'
+---
+
+# Gateway Economics in Livepeer
+Gateways in Livepeer do not earn money at the _protocol level_ (though they can earn money at the _business application level_).
+
+Livepeer follows a service provider model where gateways are customers purchasing media & AI processing services from the network.
+The actual protocol-level earners are orchestrators, transcoders, AI workers, and redeemers who provide the computational work
+and blockchain services.
+
+**The Payment Flow**
+
+In Livepeer's economic model, gateways are consumers of media processing services:
+
+- Gateways pay Orchestrators for transcoding/AI work via payment tickets
+- Orchestrators pay Transcoders/AI Workers who perform the actual work
+- Redeemers earn fees by redeeming winning payment tickets on-chain
+
+## Who Actually Earns Money?
+
+
+
+
+
+
Node Type
+
How They Earn Money
+
+
+
+
+
Orchestrator
+
Receives payments from gateways for coordinating work
+
+
+
Transcoder
+
Gets paid by orchestrators for video transcoding work
+
+
+
AI Worker
+
Gets paid by orchestrators for AI model inference
+
+
+
Redeemer
+
Earns fees for redeeming winning tickets on blockchain
+
+
+
Gateway
+
PAYS for services (does not earn)
+
+
+
+
+
+### Gateway Costs
+Gateways incur costs for:
+
+- Video transcoding: Per segment based on pixels processed
+- AI processing: Per pixel based on output dimensions
+- Live AI video: Interval-based payments during streaming
+
+### Why Run a Gateway?
+If gateways don't earn money, why run one?
+
+- Running your own Gateway means you do not pay a fee to route through another party's Gateway
+- Content providers run gateways to process their own video/AI content and ensure SLAs on their Orchestrators.
+- Service providers may charge end-users higher rates than what they pay Orchestrators as service fees
+- Integrated platforms use gateways as part of larger media services
+
+## Gateways Arbitrage Earnings
+Gateways make money through business arbitrage:
+
+- Content providers pay gateways for video/AI processing services
+- Gateways pay orchestrators for the actual computational work
+
+The difference is the gateway's profit margin
+
+## Gateway Fee Structure
+
+As a gateway operator, you don't set protocol-level "fees" in Livepeer - you set **business pricing** at the application layer.
+The protocol only controls what you **pay** orchestrators, not what you **charge** customers.
+
+### Protocol-Level Costs (What You Pay)
+
+You control your costs through these configuration flags [1](#10-0) :
+
+```bash
+# Maximum you'll pay per pixel for transcoding
+-maxPricePerUnit=1000
+
+# Maximum you'll pay per AI capability/model
+-maxPricePerCapability='{"capabilities_prices": [{"pipeline": "text-to-image", "model_id": "stabilityai/sd-turbo", "price_per_unit": 1000}]}'
+```
+
+### Business-Level Pricing (What You Charge)
+
+Your actual fees to end-users are set at the application layer, outside the Livepeer protocol.
+
+Common approaches include:
+1. **Per-request pricing**: Charge per API call to your gateway
+2. **Usage-based pricing**: Charge per minute of video or per AI generation
+3. **Subscription models**: Monthly fees for access to your gateway services
+
+### Implementation Example
+
+Here's how you'd implement pricing logic in your application:
+
+```go
+// Your application code (not in Livepeer protocol)
+func calculateUserPrice(requestType string, pixels int64) float64 {
+ basePrice := getYourBusinessPrice(requestType)
+ yourCost := getOrchestratorCost(pixels)
+ profitMargin := 0.20 // 20% margin
+
+ return basePrice + yourCost*profitMargin
+}
+```
+
+### Price Discovery
+
+Use the CLI to discover orchestrator prices and set your margins:
+
+```bash
+livepeer_cli
+# Select "Set broadcast config" to see current market rates
+# Then set your max prices accordingly
+```
+
+Your "fee" is the difference between what customers pay you and what you pay orchestrators for processing.
+
+
+### Case Study: Streamplace
+[Streamplace](https://stream.place) is a gateway that provides video processing services to content creators.
+Creators pay Streamplace for video processing, and Streamplace pays orchestrators for the actual work.
+Streamplace's profit margin is the difference between what creators pay and what it pays orchestrators.
+
+[Daydream](https://daydream.live) is another example of a gateway that provides AI video processing services.
+Builders & Creators pay Daydream for AI video processing, and Daydream pays orchestrators for the actual work.
+Daydream's profit margin is the difference between what creators pay and what it pays orchestrators.
diff --git a/v2/pages/04_gateways/about-gateways/gateway-explainer.mdx b/v2/pages/04_gateways/about-gateways/gateway-explainer.mdx
new file mode 100644
index 00000000..3cb3b09c
--- /dev/null
+++ b/v2/pages/04_gateways/about-gateways/gateway-explainer.mdx
@@ -0,0 +1,191 @@
+---
+title: Gateway Explainer
+sidebarTitle: Gateway Explainer
+---
+
+import { GotoCard } from '/snippets/components/links.jsx'
+
+
+ This page is a work in progress.
+ TODO: Edit, Streamline, Format & Style
+
+
+## Definition
+Gateways serve as the primary demand aggregation layer in the Livepeer network.
+They accept video transcoding and AI inference requests from end customers, then distribute these jobs across the network of GPU-equipped Orchestrators.
+In earlier Livepeer documentation, this role was referred to as a broadcaster.
+
+## What is a Gateway?
+
+Gateways are the entry point for applications into the Livepeercompute network.
+They are the coordination layer that connects real-time AI
+and video workloads to the orchestrators who perform the GPU compute.
+
+They operate as the essential technical layer between the protocol and
+the distributed compute network.
+
+A gateway is a self-operated Livepeer node that interacts directly with orchestrators, submits jobs, handles payment, and exposes direct protocol interfaces.
+Hosted services like Daydream are not gateways.
+
+A Gateway is responsible for
+- validating requests
+- selecting Workers
+- translating requests into Worker OpenAPI calls
+- aggregating results
+
+Gateways earn revenue from transaction fees on all jobs they route.
+
+If you are coming from an Ethereum background, Gateways could loosely be thought of as sequencers in L2 rollups.
+If you are coming from a traditional cloud background, Gateways are akin to API gateways or load balancers.
+
+Anyone that wants to build applications and services (like [Daydream] and [Stream.place] ) on top of the Livepeer
+protocol will build their own Gateway in order to offer their services to Livepeer Developers, Builders & end-users and enable
+communication of their application with the Livepeer GPU network (DePIN / Orchestrators)
+
+
+## What Gateways Do
+
+Gateways handle all service-level logic required to operate a scalable, low-latency AI video network:
+
+- **Job Intake**
+ They receive workloads from applications using Livepeer APIs, PyTrickle, or BYOC integrations.
+
+- **Capability & Model Matching**
+ Gateways determine which orchestrators support the required GPU, model, or pipeline.
+
+- **Routing & Scheduling**
+ They dispatch jobs to the optimal orchestrator based on performance, availability, and pricing.
+
+- **Marketplace Exposure**
+ Gateway operators can publish the services they offer, including supported models, pipelines, and pricing structures.
+
+Gateways do _not_ perform GPU compute. Instead, they focus on coordination and service routing.
+
+
+
+## Why Gateways Matter
+
+As Livepeer transitions into a high-demand, real-time AI network, Gateways become essential infrastructure.
+
+They enable:
+- Low-latency workflows for Daydream, ComfyStream, and other real-time AI video tools
+- Dynamic GPU routing for inference-heavy workloads
+- A decentralized marketplace of compute capabilities
+- Flexible integration via the BYOC pipeline model
+
+Gateways simplify the developer experience while preserving the decentralization, performance, and competitiveness of the Livepeer network.
+
+## Summary
+
+Gateways are the coordination and routing layer of the Livepeer ecosystem. They expose capabilities, price services, accept workloads,
+and dispatch them to orchestrators for GPU execution. This design enables a scalable, low-latency, AI-ready decentralized compute marketplace.
+
+This architecture enables Livepeer to scale into a global provider of real-time AI video infrastructure.
+
+---
+
+---
+
+---
+
+---
+
+ WIP: Unsure where below section belongs currently
+
+
+ ## Key Marketplace Features
+
+ ### 1. Capability Discovery
+
+ Gateways and orchestrators list:
+
+ - AI model support
+ - Versioning and model weights
+ - Pipeline compatibility
+ - GPU type and compute class
+
+ Applications can programmatically choose the best provider.
+
+ ### 2. Dynamic Pricing
+
+ Pricing can vary by:
+
+ - GPU class
+ - Model complexity
+ - Latency SLA
+ - Throughput requirements
+ - Region
+
+ Gateways expose pricing APIs for transparent selection.
+
+ ### 3. Performance Competition
+
+ Orchestrators compete on:
+
+ - Speed
+ - Reliability
+ - GPU quality
+ - Cost efficiency
+
+ Gateways compete on:
+
+ - Routing quality
+ - Supported features
+ - Latency
+ - Developer ecosystem fit
+
+ This creates a healthy decentralized market.
+
+ ### 4. BYOC Integration
+
+ Any container-based pipeline can be brought into the marketplace:
+
+ - Run custom AI models
+ - Run ML workflows
+ - Execute arbitrary compute
+ - Support enterprise workloads
+
+ Gateways advertise BYOC offerings; orchestrators execute containers.
+
+
+
+ ## Marketplace Benefits
+
+ - **Developer choice** — choose the best model, price, and performance
+ - **Economic incentives** — better nodes earn more work
+ - **Scalability** — network supply grows independently of demand
+ - **Innovation unlock** — new models and pipelines can be added instantly
+ - **Decentralization** — no single operator controls the workload flow
+
+ ## Summary
+
+ The Marketplace turns Livepeer into a competitive, discoverable, real-time AI compute layer.
+
+ - Gateways expose services
+ - Orchestrators execute them
+ - Applications choose the best fit
+ - Developers build on top of it
+ - Users benefit from low-latency, high-performance AI
+
+
+# References
+
+ Unverified Reference
+https://github.com/videoDAC/livepeer-gateway
+
+
\ No newline at end of file
diff --git a/v2/pages/04_gateways/about-gateways/gateway-functions.mdx b/v2/pages/04_gateways/about-gateways/gateway-functions.mdx
new file mode 100644
index 00000000..6927bab5
--- /dev/null
+++ b/v2/pages/04_gateways/about-gateways/gateway-functions.mdx
@@ -0,0 +1,95 @@
+---
+title: 'Gateway Functions & Services'
+description: 'Learn about the key functions and services provided by Livepeer Gateways.'
+sidebarTitle: 'Gateway Functions'
+---
+
+
+ This page is a work in progress.
+ TODO: Proper copy, edit, Streamline, Format & Style
+
+
+## What a Gateway Operator Does
+
+Gateway operators handle:
+
+- Job intake and API requests
+- Routing workloads to the best Orchestrator (GPU Node)
+- Managing pricing, capabilities, and service metadata
+- Publishing offerings (AI inference, video transcoding and more) to the Marketplace
+- Monitoring job performance, latency, and reliability
+
+Gateways do **not** compute or perform the AI inference or transcoding themselves.
+That work is performed by orchestrators.
+
+
+
+## Key Marketplace Features
+
+### 1. Capability Discovery
+
+Gateways and orchestrators list:
+
+- AI model support
+- Versioning and model weights
+- Pipeline compatibility
+- GPU type and compute class
+
+Applications can programmatically choose the best provider.
+
+### 2. Dynamic Pricing
+
+Pricing can vary by:
+
+- GPU class
+- Model complexity
+- Latency SLA
+- Throughput requirements
+- Region
+
+Gateways expose pricing APIs for transparent selection.
+
+### 3. Performance Competition
+
+Orchestrators compete on:
+
+- Speed
+- Reliability
+- GPU quality
+- Cost efficiency
+
+Gateways compete on:
+
+- Routing quality
+- Supported features
+- Latency
+- Developer ecosystem fit
+
+This creates a healthy decentralized market.
+
+### 4. BYOC Integration
+
+Any container-based pipeline can be brought into the marketplace:
+
+- Run custom AI models
+- Run ML workflows
+- Execute arbitrary compute
+- Support enterprise workloads
+
+Gateways advertise BYOC offerings; orchestrators execute containers.
+
+## Marketplace Benefits
+
+- **Developer choice** — choose the best model, price, and performance
+- **Economic incentives** — better nodes earn more work
+- **Scalability** — network supply grows independently of demand
+- **Innovation unlock** — new models and pipelines can be added instantly
+- **Decentralization** — no single operator controls the workload flow
+
+## Summary
+
+The Marketplace turns Livepeer into a competitive, discoverable, real-time AI compute layer.
+
+- Gateways expose services
+- Orchestrators execute them
+- Applications choose the best fit
diff --git a/v2/pages/04_gateways/about-gateways/overview.mdx b/v2/pages/04_gateways/about-gateways/overview.mdx
new file mode 100644
index 00000000..368c00a0
--- /dev/null
+++ b/v2/pages/04_gateways/about-gateways/overview.mdx
@@ -0,0 +1,33 @@
+---
+title: 'Gateways Overview'
+sidebarTitle: 'Overview'
+tag: Start Here
+description: 'An overview of the Livepeer Gateway role'
+---
+ WIP: This page needs work - roll explainer into this page
+
+Definition of a Gateway
+
+This section is for those folks looking to ...
+
+
+## Choose your own adventure
+
+
+
+ See how to run a Gateway on the Livepeer Network.
+
+
+ See how to use a Gateway on the Livepeer Network.
+
+
diff --git a/v2/pages/04_gateways/gateway-tools/explorer.mdx b/v2/pages/04_gateways/gateway-tools/explorer.mdx
new file mode 100644
index 00000000..939828a6
--- /dev/null
+++ b/v2/pages/04_gateways/gateway-tools/explorer.mdx
@@ -0,0 +1,49 @@
+---
+title: Gateway Explorer
+description: View gateway data on the Explorer
+sidebarTitle: Gateway Explorer
+---
+
+
+ This page is a work in progress. TODO: Explain the data on gateways
+
+
+import { GotoLink, GotoCard } from '/snippets/components/links.jsx'
+
+
+ Coming Soon! Gateways on Livepeer Explorer is currently in development.
+
+
+
+ {' '}
+ Livepeer Gateway Explorer
+
+ }
+ href="https://explorer-arbitrum-one-git-feat-add-g-10dba1-livepeer-foundation.vercel.app/"
+ arrow="true"
+ cta="Visit the Gateway Explorer"
+>
+
+
+
+## About The Gateway Data
+
+TODO
+
+## Explorer Codebase
+
+Livepeer is committed to open-source development. If you want to dig deep into the code or you're interested in
+contributing to the Explorer, you can find the codebase on GitHub.
+
+
diff --git a/v2/pages/04_gateways/gateway-tools/livepeer-tools.mdx b/v2/pages/04_gateways/gateway-tools/livepeer-tools.mdx
new file mode 100644
index 00000000..e1fc95b4
--- /dev/null
+++ b/v2/pages/04_gateways/gateway-tools/livepeer-tools.mdx
@@ -0,0 +1,46 @@
+---
+title: Livepeer Tools Dashboard
+description: Livepeer Tools
+sidebarTitle: Livepeer Tools
+---
+
+This page is a work in progress.
+
+import { GotoCard } from '/snippets/components/links.jsx'
+
+Livepeer Tools is a dashboard for monitoring and managing Livepeer gateways. It provides a user-friendly interface for viewing gateway performance metrics, managing gateway configurations, and troubleshooting issues.
+https://www.livepeer.tools/gateways
+
+
+ {' '}
+ Cloud SPE Gateway Explorer
+
+ }
+ href="https://www.livepeer.tools/gateways"
+ arrow="true"
+ cta="Visit The Cloud SPE Gateway Explorer"
+>
+
+
+
+## About The Gateway Data
+
+TODO
+
+## Explorer Codebase
+
+Livepeer is committed to open-source development. If you want to dig deep into the code or you're interested in
+contributing to the Explorer, you can find the codebase on GitHub.
+
+
diff --git a/v2/pages/04_gateways/gateways-home.mdx b/v2/pages/04_gateways/gateways-home.mdx
new file mode 100644
index 00000000..c6e699af
--- /dev/null
+++ b/v2/pages/04_gateways/gateways-home.mdx
@@ -0,0 +1,217 @@
+---
+title: 'Gateway Portal'
+sidebarTitle: 'Gateway Home'
+tag: Start Here
+description: 'Welcome To The Gateway Portal: Explore, Navigate, Create'
+---
+
+import { ScrollableDiagram } from '/snippets/components/zoomable-diagram.jsx'
+import { BlinkingIcon } from '/snippets/components/links.jsx'
+
+ In earlier Livepeer documentation, Gateways were referred to as Broadcasters
+
+
+## Gateway Portal: Map
+
+Gateways serve as the primary demand aggregation layer in the Livepeer network.
+They accept video transcoding and AI inference requests from end customers, then distribute these jobs across the network of GPU-equipped Orchestrators.
+
+**Mental Model**
+
+
+
+
+ Running a Gateway is similar to operating an API Gateway or Load Balancer in cloud computing —
+ it ingests traffic, routes workloads to backend GPU nodes, and manages session flow
+ without doing the heavy compute itself.
+
+
+
+ ```mermaid
+ %%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui' }}}%%
+ flowchart LR
+ subgraph Clients["Client / Application Layer"]
+ A["Apps & SDKs • Video Ingest • AI Inference Requests • WebRTC / HTTP"]
+ end
+
+ subgraph Gateway["Gateway Layer (Livepeer Gateway)"]
+ B["Gateway Node
Cloud Analogy: • API Gateway • L7 Load Balancer • Control Plane
• Payments • Accounting • Slashing / Security"]
+ end
+
+ A -->|Requests| B
+ B -->|Dispatch Jobs| C
+ C -->|Results / Streams| B
+ B -->|Responses| A
+ C -->|Usage & Proof| D
+
+ classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px
+ style Clients fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style Gateway fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style Compute fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style Settlement fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ ```
+
+
+
+
+
+ Running a Gateway is **not** like running a validator on Ethereum.
+ Validators secure consensus whereas Gateways route workloads. It's more akin to a Sequencer on a Layer 2.
+ Just as a Sequencer ingests user transactions, orders them, and routes them into the rollup execution layer,
+ a Livepeer Gateway performs the same function for the Livepeer compute network.
+
+
+
+ ```mermaid
+ %%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui' }}}%%
+ flowchart LR
+ subgraph User["User Layer"]
+ A["Client Video/AI Request"]
+ end
+
+ subgraph Gateway["Gateway Layer"]
+ B["Livepeer Gateway = L2 Sequencer
= L2 Execution Layer"]
+ end
+
+ subgraph Settlement["Settlement Layer"]
+ D["Ethereum Consensus & Payment Security"]
+ end
+
+ A --> B
+ B --> C
+ C --> B
+ B --> A
+ C --> D
+
+ classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px
+ style User fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style Gateway fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style Compute fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style Settlement fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ ```
+
+
+
+
+
+ For the rest of us, running a Gateway is like being a film producer.
+ You take a request, assemble the right specialists, manage constraints,
+ and ensure the final result is delivered reliably—without doing every task yourself.
+
+
+
+ ```mermaid
+ %%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui' }}}%%
+ flowchart LR
+ subgraph Persona["Persona: Gateway Operator = Film Producer"]
+ P["Film Producer Mindset • Owns delivery • Sets constraints • Chooses specialists • Ensures quality"]
+ end
+
+ subgraph Request["Act I — The Pitch"]
+ A["Incoming Request • Live Video Stream • AI Inference Job • Quality & Latency Requirements"]
+ end
+
+ subgraph Planning["Act II — Pre-Production"]
+ B["Gateway (Producer)
• Interpret the request • Set budget & latency constraints • Choose specialists • Plan execution"]
+ end
+
+ subgraph Crew["Act III — Production Crew"]
+ C["Orchestrators / GPU Workers
• Transcoding • AI Inference • Real-time Processing"]
+ end
+
+ subgraph Delivery["Act IV — Final Cut & Release"]
+ D["Verified Output • Stream / AI Result • Quality checked • Delivered on time"]
+ end
+
+ subgraph Settlement["Credits & Accounting"]
+ E["Onchain Settlement • Usage recorded • Payments distributed • Trust enforced"]
+ end
+
+ P --> A
+ A --> B
+ B --> C
+ C --> B
+ B --> D
+ C --> E
+
+ classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px
+ style Persona fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style Request fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style Planning fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style Crew fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style Delivery fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style Settlement fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ ```
+
+
+
+
+
+
+## Gateway Portal: Choose Your Mission
+
+ Your Journey Starts Here
+
+
+
+ What? Where Am I? What's a Gateway?
+ Why do I need one?
+
+
+ Find Video and AI Services available via Gateways on the Livepeer Network.
+
+
+ Developer Level Up
+
+ Deploy your own Gateway on the Livepeer Protocol - no GPU required!
+
+
+ Tools and Dashboards to help find and manage Gateways -> for users and operators.
+
+
+ Full guides, examples and tutorials on running a Livepeer Gateway node.
+
+
+ All your Gateway questions answered.
+
+
+
+---
+
+
+ Remove me?
+## Gateway Launch Pad
+Jump to
+- [What's a Gateway?](#whats-a-gateway)
+- [Gateway Services & Providers](#gateway-services--providers)
+- [Run a Gateway](#run-a-gateway)
+- [Gateway Tools & Dashboards](#gateway-tools--dashboards)
+- [Gateway Guides & Resources](#gateway-guides--resources)
+- [Gateway FAQ Emporium](#gateway-faq-emporium)
\ No newline at end of file
diff --git a/v2/pages/04_gateways/guides-and-resources/community-guides.mdx b/v2/pages/04_gateways/guides-and-resources/community-guides.mdx
new file mode 100644
index 00000000..56bccaca
--- /dev/null
+++ b/v2/pages/04_gateways/guides-and-resources/community-guides.mdx
@@ -0,0 +1,6 @@
+---
+title: Community Guides
+sidebarTitle: Community Guides
+description: Community guides for running a Livepeer Gateway
+keywords: [community, guides, gateway]
+---
diff --git a/v2/pages/04_gateways/guides-and-resources/community-projects.mdx b/v2/pages/04_gateways/guides-and-resources/community-projects.mdx
new file mode 100644
index 00000000..35a33b90
--- /dev/null
+++ b/v2/pages/04_gateways/guides-and-resources/community-projects.mdx
@@ -0,0 +1,5 @@
+---
+title: Community Projects
+description: A list of community projects making running a gateway easy!
+sidebarTitle: Community Resources
+---
diff --git a/v2/pages/04_gateways/guides-and-resources/faq.mdx b/v2/pages/04_gateways/guides-and-resources/faq.mdx
new file mode 100644
index 00000000..54d8c330
--- /dev/null
+++ b/v2/pages/04_gateways/guides-and-resources/faq.mdx
@@ -0,0 +1,100 @@
+---
+title: 'Gateway FAQ'
+sidebarTitle: 'FAQ'
+description: 'Gateway Frequently Asked Questions'
+---
+
+
+ This is a brainstroming FAQ page. Not finalised.
+
+
+# FAQ
+
+1) How is pricing done?
+
+Orchestrators set pricing per pixel in Wei, advertised off-chain to gateways.
+
+Livepeer docs do not contain an official gateway marketplace pricing guide; gateway providers/operators set prices themselves. (Verified absence)
+
+2) Can Gateway Operators add new AI inference endpoints?
+
+Operators can run AI gateways and expose inference endpoints; orchestrators advertise their AI service URI on-chain for routing.
+
+There is no formal documented “BYOC pipeline” for registering custom models — it comes from running the gateway’s API. (Verified absence)
+
+3) Is there a way to see all marketplace offerings from gateways?
+
+No official centralized marketplace exists in Livepeer docs. Third-party portals/communities may list offerings. (Verified absence)
+
+
+## Gateway Pricing References & Resources
+
+### Deep references related to Gateway pricing, orchestration economics, and marketplace visibility
+
+| Link Name | Hyperlink location | Link Summary of Content |
+| ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
+| Livepeer Docs — Set Pricing | [https://docs.livepeer.org/orchestrators/guides/set-pricing](https://docs.livepeer.org/orchestrators/guides/set-pricing) | Official guide explaining how orchestrators set transcoding prices per pixel (Wei), including automatic price adjustment behavior. |
+| Livepeer Docs — Gateway Overview | [https://docs.livepeer.org/gateways/guides/gateway-overview](https://docs.livepeer.org/gateways/guides/gateway-overview) | Describes the Gateway role, deployment, and responsibilities (no direct pricing guidance). |
+| Livepeer Studio Pricing | [https://livepeer.studio/pricing](https://livepeer.studio/pricing) | Example of a commercial, hosted gateway-style offering with explicit pricing tiers. |
+| Livepeer Forum — Inference Credits Pre‑Proposal | [https://forum.livepeer.org/t/agent-spe-inference-credits-pre-proposal/2747](https://forum.livepeer.org/t/agent-spe-inference-credits-pre-proposal/2747) | Community discussion touching on gateway pricing transparency and inference credits. |
+| GitHub — livepeer-broadcaster | [https://github.com/videodac/livepeer-broadcaster](https://github.com/videodac/livepeer-broadcaster) | Source code and configuration for gateway/broadcaster software; no canonical pricing config. |
+| Livepeer Docs — AI Gateways | [https://docs.livepeer.org/ai/builders/gateways](https://docs.livepeer.org/ai/builders/gateways) | Overview of AI gateways in the Livepeer ecosystem. |
+| Livepeer Cloud | [https://www.livepeer.cloud/](https://www.livepeer.cloud/) | Third‑party/hosted gateway portal showing how services may be packaged and offered. |
+| Livepeer Docs — AI Orchestrators On‑Chain | [https://na-36.mintlify.app/ai/orchestrators/onchain](https://na-36.mintlify.app/ai/orchestrators/onchain) | How AI orchestrators advertise service URIs on‑chain for gateway routing. |
+| Livepeer Pricing Tool (GitHub) | [https://github.com/buidl-labs/livepeer-pricing-tool](https://github.com/buidl-labs/livepeer-pricing-tool) | Community-built tool for observing network transcoding pricing. |
+| TokenTerminal — Livepeer Fees | [https://tokenterminal.com/explorer/projects/livepeer/metrics/fees](https://tokenterminal.com/explorer/projects/livepeer/metrics/fees) | Aggregated view of network fees driven by transcoding and AI inference. |
+| Messari — Livepeer Q3 2024 Brief | [https://messari.io/report/livepeer-q3-2024-brief](https://messari.io/report/livepeer-q3-2024-brief) | Mentions AI subnet fees and usage-based revenue growth. |
+| Livepeer Whitepaper | [https://github.com/livepeer/wiki/blob/master/WHITEPAPER.md](https://github.com/livepeer/wiki/blob/master/WHITEPAPER.md) | Protocol-level economic model and roles (historical but foundational). |
+| Gate.com — Livepeer AI Subnet | [https://www.gate.com/learn/articles/introducing-the-livepeer-ai-subnet/3044](https://www.gate.com/learn/articles/introducing-the-livepeer-ai-subnet/3044) | Third-party explanation of AI subnet economics and pricing concepts. |
+| Medium — Primer on Transcoding Fees | [https://medium.com/figment/primer-on-livepeer-transcoding-fees-3658057f98c2](https://medium.com/figment/primer-on-livepeer-transcoding-fees-3658057f98c2) | Clear explanation of per-pixel pricing between broadcasters and orchestrators. |
+| Livepeer Docs — What is Livepeer AI | [https://docs.livepeer.org/ai/introduction](https://docs.livepeer.org/ai/introduction) | Context on AI workflows and gateway/orchestrator interaction. |
+
+---
+
+## Key Findings for Docs
+
+### How pricing works (verified)
+
+* **Pricing is orchestrator-set**, not protocol-fixed.
+* Orchestrators advertise a **price per pixel (Wei)** to gateways.
+* Gateways route work based on availability and pricing.
+* **There is no official Livepeer Gateway pricing guide** defining what gateways should charge end users.
+
+### AI inference endpoints
+
+* Gateway operators can run AI gateways and expose inference APIs.
+* AI orchestrators must advertise their service URI on‑chain for routing.
+* There is **no documented BYOC-style pipeline registration flow** today (docs gap).
+
+### Marketplace visibility
+
+* There is **no canonical marketplace** listing all gateway offerings.
+* Visibility is fragmented across hosted providers, forums, and third‑party dashboards.
+
+> Docs gap identified: Gateway pricing strategy, discovery, and marketplace aggregation are currently undocumented at the protocol level.
+
+---
+
+## Answers to Your Specific Questions
+
+### 1) How is pricing done?
+
+**Verified from docs:**
+
+* Orchestrators set a **price per pixel in Wei**, which they advertise to gateways off-chain. This determines how much they charge for transcoding work. (Livepeer Docs)
+* There is a mechanism for **automatic price adjustment** based on ticket redemption overhead unless explicitly disabled. (Livepeer Docs)
+* There is **no official documented Livepeer Gateway pricing guide** for gateway operators setting marketplace pricing for hosting or AI services. Livepeer documentation focuses on orchestrator-level transcoding pricing only. The absence of direct gateway pricing guidance is a current, verified documentation gap.
+
+**Flat fee vs operator-set?**
+
+* Pricing is **operator-set (orchestrator-defined)** for transcoding.
+* Gateway usage pricing exposed by providers (e.g. Livepeer Cloud, Livepeer Studio) is **product or service specific**, not defined at the protocol level.
+* Livepeer docs do **not** define standard gateway pricing models; gateway operators and service providers set their own pricing. *(Verified absence)*
+
+---
+
+### 2) Can Gateway Operators add or contribute new AI inference endpoints if they run them?
+
+**Verified:**
+
+* For the Livepeer AI network, **AI orchestrators must advertise their AI service URI on-chain** so that AI gateways can discover and route i
diff --git a/v2/pages/04_gateways/guides-and-resources/page-2.mdx b/v2/pages/04_gateways/guides-and-resources/page-2.mdx
new file mode 100644
index 00000000..1dbccb19
--- /dev/null
+++ b/v2/pages/04_gateways/guides-and-resources/page-2.mdx
@@ -0,0 +1,2 @@
+# Page 2
+
diff --git a/v2/pages/04_gateways/guides-references/api-reference/ai-worker-api.mdx b/v2/pages/04_gateways/guides-references/api-reference/ai-worker-api.mdx
new file mode 100644
index 00000000..ab1ba459
--- /dev/null
+++ b/v2/pages/04_gateways/guides-references/api-reference/ai-worker-api.mdx
@@ -0,0 +1,97 @@
+---
+title: 'AI API'
+description: 'Complete API reference for Livepeer AI Worker endpoints'
+---
+
+# AI Worker API Reference
+
+Complete API reference for all Livepeer AI Worker endpoints.
+
+## Base URLs
+
+| Environment | URL |
+|-------------|-----|
+| Livepeer Cloud Gateway | `https://dream-gateway.livepeer.cloud` |
+| Livepeer Studio Gateway | `https://livepeer.studio/api/beta/generate` |
+
+---
+
+## Generate Endpoints
+
+### POST /text-to-image
+
+
+
+---
+
+### POST /image-to-image
+
+
+
+---
+
+### POST /image-to-video
+
+
+
+---
+
+### POST /upscale
+
+
+
+---
+
+### POST /audio-to-text
+
+
+
+---
+
+### POST /segment-anything-2
+
+
+
+---
+
+### POST /llm
+
+
+
+---
+
+### POST /image-to-text
+
+
+
+---
+
+### POST /live-video-to-video
+
+
+
+---
+
+### POST /text-to-speech
+
+
+
+---
+
+## System Endpoints
+
+### GET /health
+
+
+
+---
+
+### GET /hardware/info
+
+
+
+---
+
+### GET /hardware/stats
+
+
diff --git a/v2/pages/04_gateways/guides-references/configuration-flags.mdx b/v2/pages/04_gateways/guides-references/configuration-flags.mdx
new file mode 100644
index 00000000..0712a063
--- /dev/null
+++ b/v2/pages/04_gateways/guides-references/configuration-flags.mdx
@@ -0,0 +1,498 @@
+---
+title: 'Gateway Configuration Flags'
+description: 'Reference: full list of configuration flags for Livepeer Gateways'
+sidebarTitle: 'Configuration Flags'
+---
+ This should be dynamic and auto-generated from codebase to future proof it - It's currently static
+
+import { DoubleIconLink } from '/snippets/components/links.jsx'
+
+## Gateway Configuration Flags
+
+Related Wiki pages:
+-
+-
+
+
+
+ Table Legend:
+ ● Video
+ ● AI
+ ● Both
+
+
+
+
+
+
+
Flag
+
Type
+
Description
+
+
+
+
+
Network & Addresses
+
+
+
-network
+
Both
+
Network to connect to (offchain, arbitrum-one-mainnet, etc.)
+
+
+
-rtmpAddr
+
Video
+
Address to bind for RTMP commands (video ingest)
+
+
+
-cliAddr
+
Both
+
Address to bind for CLI commands
+
+
+
-httpAddr
+
Both
+
Address to bind for HTTP commands
+
+
+
-serviceAddr
+
Both
+
Orchestrator service URI for broadcasters to contact
+
+
+
-gatewayHost
+
Both
+
External hostname where Gateway node is running
+
+
+
+
Node Type
+
+
+
-gateway
+
Both
+
Set to true to be a gateway (handles both video and AI)
+
+
+
-orchestrator
+
Both
+
Set to true to be an orchestrator
+
+
+
-transcoder
+
Video
+
Set to true to be a transcoder
+
+
+
-aiWorker
+
AI
+
Set to true to run an AI worker
+
+
+
-broadcaster
+
Video
+
⚠️ Set to true to be a broadcaster (deprecated, use -gateway)
+
+
+
+
Video Transcoding
+
+
+
-transcodingOptions
+
Video
+
Transcoding profiles for broadcast job
+
+
+
-maxAttempts
+
Video
+
Maximum transcode attempts
+
+
+
-maxSessions
+
Both
+
Max concurrent sessions (transcoding for orchestrator, RTMP streams for gateway)
+
+
+
-nvidia
+
Video
+
Comma-separated list of Nvidia GPU device IDs
+
+
+
-netint
+
Video
+
Comma-separated list of NetInt device GUIDs
+
+
+
-hevcDecoding
+
Video
+
Enable or disable HEVC decoding
+
+
+
-testTranscoder
+
Video
+
Test Nvidia GPU transcoding at startup
+
+
+
-currentManifest
+
Video
+
Expose active ManifestID as "/stream/current.m3u8"
+
+
+
+
AI Processing
+
+
+
-aiServiceRegistry
+
AI
+
Use an AI ServiceRegistry contract address
+
+
+
-aiModels
+
AI
+
Models (pipeline:model_id) for AI worker to load
+
+
+
-aiModelsDir
+
AI
+
Directory where AI model weights are stored
+
+
+
-aiRunnerImage
+
AI
+
⚠️ Docker image for the AI runner (deprecated use -aiRunnerImageOverrides)
+
+
+
-aiRunnerImageOverrides
+
AI
+
Docker image overrides for different pipelines
+
+
+
-aiVerboseLogs
+
AI
+
Enable verbose logs for AI runner containers
+
+
+
-aiProcessingRetryTimeout
+
AI
+
Timeout for retrying AI processing requests
+
+
+
-aiRunnerContainersPerGPU
+
AI
+
Number of AI runner containers per GPU
+
+
+
+
Live AI Video
+
+
+
-mediaMTXApiPassword
+
AI
+
HTTP basic auth password for MediaMTX API
+
+
+
-liveAITrickleHostForRunner
+
AI
+
Trickle Host used by AI Runner
+
+
+
-liveAIAuthApiKey
+
AI
+
API key for Live AI authentication requests
+
+
+
-liveAIAuthWebhookUrl
+
AI
+
Live AI RTMP authentication webhook URL
+
+
+
-livePaymentInterval
+
AI
+
Interval for Gateway ↔ Orchestrator payments for Live AI
+
+
+
+
Orchestrator Selection
+
+
+
-orchAddr
+
Video
+
Comma-separated list of orchestrators to connect to
+
+
+
-orchWebhookUrl
+
Video
+
Orchestrator discovery callback URL
+
+
+
-orchBlocklist
+
Video
+
Comma-separated list of blocklisted orchestrators
+
+
+
-orchMinLivepeerVersion
+
Video
+
Minimal go-livepeer version for orchestrators
+
+
+
-selectRandFreq
+
Video
+
Weight of random factor in orchestrator selection
+
+
+
-selectStakeWeight
+
Video
+
Weight of stake factor in orchestrator selection
+
+
+
-selectPriceWeight
+
Video
+
Weight of price factor in orchestrator selection
+
+
+
-selectPriceExpFactor
+
Video
+
Significance of small price changes in selection
+
+
+
-orchPerfStatsUrl
+
Video
+
URL of Orchestrator Performance Stream Tester
+
+
+
-region
+
Video
+
Region where broadcaster is deployed
+
+
+
-minPerfScore
+
Video
+
Minimum orchestrator performance score to accept
+
+
+
-discoveryTimeout
+
Video
+
Time to wait for orchestrator info for manifest
+
+
+
+
Pricing & Payments
+
+
+
-maxPricePerUnit
+
Video
+
Maximum transcoding price per pixelsPerUnit
+
+
+
-maxPricePerCapability
+
AI
+
JSON list of prices per AI capability/model
+
+
+
-ignoreMaxPriceIfNeeded
+
Both
+
Allow exceeding max price if no orchestrator meets requirement
+
+
+
-pricePerUnit
+
Video
+
Price per pixelsPerUnit amount for transcoding
+
+
+
-pixelsPerUnit
+
Both
+
Amount of pixels per unit for pricing
+
+
+
-priceFeedAddr
+
Both
+
ETH address of Chainlink price feed contract
+
+
+
-autoAdjustPrice
+
Video
+
Enable automatic price adjustments
+
+
+
-pricePerGateway
+
Video
+
JSON list of price per gateway
+
+
+
-pricePerBroadcaster
+
Video
+
JSON list of price per broadcaster
+
+
+
+
Blockchain / Ethereum
+
+
+
-ethAcctAddr
+
Both
+
Existing ETH account address
+
+
+
-ethPassword
+
Both
+
Password for ETH account or path to file
+
+
+
-ethKeystorePath
+
Both
+
Path to ETH keystore directory or keyfile
+
+
+
-ethOrchAddr
+
Both
+
ETH address of on-chain registered orchestrator
+
+
+
-ethUrl
+
Both
+
Ethereum node JSON-RPC URL
+
+
+
-ethController
+
Both
+
Protocol smart contract address
+
+
+
-transactionTimeout
+
Both
+
Time to wait for ETH transaction confirmation
+
+
+
-maxTransactionReplacements
+
Both
+
Number of times to replace pending ETH transactions
+
+
+
-gasLimit
+
Both
+
Gas limit for ETH transactions
+
+
+
-minGasPrice
+
Both
+
Minimum gas price for ETH transactions in wei
+
+
+
-maxGasPrice
+
Both
+
Maximum gas price for ETH transactions in wei
+
+
+
+
Ticket System
+
+
+
-ticketEV
+
Both
+
Expected value for PM tickets
+
+
+
-maxFaceValue
+
Both
+
Max ticket face value in WEI
+
+
+
-maxTicketEV
+
Both
+
Maximum acceptable expected value for one PM ticket
+
+
+
-maxTotalEV
+
Both
+
Maximum acceptable expected value for one PM payment
+
+
+
-depositMultiplier
+
Both
+
Deposit multiplier for max acceptable ticket faceValue
+
+
+
+
Services
+
+
+
-redeemer
+
Both
+
Run a ticket redemption service
+
+
+
-redeemerAddr
+
Both
+
URL of ticket redemption service to use
+
+
+
-reward
+
Both
+
Run a reward service
+
+
+
-initializeRound
+
Both
+
Transcoder should automatically initialize new rounds
+
+
+
-initializeRoundMaxDelay
+
Both
+
Maximum delay before initializing a round
+
+
+
+
Monitoring & Metrics
+
+
+
-monitor
+
Both
+
Send performance metrics
+
+
+
-metricsPerStream
+
Both
+
Group performance metrics per stream
+
+
+
-metricsClientIP
+
Both
+
Expose client's IP in metrics
+
+
+
-metadataQueueUri
+
Both
+
URI for message broker to send operation metadata
+
+
+
-metadataAmqpExchange
+
Both
+
Name of AMQP exchange for operation metadata
+
+
+
-metadataPublishTimeout
+
Both
+
Max time to wait for publishing metadata events
+
+
+
+
Storage
+
+
+
-dataDir
+
Both
+
Directory that data is stored in
+
+
+
-objectStore
+
Both
+
URL of primary object store
+
+
+
-recordStore
+
Both
+
URL of object store for recordings
+
+
+
+
diff --git a/v2/pages/04_gateways/references/api-reference/AI-API/ai.mdx b/v2/pages/04_gateways/references/api-reference/AI-API/ai.mdx
new file mode 100644
index 00000000..3b336a45
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/AI-API/ai.mdx
@@ -0,0 +1,85 @@
+---
+title: 'AI API Portal'
+sidebarTitle: 'AI API Portal'
+description: 'AI API Reference Portal - find all API endpoints and try them out here'
+tag: 'API Index'
+---
+
+
+ Source code and OpenAPI specification
+
+
+## Base URLs
+
+
+
+
+
+
Environment
+
URL
+
+
+
+
+
Livepeer Cloud Community Gateway
+
https://dream-gateway.livepeer.cloud
+
+
+
Livepeer Studio Gateway
+
https://livepeer.studio/api/beta/generate
+
+
+
+
+
+---
+
+## Endpoints
+
+
+
+ Generate images from text prompts
+
+
+ Apply image transformations to a provided image
+
+
+ Generate a video from a provided image
+
+
+ Upscale an image by increasing its resolution
+
+
+ Transcribe audio files to text
+
+
+ Segment objects in an image
+
+
+ Generate text using a language model
+
+
+ Transform image files to text
+
+
+ Apply transformations to a live video streamed to the returned endpoints
+
+
+ Generate a text-to-speech audio file based on the provided text input and speaker description
+
+
+
+## Other Endpoints
+
+
+
+ Health
+
+
+ Hardware Info
+
+
+ Hardware Stats
+
+
+
diff --git a/v2/pages/04_gateways/references/api-reference/AI-API/audio-to-text.mdx b/v2/pages/04_gateways/references/api-reference/AI-API/audio-to-text.mdx
new file mode 100644
index 00000000..828fc7d0
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/AI-API/audio-to-text.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /audio-to-text
+---
diff --git a/v2/pages/04_gateways/references/api-reference/AI-API/hardware-info.mdx b/v2/pages/04_gateways/references/api-reference/AI-API/hardware-info.mdx
new file mode 100644
index 00000000..17b2129e
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/AI-API/hardware-info.mdx
@@ -0,0 +1,3 @@
+---
+openapi: get /hardware/info
+---
diff --git a/v2/pages/04_gateways/references/api-reference/AI-API/hardware-stats.mdx b/v2/pages/04_gateways/references/api-reference/AI-API/hardware-stats.mdx
new file mode 100644
index 00000000..ad3e9112
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/AI-API/hardware-stats.mdx
@@ -0,0 +1,3 @@
+---
+openapi: get /hardware/stats
+---
diff --git a/v2/pages/04_gateways/references/api-reference/AI-API/health.mdx b/v2/pages/04_gateways/references/api-reference/AI-API/health.mdx
new file mode 100644
index 00000000..35ceba0d
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/AI-API/health.mdx
@@ -0,0 +1,3 @@
+---
+openapi: get /health
+---
diff --git a/v2/pages/04_gateways/references/api-reference/AI-API/image-to-image.mdx b/v2/pages/04_gateways/references/api-reference/AI-API/image-to-image.mdx
new file mode 100644
index 00000000..11ab10b6
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/AI-API/image-to-image.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /image-to-image
+---
diff --git a/v2/pages/04_gateways/references/api-reference/AI-API/image-to-text.mdx b/v2/pages/04_gateways/references/api-reference/AI-API/image-to-text.mdx
new file mode 100644
index 00000000..6693d6a3
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/AI-API/image-to-text.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /image-to-text
+---
diff --git a/v2/pages/04_gateways/references/api-reference/AI-API/image-to-video.mdx b/v2/pages/04_gateways/references/api-reference/AI-API/image-to-video.mdx
new file mode 100644
index 00000000..607bf9ce
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/AI-API/image-to-video.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /image-to-video
+---
diff --git a/v2/pages/04_gateways/references/api-reference/AI-API/live-video-to-video.mdx b/v2/pages/04_gateways/references/api-reference/AI-API/live-video-to-video.mdx
new file mode 100644
index 00000000..65539ff0
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/AI-API/live-video-to-video.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /live-video-to-video
+---
diff --git a/v2/pages/04_gateways/references/api-reference/AI-API/llm.mdx b/v2/pages/04_gateways/references/api-reference/AI-API/llm.mdx
new file mode 100644
index 00000000..effd31b2
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/AI-API/llm.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /llm
+---
diff --git a/v2/pages/04_gateways/references/api-reference/AI-API/segment-anything-2.mdx b/v2/pages/04_gateways/references/api-reference/AI-API/segment-anything-2.mdx
new file mode 100644
index 00000000..abd07c44
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/AI-API/segment-anything-2.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /segment-anything-2
+---
diff --git a/v2/pages/04_gateways/references/api-reference/AI-API/text-to-image.mdx b/v2/pages/04_gateways/references/api-reference/AI-API/text-to-image.mdx
new file mode 100644
index 00000000..47eb264a
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/AI-API/text-to-image.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /text-to-image
+---
diff --git a/v2/pages/04_gateways/references/api-reference/AI-API/text-to-speech.mdx b/v2/pages/04_gateways/references/api-reference/AI-API/text-to-speech.mdx
new file mode 100644
index 00000000..6f9ee77f
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/AI-API/text-to-speech.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /text-to-speech
+---
diff --git a/v2/pages/04_gateways/references/api-reference/AI-API/upscale.mdx b/v2/pages/04_gateways/references/api-reference/AI-API/upscale.mdx
new file mode 100644
index 00000000..9d520b08
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/AI-API/upscale.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /upscale
+---
diff --git a/v2/pages/04_gateways/references/api-reference/_delete-all-api.mdx b/v2/pages/04_gateways/references/api-reference/_delete-all-api.mdx
new file mode 100644
index 00000000..dd99a4b7
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/_delete-all-api.mdx
@@ -0,0 +1,82 @@
+---
+title: 'AI Worker API'
+description: 'API reference for Livepeer AI Worker endpoints'
+openapi: ai/worker/api/openapi.yaml
+---
+
+# AI Worker API Reference
+
+This page provides the complete API reference for the Livepeer AI Worker. The AI Worker exposes endpoints for various AI pipelines including image generation, video generation, transcription, and more.
+
+
+These endpoints are available on AI Workers and Gateways running the Livepeer AI Runner.
+
+
+## Base URLs
+
+| Environment | URL |
+|-------------|-----|
+| Livepeer Cloud Gateway | `https://dream-gateway.livepeer.cloud` |
+| Livepeer Studio Gateway | `https://livepeer.studio/api/beta/generate` |
+
+## Authentication
+
+All generate endpoints require authentication via Bearer token in the `Authorization` header.
+
+```bash
+curl -X POST "https://dream-gateway.livepeer.cloud/text-to-image" \
+ -H "Authorization: Bearer YOUR_API_KEY" \
+ -H "Content-Type: application/json" \
+ -d '{"prompt": "a beautiful sunset"}'
+```
+
+## Endpoints
+
+### Generate Endpoints
+
+
+
+ Generate images from text prompts
+
+
+ Apply transformations to images
+
+
+ Generate video from an image
+
+
+ Upscale images to higher resolution
+
+
+ Transcribe audio to text
+
+
+ Segment objects in images
+
+
+ Large Language Model inference
+
+
+ Generate text descriptions from images
+
+
+ Real-time video transformations
+
+
+ Generate speech from text
+
+
+
+### System Endpoints
+
+
+
+ Check worker health status
+
+
+ Get hardware information
+
+
+ Get hardware statistics
+
+
diff --git a/v2/pages/04_gateways/references/api-reference/ai-worker-api.mdx b/v2/pages/04_gateways/references/api-reference/ai-worker-api.mdx
new file mode 100644
index 00000000..ab1ba459
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/ai-worker-api.mdx
@@ -0,0 +1,97 @@
+---
+title: 'AI API'
+description: 'Complete API reference for Livepeer AI Worker endpoints'
+---
+
+# AI Worker API Reference
+
+Complete API reference for all Livepeer AI Worker endpoints.
+
+## Base URLs
+
+| Environment | URL |
+|-------------|-----|
+| Livepeer Cloud Gateway | `https://dream-gateway.livepeer.cloud` |
+| Livepeer Studio Gateway | `https://livepeer.studio/api/beta/generate` |
+
+---
+
+## Generate Endpoints
+
+### POST /text-to-image
+
+
+
+---
+
+### POST /image-to-image
+
+
+
+---
+
+### POST /image-to-video
+
+
+
+---
+
+### POST /upscale
+
+
+
+---
+
+### POST /audio-to-text
+
+
+
+---
+
+### POST /segment-anything-2
+
+
+
+---
+
+### POST /llm
+
+
+
+---
+
+### POST /image-to-text
+
+
+
+---
+
+### POST /live-video-to-video
+
+
+
+---
+
+### POST /text-to-speech
+
+
+
+---
+
+## System Endpoints
+
+### GET /health
+
+
+
+---
+
+### GET /hardware/info
+
+
+
+---
+
+### GET /hardware/stats
+
+
diff --git a/v2/pages/04_gateways/references/api-reference/hardware-info.mdx b/v2/pages/04_gateways/references/api-reference/hardware-info.mdx
new file mode 100644
index 00000000..000e755b
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/hardware-info.mdx
@@ -0,0 +1,3 @@
+---
+openapi: get /hardware/info
+---
\ No newline at end of file
diff --git a/v2/pages/04_gateways/references/api-reference/hardware-stats.mdx b/v2/pages/04_gateways/references/api-reference/hardware-stats.mdx
new file mode 100644
index 00000000..8217ff88
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/hardware-stats.mdx
@@ -0,0 +1,3 @@
+---
+openapi: get /hardware/stats
+---
\ No newline at end of file
diff --git a/v2/pages/04_gateways/references/api-reference/health.mdx b/v2/pages/04_gateways/references/api-reference/health.mdx
new file mode 100644
index 00000000..f27caa88
--- /dev/null
+++ b/v2/pages/04_gateways/references/api-reference/health.mdx
@@ -0,0 +1,3 @@
+---
+openapi: get /health
+---
\ No newline at end of file
diff --git a/v2/pages/04_gateways/references/arbitrum-rpc.mdx b/v2/pages/04_gateways/references/arbitrum-rpc.mdx
new file mode 100644
index 00000000..81daf1ae
--- /dev/null
+++ b/v2/pages/04_gateways/references/arbitrum-rpc.mdx
@@ -0,0 +1,11 @@
+---
+title: 'Arbitrum RPCs'
+description: 'List of Public Arbitrum RPCs'
+sidebarTitle: 'Arbitrum RPC Reference'
+---
+
+import { ChainlistRPCs } from '/snippets/components/chainlist.jsx';
+
+Public RPC endpoints from [Chainlist](https://chainlist.org/chain/42161) (dynamically updated):
+
+
\ No newline at end of file
diff --git a/v2/pages/04_gateways/references/configuration-flags.mdx b/v2/pages/04_gateways/references/configuration-flags.mdx
new file mode 100644
index 00000000..41e81100
--- /dev/null
+++ b/v2/pages/04_gateways/references/configuration-flags.mdx
@@ -0,0 +1,497 @@
+---
+title: 'Gateway Configuration Flags'
+description: 'Reference: full list of configuration flags for Livepeer Gateways'
+sidebarTitle: 'Configuration Flags'
+---
+ This should be dynamic and auto-generated from codebase to future proof it - It's currently static
+
+import { DoubleIconLink } from '/snippets/components/links.jsx'
+
+## Gateway Configuration Flags
+
+{/* Related Code Sections:
+-
+- */}
+
+
+
+ ● Video
+ ● AI
+ ● Both
+
+
+
+
+
+
+
Flag
+
Type
+
Description
+
+
+
+
+
Network & Addresses
+
+
+
-network
+
Both
+
Network to connect to (offchain, arbitrum-one-mainnet, etc.)
+
+
+
-rtmpAddr
+
Video
+
Address to bind for RTMP commands (video ingest)
+
+
+
-cliAddr
+
Both
+
Address to bind for CLI commands
+
+
+
-httpAddr
+
Both
+
Address to bind for HTTP commands
+
+
+
-serviceAddr
+
Both
+
Orchestrator service URI for broadcasters to contact
+
+
+
-gatewayHost
+
Both
+
External hostname where Gateway node is running
+
+
+
+
Node Type
+
+
+
-gateway
+
Both
+
Set to true to be a gateway (handles both video and AI)
+
+
+
-orchestrator
+
Both
+
Set to true to be an orchestrator
+
+
+
-transcoder
+
Video
+
Set to true to be a transcoder
+
+
+
-aiWorker
+
AI
+
Set to true to run an AI worker
+
+
+
-broadcaster
+
Video
+
⚠️ Set to true to be a broadcaster (deprecated, use -gateway)
+
+
+
+
Video Transcoding
+
+
+
-transcodingOptions
+
Video
+
Transcoding profiles for broadcast job
+
+
+
-maxAttempts
+
Video
+
Maximum transcode attempts
+
+
+
-maxSessions
+
Both
+
Max concurrent sessions (transcoding for orchestrator, RTMP streams for gateway)
+
+
+
-nvidia
+
Video
+
Comma-separated list of Nvidia GPU device IDs
+
+
+
-netint
+
Video
+
Comma-separated list of NetInt device GUIDs
+
+
+
-hevcDecoding
+
Video
+
Enable or disable HEVC decoding
+
+
+
-testTranscoder
+
Video
+
Test Nvidia GPU transcoding at startup
+
+
+
-currentManifest
+
Video
+
Expose active ManifestID as "/stream/current.m3u8"
+
+
+
+
AI Processing
+
+
+
-aiServiceRegistry
+
AI
+
Use an AI ServiceRegistry contract address
+
+
+
-aiModels
+
AI
+
Models (pipeline:model_id) for AI worker to load
+
+
+
-aiModelsDir
+
AI
+
Directory where AI model weights are stored
+
+
+
-aiRunnerImage
+
AI
+
⚠️ Docker image for the AI runner (deprecated use -aiRunnerImageOverrides)
+
+
+
-aiRunnerImageOverrides
+
AI
+
Docker image overrides for different pipelines
+
+
+
-aiVerboseLogs
+
AI
+
Enable verbose logs for AI runner containers
+
+
+
-aiProcessingRetryTimeout
+
AI
+
Timeout for retrying AI processing requests
+
+
+
-aiRunnerContainersPerGPU
+
AI
+
Number of AI runner containers per GPU
+
+
+
+
Live AI Video
+
+
+
-mediaMTXApiPassword
+
AI
+
HTTP basic auth password for MediaMTX API
+
+
+
-liveAITrickleHostForRunner
+
AI
+
Trickle Host used by AI Runner
+
+
+
-liveAIAuthApiKey
+
AI
+
API key for Live AI authentication requests
+
+
+
-liveAIAuthWebhookUrl
+
AI
+
Live AI RTMP authentication webhook URL
+
+
+
-livePaymentInterval
+
AI
+
Interval for Gateway ↔ Orchestrator payments for Live AI
+
+
+
+
Orchestrator Selection
+
+
+
-orchAddr
+
Video
+
Comma-separated list of orchestrators to connect to
+
+
+
-orchWebhookUrl
+
Video
+
Orchestrator discovery callback URL
+
+
+
-orchBlocklist
+
Video
+
Comma-separated list of blocklisted orchestrators
+
+
+
-orchMinLivepeerVersion
+
Video
+
Minimal go-livepeer version for orchestrators
+
+
+
-selectRandFreq
+
Video
+
Weight of random factor in orchestrator selection
+
+
+
-selectStakeWeight
+
Video
+
Weight of stake factor in orchestrator selection
+
+
+
-selectPriceWeight
+
Video
+
Weight of price factor in orchestrator selection
+
+
+
-selectPriceExpFactor
+
Video
+
Significance of small price changes in selection
+
+
+
-orchPerfStatsUrl
+
Video
+
URL of Orchestrator Performance Stream Tester
+
+
+
-region
+
Video
+
Region where broadcaster is deployed
+
+
+
-minPerfScore
+
Video
+
Minimum orchestrator performance score to accept
+
+
+
-discoveryTimeout
+
Video
+
Time to wait for orchestrator info for manifest
+
+
+
+
Pricing & Payments
+
+
+
-maxPricePerUnit
+
Video
+
Maximum transcoding price per pixelsPerUnit
+
+
+
-maxPricePerCapability
+
AI
+
JSON list of prices per AI capability/model
+
+
+
-ignoreMaxPriceIfNeeded
+
Both
+
Allow exceeding max price if no orchestrator meets requirement
+
+
+
-pricePerUnit
+
Video
+
Price per pixelsPerUnit amount for transcoding
+
+
+
-pixelsPerUnit
+
Both
+
Amount of pixels per unit for pricing
+
+
+
-priceFeedAddr
+
Both
+
ETH address of Chainlink price feed contract
+
+
+
-autoAdjustPrice
+
Video
+
Enable automatic price adjustments
+
+
+
-pricePerGateway
+
Video
+
JSON list of price per gateway
+
+
+
-pricePerBroadcaster
+
Video
+
JSON list of price per broadcaster
+
+
+
+
Blockchain / Ethereum
+
+
+
-ethAcctAddr
+
Both
+
Existing ETH account address
+
+
+
-ethPassword
+
Both
+
Password for ETH account or path to file
+
+
+
-ethKeystorePath
+
Both
+
Path to ETH keystore directory or keyfile
+
+
+
-ethOrchAddr
+
Both
+
ETH address of on-chain registered orchestrator
+
+
+
-ethUrl
+
Both
+
Ethereum node JSON-RPC URL
+
+
+
-ethController
+
Both
+
Protocol smart contract address
+
+
+
-transactionTimeout
+
Both
+
Time to wait for ETH transaction confirmation
+
+
+
-maxTransactionReplacements
+
Both
+
Number of times to replace pending ETH transactions
+
+
+
-gasLimit
+
Both
+
Gas limit for ETH transactions
+
+
+
-minGasPrice
+
Both
+
Minimum gas price for ETH transactions in wei
+
+
+
-maxGasPrice
+
Both
+
Maximum gas price for ETH transactions in wei
+
+
+
+
Ticket System
+
+
+
-ticketEV
+
Both
+
Expected value for PM tickets
+
+
+
-maxFaceValue
+
Both
+
Max ticket face value in WEI
+
+
+
-maxTicketEV
+
Both
+
Maximum acceptable expected value for one PM ticket
+
+
+
-maxTotalEV
+
Both
+
Maximum acceptable expected value for one PM payment
+
+
+
-depositMultiplier
+
Both
+
Deposit multiplier for max acceptable ticket faceValue
+
+
+
+
Services
+
+
+
-redeemer
+
Both
+
Run a ticket redemption service
+
+
+
-redeemerAddr
+
Both
+
URL of ticket redemption service to use
+
+
+
-reward
+
Both
+
Run a reward service
+
+
+
-initializeRound
+
Both
+
Transcoder should automatically initialize new rounds
+
+
+
-initializeRoundMaxDelay
+
Both
+
Maximum delay before initializing a round
+
+
+
+
Monitoring & Metrics
+
+
+
-monitor
+
Both
+
Send performance metrics
+
+
+
-metricsPerStream
+
Both
+
Group performance metrics per stream
+
+
+
-metricsClientIP
+
Both
+
Expose client's IP in metrics
+
+
+
-metadataQueueUri
+
Both
+
URI for message broker to send operation metadata
+
+
+
-metadataAmqpExchange
+
Both
+
Name of AMQP exchange for operation metadata
+
+
+
-metadataPublishTimeout
+
Both
+
Max time to wait for publishing metadata events
+
+
+
+
Storage
+
+
+
-dataDir
+
Both
+
Directory that data is stored in
+
+
+
-objectStore
+
Both
+
URL of primary object store
+
+
+
-recordStore
+
Both
+
URL of object store for recordings
+
+
+
+
diff --git a/v2/pages/04_gateways/references/orchestrator-offerings.mdx b/v2/pages/04_gateways/references/orchestrator-offerings.mdx
new file mode 100644
index 00000000..c8f50645
--- /dev/null
+++ b/v2/pages/04_gateways/references/orchestrator-offerings.mdx
@@ -0,0 +1,154 @@
+---
+title: Orchestrator Offerings Reference
+description: "Reference: Orchestrator Offerings & Discovery"
+sidebarTitle: Orchestrator Offerings
+---
+
+Orchestrators publish their offerings through the `OrchestratorInfo` data structure
+
+```protobuf
+message OrchestratorInfo {
+ string transcoder = 1; // Service URI
+ TicketParams ticket_params = 2; // Payment parameters
+ PriceInfo price_info = 3; // Pricing information
+ bytes address = 4; // ETH address
+ Capabilities capabilities = 5; // Supported features
+ AuthToken auth_token = 6; // Authentication
+ repeated HardwareInformation hardware = 7; // Hardware specs
+ repeated OSInfo storage = 32; // Storage options
+ repeated PriceInfo capabilities_prices = 33; // AI model pricing
+}
+```
+
+### Registration Process
+
+Orchestrators register on-chain via the `activateOrchestrator` endpoint
+
+```bash
+# Required parameters for registration
+-blockRewardCut=5.0
+-feeShare=10.0
+-pricePerUnit=1000
+-pixelsPerUnit=1000000000000
+-serviceURI=https://orchestrator.example.com:8935
+```
+
+## What is Published
+
+### 1. Service Capabilities
+
+Orchestrators declare their processing capabilities through the `Capabilities` system
+
+- **Video Transcoding**: Format conversion, bitrate adaptation
+- **AI Processing**: Text-to-image, image-to-video, upscaling, etc.
+- **Live AI**: Real-time video-to-video processing
+
+### 2. Pricing Information
+
+Two-tier pricing structure
+
+- **Base Pricing**: Per-pixel rates for transcoding (`-pricePerUnit`)
+- **Capability Pricing**: Per-model AI pricing (`-maxPricePerCapability`)
+
+### 3. Hardware Specifications
+
+Detailed hardware info for performance matching
+
+```go
+type HardwareInformation struct {
+ Pipeline string // GPU pipeline info
+ ModelId string // AI model identifier
+ GpuInfo map[string]*GPUComputeInfo // GPU specifications
+}
+```
+
+## Discovery Mechanisms
+
+### 1. Direct Discovery
+
+Gateways specify orchestrators directly
+
+```bash
+-orchAddr=https://orch1.example.com:8935,https://orch2.example.com:8935
+```
+
+### 2. Webhook Discovery
+
+Dynamic discovery via external service
+
+```bash
+-orchWebhookUrl=https://discovery.example.com/orchestrators
+```
+
+### 3. On-Chain Discovery
+
+Automatic discovery of registered orchestrators
+
+- Queries blockchain for active orchestrators
+- Caches results in local database
+- Polls for updates periodically
+
+### 4. Network Capabilities API
+
+RESTful discovery endpoint
+
+```bash
+GET /getNetworkCapabilities
+```
+
+Returns:
+```json
+{
+ "capabilities_names": {...},
+ "orchestrators": [
+ {
+ "address": "0x...",
+ "localAddress": "0x...",
+ "orchURI": "https://...",
+ "capabilities": {...},
+ "capabilities_prices": [...],
+ "hardware": [...]
+ }
+ ]
+}
+```
+
+## Selection Process
+
+### Gateway Selection Logic
+
+Gateways select orchestrators based on a multi-factor scoring algorithm
+
+1. **Capability Matching**: Required features supported
+2. **Price Constraints**: Within maximum price limits
+3. **Performance Scores**: Historical performance metrics
+4. **Blacklist Filtering**: Exclude problematic orchestrators
+5. **Latency Considerations**: Network proximity
+
+### Selection Algorithm
+
+The discovery system uses a multi-factor scoring algorithm
+
+- **Random Factor** (`-selectRandFreq`): Prevents centralization
+- **Stake Weight** (`-selectStakeWeight`): Considers LPT stake
+- **Price Weight** (`-selectPriceWeight`): Favors competitive pricing
+
+## Marketplace Monitoring
+
+### CLI Tools
+
+Discovery and monitoring via `livepeer_cli`
+
+```bash
+livepeer_cli
+# Select "Set broadcast config" to see market rates
+# View available orchestrators and pricing
+```
+
+### HTTP Endpoints
+
+Real-time marketplace data
+
+- `/registeredOrchestrators` - All on-chain orchestrators
+- `/orchestratorInfo` - Specific orchestrator details
+- `/getNetworkCapabilities` - Available services and pricing
diff --git a/v2/pages/04_gateways/references/technical-architecture.mdx b/v2/pages/04_gateways/references/technical-architecture.mdx
new file mode 100644
index 00000000..ad973edb
--- /dev/null
+++ b/v2/pages/04_gateways/references/technical-architecture.mdx
@@ -0,0 +1,150 @@
+---
+title: Technical Architecture
+description: Technical Architecture Diagrams and References
+sidebarTitle: Technical Architecture
+---
+import { ScrollableDiagram } from '/snippets/components/zoomable-diagram.jsx'
+
+
+
+
+ Inference, Transcoding, BYOC]
+ end
+ U --> GI --> GM --> GR --> OC --> OG --> OC --> GI --> U`}
+ />
+
+
+
+
+ >Gateway: Submit job
+ Gateway->>Marketplace: Query orchestrator capabilities
+ Marketplace-->>Gateway: Matching candidates
+ Gateway->>Orchestrator: Dispatch workload
+ Orchestrator->>Gateway: Return results
+ Gateway->>App: Deliver output`}
+ />
+
+
+
+
+ • Ingest (RTMP/HTTP/WebRTC) • Segment video • Queue + order jobs • AI pipeline routing • Orchestrator selection • Verification & receipts"]
+
+ CAM -->|"Live stream"| GATEWAY
+ VID -->|"VOD upload"| GATEWAY
+ AIIN -->|"AI job request"| GATEWAY
+
+ subgraph JOBS["Workflows"]
+ VJ["Video Transcoding Job"]
+ AIJ["AI Inference Job (Daydream / ComfyStream / BYOC)"]
+ end
+
+ GATEWAY --> VJ
+ GATEWAY --> AIJ
+
+ subgraph ORCH["Orchestrator Network (GPU Operators)"]
+ O1["Orchestrator A GPU Pool"]
+ O2["Orchestrator B GPU Pool"]
+ O3["Orchestrator C GPU Pool"]
+ end
+
+ VJ -->|"Transcode segments"| O1
+ VJ --> O2
+ AIJ -->|"Run model / inference"| O1
+ AIJ --> O3
+
+ subgraph OUTPUTS["Outputs"]
+ HLS["Adaptive Bitrate Video (HLS/LL-HLS)"]
+ AIOUT["AI Frames / Stylized Video"]
+ end
+
+ O1 --> GATEWAY
+ O2 --> GATEWAY
+ O3 --> GATEWAY
+
+ GATEWAY --> HLS
+ GATEWAY --> AIOUT
+
+ ETH[("Arbitrum Blockchain Payments • Tickets • Rewards")]
+ GATEWAY --> ETH
+ O1 --> ETH
+ O2 --> ETH
+ O3 --> ETH
+
+ classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px
+ style INPUT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style JOBS fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style ORCH fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style OUTPUTS fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px`}
+ />
+
+
+
+
+
+{/* ### Marketplace Interaction Model
+
+ P
+ O --> P
+ A --> D
+ P --> R
+ R --> A`}
+/>
+
+### BYOC (Bring Your Own Container) Architecture
+
+ B[Compliant Runtime Spec]
+ B --> C[Gateway Intake]
+ C --> D[Capability Validation]
+ D --> E[Orchestrator Container Runner]
+ E --> F[GPU Execution]
+ F --> C --> A`}
+/> */}
diff --git a/v2/pages/04_gateways/run-a-gateway/configure/ai-configuration.mdx b/v2/pages/04_gateways/run-a-gateway/configure/ai-configuration.mdx
new file mode 100644
index 00000000..5c701d3f
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/configure/ai-configuration.mdx
@@ -0,0 +1,170 @@
+---
+title: 'AI Configuration'
+description: 'Configure AI Inference Services on a Livepeer Gateway'
+sidebarTitle: 'AI Configuration'
+icon: "user-robot"
+---
+
+import { DoubleIconLink, BlinkingIcon } from '/snippets/components/links.jsx'
+import { StyledSteps, StyledStep } from '/snippets/components/steps.jsx';
+
+This page will walk you through the process of deploying and configuring a Livepeer Gateway for AI inference services.
+
+## Gateway Modes
+You can run a gateway
+- **"Off-chain"** -> dev or local mode
+- **"On-chain"** -> production mode connected to the blockchain-based Livepeer network.
+
+
+ If you run your gateway **off-chain** - **you will need to run your own Orchestrator node** ie. have access to a GPU and set it up as an Orchestrator, in order to test Gateway functionality.
+
+
+ There is currently no Livepeer "Testnet" available which has Orchestrator offerings, though there are conversations underway to enable this in the future.
+
+ **Do you think Livepeer should have a "testnet" available for Gateways to connect to?**
+
+ Follow & contribute to the discussion in the [Discord]('https://discord.gg/livepeer') and on the [Forum]('https://forum.livepeer.org'))
+
+
+
+## Deploy a Gateway for AI Inference Services
+
+You can run the Livepeer AI software using one of the following methods:
+
+- **Docker** (Recommended): The simplest and preferred method.
+- **Pre-built Binaries**: An alternative if you prefer not to use Docker.
+
+
+## Deploy an AI Gateway
+
+Follow the steps below to start your Livepeer AI Gateway node.
+
+ These instructions apply to both on-chain & off-chain Gateway deployments.
+
+
+
+
+
+ Fetch the latest with the following command:
+
+ ```bash icon="terminal" Pull Docker Image
+ docker pull livepeer/go-livepeer:master
+ ```
+
+
+ Run the Docker container for your AI Gateway node:
+
+ ```bash icon="terminal"
+ docker run \
+ --name livepeer_ai_gateway \
+ -v ~/.lpData2/:/root/.lpData2 \
+ -p 8937:8937 \
+ --network host \
+ livepeer/go-livepeer:master \
+ -datadir ~/.lpData2 \
+ -gateway \
+ -orchAddr \
+ -httpAddr 0.0.0.0:8937 \
+ -v 6 \
+ -httpIngest
+ ```
+
+ This command launches a local (**off-chain**) AI Gateway node. The flags are similar to those used for a Mainnet Transcoding Network Gateway. (fixme) See the [go-livepeer CLI reference](/references/go-livepeer/cli-reference) for details.
+
+
+ Upon successful startup, you should see output similar to:
+
+ ```bash icon="terminal"
+ I0501 11:07:47.609839 1 mediaserver.go:201] Transcode Job Type: [{P240p30fps16x9 600k 30 0 426x240 16:9 0 0 0s 0 0 0 0} {P360p30fps16x9 1200k 30 0 640x360 16:9 0 0 0s 0 0 0 0}]
+ I0501 11:07:47.609917 1 mediaserver.go:226] HTTP Server listening on http://0.0.0.0:8937
+ I0501 11:07:47.609963 1 lpms.go:92] LPMS Server listening on rtmp://127.0.0.1:1935
+ ```
+
+
+ Ensure that port `8937` is open and accessible, and configure your router for port forwarding if necessary to make the Gateway accessible from the internet.
+ Add Howto
+
+
+ Follow the instructions in the to verify that the AI Gateway is operational.
+
+
+
+
+
+
+
+ Download the latest Livepeer AI binary for your system:
+
+ ```bash icon="terminal"
+ wget https://build.livepeer.live/go-livepeer/livepeer--.tar.gz
+ ```
+
+ Replace `` and `` with your operating system and architecture (e.g., `linux-amd64` for Linux AMD64). For more details, see the [go-livepeer installation guide](/orchestrators/guides/install-go-livepeer#install-using-a-binary-release).
+
+ The Windows and MacOS (amd64) binaries of Livepeer AI are **not** available yet.
+
+
+ Once downloaded, extract the binary to a directory of your choice.
+
+
+ Start the AI Gateway node with the following command:
+
+ ```bash icon="terminal"
+ ./livepeer \
+ -datadir ~/.lpData2 \
+ -gateway \
+ -orchAddr \
+ -httpAddr 0.0.0.0:8937 \
+ -v 6 \
+ -httpIngest
+ ```
+
+ This command launches an **off-chain** AI Gateway node. Refer to the [go-livepeer CLI reference](/references/go-livepeer/cli-reference) for more details on the flags.
+
+
+ Check the terminal for the following output to confirm successful startup:
+
+ ```bash icon="terminal"
+ I0501 11:07:47.609839 1 mediaserver.go:201] Transcode Job Type: [{P240p30fps16x9 600k 30 0 426x240 16:9 0 0 0s 0 0 0 0} {P360p30fps16x9 1200k 30 0 640x360 16:9 0 0 0s 0 0 0 0}]
+ I0501 11:07:47.609917 1 mediaserver.go:226] HTTP Server listening on http://0.0.0.0:8937
+ I0501 11:07:47.609963 1 lpms.go:92] LPMS Server listening on rtmp://127.0.0.1:1935
+ ```
+
+
+ Ensure that port `8937` is open and accessible, and configure port forwarding if needed.
+
+
+ Follow the instructions in the to verify that the AI Gateway is operational.
+
+
+
+
+ If binaries are unavailable for your system, you can build the [master branch](https://github.com/livepeer/go-livepeer/tree/master) of [go-livepeer](https://github.com/livepeer/go-livepeer) from source. Refer to the [Livepeer installation guide](/orchestrators/guides/install-go-livepeer#install-using-a-binary-release) or reach out to the Livepeer community on [Discord](https://discord.gg/livepeer) for assistance.
+
+
+
+
+
+
+## Gateway Code Links
+For AI processing, the Gateway extends its functionality to handle AI-specific workflows.
+
+
+
+
+Key components include:
+
+- **AISessionManager**: Manages AI processing sessions and selects appropriate Orchestrators with AI capabilities
+- **MediaMTX Integration**: Handles media streaming for AI processing
+- **Trickle Protocol**: Enables efficient streaming for real-time AI video processing
+
+The AI workflow involves
+- authenticating AI streams,
+- selecting AI-capable Orchestrators,
+- processing payments **based on pixels**, and
+- managing live AI pipelines
\ No newline at end of file
diff --git a/v2/pages/04_gateways/run-a-gateway/configure/configuration-overview.mdx b/v2/pages/04_gateways/run-a-gateway/configure/configuration-overview.mdx
new file mode 100644
index 00000000..ffd9df7d
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/configure/configuration-overview.mdx
@@ -0,0 +1,45 @@
+---
+title: 'Configuration Overview'
+description: 'Overview of configuring a Livepeer Gateway including running & pricing AI & Video services'
+sidebarTitle: 'Configuration Overview'
+---
+
+
+This should be streamlined.
+
+Config options are:
+- off-chain vs on-chain (includes funding)
+- video vs ai only vs dual mode
+- Config reference for pricing, algorithms etc.
+
+
+
+## Introduction
+Gateways in Livepeer serve as the entry point for media streams, handling both traditional video transcoding and
+AI processing workflows. While the core function of ingesting and distributing media is similar, the processing pipelines and components differ.
+A single gateway can handle both types of workloads simultaneously.
+
+
+This section breaks down the Livepeer Gateway configuration space into the following options:
+- **Transcoding Options** - used by Transcoding Network Gateways
+- **AI Gateway Flags & Options** - used when running a Gateway in the Livepeer AI network context
+- **Dual Configuration** - used when running a Gateway that supports both video transcoding and AI inference services
+- **Pricing Configuration** - used to configure pricing for service offerings
+
+## Launch Pad
+
+
+
+ Configure video transcoding services
+
+
+ Configure AI inference services
+
+
+ Configure both video transcoding and AI inference services
+
+
+ Configure pricing for services
+
+
+
diff --git a/v2/pages/04_gateways/run-a-gateway/configure/configuration-reference.mdx b/v2/pages/04_gateways/run-a-gateway/configure/configuration-reference.mdx
new file mode 100644
index 00000000..7853d011
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/configure/configuration-reference.mdx
@@ -0,0 +1,5 @@
+---
+title: 'Configuration Reference'
+description: 'Reference for configuring a Livepeer Gateway'
+sidebarTitle: 'Configuration Reference'
+---
diff --git a/v2/pages/04_gateways/run-a-gateway/configure/dual-configuration.mdx b/v2/pages/04_gateways/run-a-gateway/configure/dual-configuration.mdx
new file mode 100644
index 00000000..756012f7
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/configure/dual-configuration.mdx
@@ -0,0 +1,331 @@
+---
+title: 'Configure AI & Video Dual Gateway Services'
+description: "Configure Dual AI & Video Services on a Livepeer Gateway"
+sidebarTitle: 'Dual Configuration'
+icon: "drone"
+tag: AI & Video
+---
+
+import { ScrollableDiagram } from '/snippets/components/zoomable-diagram.jsx'
+import { DoubleIconLink } from '/snippets/components/links.jsx'
+import { ExternalContent } from '/snippets/components/external-content.jsx'
+import BoxConfig from '/snippets/external/box-additional-config.mdx'
+
+
+ This is way too long
+
+ **TODO:**
+ - [ ] Verify flags and options are correct
+ - [ ] Decide on more streamlined layour or steps flow
+ - [ ] (fixme) #Configuration
+ - [ ] (fixme) ##Deployment
+ - [ ] Move Example to Guides & Resources
+
+
+
+The Livepeer Gateway supports a dual setup configuration that enables a single node to handle both
+traditional video transcoding and AI processing workloads simultaneously.
+
+This unified architecture reduces infrastructure complexity while providing
+comprehensive media processing capabilities.
+
+
+
+```mermaid
+%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui' }}}%%
+flowchart TB
+ subgraph INPUT["Input Sources"]
+ direction LR
+ RTMP["RTMP Stream"]
+ HTTP["HTTP Upload"]
+ AI_REQ["AI Request"]
+ end
+
+ GATEWAY["Gateway Node LivepeerNode"]
+
+ INPUT --> GATEWAY
+
+ subgraph MANAGERS["Session Managers"]
+ direction LR
+ BSM["BroadcastSessionsManager Video Transcoding"]
+ ASM["AISessionManager AI Processing"]
+ end
+
+ GATEWAY --> BSM
+ GATEWAY --> ASM
+
+ subgraph VIDEO["Video Pipeline"]
+ SEG["Segment Processing"]
+ ORCH_V["Orchestrators Transcoding"]
+ HLS["HLS/DASH Output"]
+ end
+
+ subgraph AI["AI Pipeline"]
+ PROC["AI Processing"]
+ ORCH_AI["Orchestrators AI Models"]
+ OUT_AI["AI Output Images/Video"]
+ end
+
+ BSM --> SEG --> ORCH_V --> HLS
+ ASM --> PROC --> ORCH_AI --> OUT_AI
+
+ subgraph PAYMENT["Payment"]
+ direction LR
+ PAY_SEG["Per Segment"]
+ PAY_PIX["Per Pixel"]
+ end
+
+ ORCH_V --> PAY_SEG
+ ORCH_AI --> PAY_PIX
+
+ classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px
+ classDef video fill:#1a1a1a,color:#fff,stroke:#3b82f6,stroke-width:2px
+ classDef ai fill:#1a1a1a,color:#fff,stroke:#a855f7,stroke-width:2px
+ class RTMP,HTTP,BSM,SEG,ORCH_V,HLS,PAY_SEG video
+ class AI_REQ,ASM,PROC,ORCH_AI,OUT_AI,PAY_PIX ai
+ style INPUT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style MANAGERS fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style VIDEO fill:#0d0d0d,stroke:#3b82f6,stroke-width:1px
+ style AI fill:#0d0d0d,stroke:#a855f7,stroke-width:1px
+ style PAYMENT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+```
+
+
+
+
+## Overview
+
+The Gateway's dual capability is enabled by its modular architecture, where different
+managers handle specific workflows while sharing common infrastructure for media ingestion,
+payment processing, and result delivery.
+
+The LivepeerNode struct contains fields for both traditional transcoding (Transcoder, TranscoderManager)
+and AI processing (AIWorker, AIWorkerManager)
+
+The gateway determines the processing type based on the request:
+- Standard transcoding requests go through the BroadcastSessionsManager
+- AI requests go through the AISessionManager with AI-specific authentication and pipeline selection
+
+The gateway initializes with two distinct session managers:
+
+```go
+// Traditional transcoding session manager
+sessManager = NewSessionManager(ctx, s.LivepeerNode, params)
+```
+
+```go
+// AI processing session manager
+AISessionManager: NewAISessionManager(lpNode, AISessionManagerTTL)
+```
+
+**Key Differences**
+
+
+
+
+
Aspect
+
Video Transcoding
+
AI Pipelines
+
+
+
+
+
Processing Type
+
Format/bitrate conversion
+
AI model inference
+
+
+
Session Manager
+
BroadcastSessionsManager
+
AISessionManager
+
+
+
Payment Model
+
Per segment
+
Per pixel processed
+
+
+
Protocol
+
Standard HLS/DASH
+
Trickle protocol for real-time AI
+
+
+
Components
+
RTMP Server, Playlist Manager
+
MediaMTX, Trickle Server
+
+
+
+
+## Configuration
+
+To configure a gateway to handle both video transcoding and AI processing, you need
+to set the appropriate flags and options when starting the livepeer binary.
+
+**Essential Flags**
+
+To enable dual setup, configure the gateway with the following flags:
+
+
+
+
+
Flag
+
Description
+
Required
+
+
+
+
+
-gateway
+
Run as a gateway node
+
✓
+
+
+
-httpIngest
+
Enable HTTP ingest for AI requests
+
✓
+
+
+
-transcodingOptions
+
Transcoding profiles for video
+
✓
+
+
+
-aiServiceRegistry
+
Enable AI service registry
+
✓
+
+
+
+See:
+
+ Verify all code below here
+
+### AI-Specific Configuration
+
+```bash AI flags icon="user-robot"
+-aiModels=${env:HOME}/.lpData/cfg/aiModels.json
+-aiModelsDir=${env:HOME}/.lpData/models
+-aiRunnerContainersPerGPU=1
+-livePaymentInterval=5s
+```
+
+### Transcoding Configuration
+Note, if the `transcodingOptions.json` file is not provided, the gateway will use the default transcoding profiles `-transcodingOptions=P240p30fps16x9,P360p30fps16x9`.
+
+```bash Transcoding flags icon="film-canister"
+# -transcodingOptions=P240p30fps16x9,P360p30fps16x9
+-transcodingOptions=${env:HOME}/.lpData/cfg/transcodingOptions.json
+-maxSessions=10
+-nvidia=all # or specific GPU IDs
+```
+
+## Deployment
+
+
+ For local development and testing purposes, there is no need to connect to the blockchain payments layer.
+
+ You will need to run your own orchestrator node for local development.
+
+ ```bash Off-Chain Gateway Deployment with dual capabilities icon="terminal"
+ livepeer -gateway \
+ -httpIngest \
+ -transcodingOptions=${env:HOME}/.lpData/offchain/transcodingOptions.json \
+ -orchAddr=0.0.0.0:8935 \
+ -httpAddr=0.0.0.0:9935 \
+ -httpIngest \
+ -v=6
+
+ # Verify these
+ -aiServiceRegistry \
+ -aiModels=${env:HOME}/.lpData/cfg/aiModels.json \
+ -aiModelsDir=${env:HOME}/.lpData/models \
+ -aiRunnerContainersPerGPU=1 \
+ ```
+
+
+
+ For production deployment with blockchain integration
+
+ You will need an ETH account with funds to pay for transcoding and AI processing and set the following environment variables:
+ `$ETH_SECRET`
+ `$ETH_ACCT_ADDR`
+
+ ```bash On-Chain Gateway Deployment with dual capabilities icon="terminal"
+ livepeer -gateway \
+ -transcodingOptions=${env:HOME}/.lpData/offchain/transcodingOptions.json \
+ -orchAddr=0.0.0.0:8935 \
+ -httpAddr=0.0.0.0:9935 \
+ -httpIngest \
+ -v=6 \
+ -network=arbitrum-one-mainnet \
+ -ethUrl=https://arb1.arbitrum.io/rpc \
+ -ethPassword= \
+ -ethAcctAddr= \
+ -v=6
+
+ # verfiy these
+ -aiServiceRegistry \
+ -aiModels=${env:HOME}/.lpData/cfg/aiModels.json \
+ -aiModelsDir=${env:HOME}/.lpData/models \
+ -aiRunnerContainersPerGPU=1 \
+ -livePaymentInterval=5s
+ ```
+
+
+
+## Combined Gateway/Orchestrator AI-Enabled Deployment
+
+For nodes that handle both orchestration and AI processing
+
+```bash Combined Gateway/OrchestratorOn-Chain Deployment icon="terminal"
+
+ livepeer -orchestrator -aiWorker -aiServiceRegistry \
+ -serviceAddr=0.0.0.0:8935 \
+ -nvidia=all \
+ -aiModels=${env:HOME}/.lpData/cfg/aiModels.json \
+ -aiModelsDir=${env:HOME}/.lpData/models \
+ -network=arbitrum-one-mainnet \
+ -ethUrl=https://arb1.arbitrum.io/rpc \
+ -ethPassword= \
+ -ethAcctAddr= \
+ -ethOrchAddr=
+```
+
+## Troubleshooting
+
+**Common Issues**
+
+- **AI models not loading:** Check `-aiModelsDir` and model file permissions
+- **Transcoding failures:** Verify GPU drivers and `-nvidia` configuration
+- **Port conflicts:** Ensure `-rtmpAddr`, `-httpAddr`, and `-cliAddr` are available
+- **Memory pressure:** Monitor AI model memory usage, adjust `-aiRunnerContainersPerGPU`
+
+**Debug Commands**
+```bash icon="terminal"
+ # Check transcoding capabilities
+ curl http://localhost:8935/getBroadcastConfig
+
+ # Test AI endpoint
+ curl -X POST http://localhost:8935/text-to-image \
+ -H "Content-Type: application/json" \
+ -d '{"prompt":"test image"}'
+
+ # Monitor logs
+ livepeer -gateway -v=6 2>&1 | grep -E "(transcode|AI|segment)"
+```
+
+
+
+
+## Example Setup
+
+The box setup for local development demonstrates running a gateway that handles both types of processing.
+
+
+
+
diff --git a/v2/pages/04_gateways/run-a-gateway/configure/pricing-configuration.mdx b/v2/pages/04_gateways/run-a-gateway/configure/pricing-configuration.mdx
new file mode 100644
index 00000000..1b28eeb0
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/configure/pricing-configuration.mdx
@@ -0,0 +1,121 @@
+---
+title: 'Pricing Configuration'
+description: 'Configure Pricing for Livepeer Gateway Services'
+sidebarTitle: 'Pricing Configuration'
+icon: "hand-holding-dollar"
+---
+
+ 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](https://github.com/livepeer/go-livepeer/blob/5691cb48/core/rpc.go).
+
+
+ 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 the `transcodingConfig.json` or directly in the CLI.
+
+
+ Maximum price per pixelsPerUnit (in wei `integer` or a custom currency format like 0.50USD or 0.02USD) for transcoding work [livepeer.go:137]("https://github.com/livepeer/go-livepeer/blob/5691cb48/cmd/livepeer/livepeer.go")
+
+
+ JSON list (or path to JSON congif file) of maximum prices per AI capability/model [livepeer.go:138]("https://github.com/livepeer/go-livepeer/blob/5691cb48/cmd/livepeer/livepeer.go")
+
+
+
+ Allows exceeding max price if no orchestrator meets requirements [livepeer.go:139]("https://github.com/livepeer/go-livepeer/blob/5691cb48/cmd/livepeer/livepeer.go")
+
+
+
+
+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](https://github.com/livepeer/go-livepeer/blob/5691cb48/cmd/livepeer/starter.go)
+
+```json
+{
+ "gateways": [
+ {
+ "ethaddress": "0x123...",
+ "priceperunit": 0.5,
+ "currency": "USD",
+ "pixelsperunit": 1000000000000
+ }
+ ]
+}
+```
+
+### Price Calculation
+
+The actual price calculation happens in the orchestrator's `priceInfo` function [orchestrator.go:357-431](https://github.com/livepeer/go-livepeer/blob/5691cb48/core/orchestrator.go)
+
+1. Checks for fixed prices per manifest ID
+2. Gets base price from orchestrator configuration
+3. For AI workloads, sums prices of individual capability/model pairs
+4. 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](https://github.com/livepeer/go-livepeer/blob/5691cb48/core/segment_rpc.go)
+- Fee calculation: Based on pixels processed × price per pixel [segment_rpc.go:645-653](https://github.com/livepeer/go-livepeer/blob/5691cb48/core/segment_rpc.go)
+
+_AI Processing_
+
+- Per-pixel payments: Calculated as width × height × outputs [live_payment.go:162-165](https://github.com/livepeer/go-livepeer/blob/5691cb48/core/live_payment.go)
+- Live video: Uses interval-based payments during streaming [ai_http.go:181-211](https://github.com/livepeer/go-livepeer/blob/5691cb48/server/ai_http.go)
+
+_Payment Processing Flow_
+
+1. Gateway sends payment with segment/request to orchestrator [live_payment.go:96-114](https://github.com/livepeer/go-livepeer/blob/5691cb48/core/live_payment.go)
+2. Orchestrator validates payment and updates balance [segment_rpc.go:257-261](https://github.com/livepeer/go-livepeer/blob/5691cb48/core/segment_rpc.go)
+3. Fees are debited from gateway's balance account [ai_http.go:568](https://github.com/livepeer/go-livepeer/blob/5691cb48/server/ai_http.go)
+
+
+### Dynamic Price Adjustment
+
+Orchestrators can enable automatic price adjustments based on transaction costs [orchestrator.go:408-431](https://github.com/livepeer/go-livepeer/blob/5691cb48/core/orchestrator.go)
+
+```go
+if !orch.node.AutoAdjustPrice {
+ return basePrice, nil
+}
+// Apply overhead multiplier based on tx costs
+overhead := big.NewRat(1, 1)
+if basePrice.Num().Cmp(big.NewInt(0)) > 0 {
+ txCostMultiplier, err := orch.node.Recipient.TxCostMultiplier(sender)
+ if txCostMultiplier.Cmp(big.NewRat(0, 1)) > 0 {
+ overhead = overhead.Add(overhead, new(big.Rat).Inv(txCostMultiplier))
+ }
+}
+```
\ No newline at end of file
diff --git a/v2/pages/04_gateways/run-a-gateway/configure/video-configuration.mdx b/v2/pages/04_gateways/run-a-gateway/configure/video-configuration.mdx
new file mode 100644
index 00000000..be29b142
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/configure/video-configuration.mdx
@@ -0,0 +1,143 @@
+---
+title: 'Video Configuration'
+description: 'Configure Video Services on a Livepeer Gateway'
+sidebarTitle: 'Video & Transcoding Configuration'
+icon: "film-canister"
+---
+
+import { DoubleIconLink } from '/snippets/components/links.jsx'
+
+## Gateways for Video Transcoding
+In traditional video transcoding, the Gateway ingests video streams via RTMP or HTTP,
+segments them, and distributes transcoding work to Orchestrators
+
+
+
+Key components include:
+
+- **BroadcastSessionsManager**: Manages transcoding sessions and selects Orchestrators
+- **[RTMP](https://en.wikipedia.org/wiki/Real-Time_Messaging_Protocol) Server**: Handles RTMP (Real-Time Message Protocol) stream ingestion
+- **Payment Manager**: Generates and sends payment tickets for transcoding work
+
+The workflow involves segmenting video, sending segments with payments to Orchestrators,
+receiving transcoded results, and serving them via HLS .
+
+Gateways that receive a live or recorded RTMP stream need to
+transcode it into multiple renditions before sending it to Orchestrators for distribution.
+
+
+## Transcoding Configuration Options
+ Homogenise Layout with AI Layout
+
+ (fixme) (moved from v1 docs) This is confusing - I don't know what I am doing or why
+
+The transcodingOptions.json file lets you precisely control the encoding ladder.
+
+This file is a custom configuration file that defines which renditions (resolutions + bitrates)
+your Gateway will produce for each incoming stream.
+It overrides the default built-in ladder (e.g., P240p30fps16x9, etc.).
+
+It is passed to the livepeer binary with the CLI flag:
+
+```bash transcodingOptions.json icon="terminal"
+ -transcodingOptions=/path/to/transcodingOptions.json
+```
+
+
+(The default without this flag is a set of presets like P240p30fps16x9,P360p30fps16x9, etc.)
+docs.livepeer.org
+
+Use the following as a template for your json file
+
+``` json transcodingOptions.json example icon="brackets-curly"
+[
+{
+ "name": "480p0",
+ "fps": 0,
+ "bitrate": 1600000,
+ "width": 854,
+ "height": 480,
+ "profile": "h264constrainedhigh",
+ "gop": "1"
+},
+{
+ "name": "720p0",
+ "fps": 0,
+ "bitrate": 3000000,
+ "width": 1280,
+ "height": 720,
+ "profile": "h264constrainedhigh",
+ "gop": "1"
+},
+{
+ "name": "1080p0",
+ "fps": 0,
+ "bitrate": 6500000,
+ "width": 1920,
+ "height": 1080,
+ "profile": "h264constrainedhigh",
+ "gop": "1"
+}
+]
+```
+
+## Modify Config Files
+
+
+
+Create the transcodingOptions.json file using the above template.
+
+``` bash icon="docker"
+nano -p /var/lib/docker/volumes/gateway-lpData/_data/transcodingOptions.json
+```
+
+Modify the docker-compose.yml file from the root user's home directory _/root/_
+and add the following below `-pixelsPerUnit=1`
+
+``` bash icon="docker"
+-transcodingOptions=/root/.lpData/transcodingOptions.json
+```
+
+
+
+Create the transcodingOptions.json file using the above template.
+
+``` bash icon="linux"
+sudo nano /usr/local/bin/lptConfig/transcodingOptions.json
+```
+
+Modify the Linux Service file /etc/systemd/system/livepeer.service and add the
+following below `-pixelsPerUnit=1`
+
+``` bash icon="linux"
+-transcodingOptions=/usr/local/bin/lptConfig/transcodingOptions.json \
+```
+
+
+
+Create the transcodingOptions.json file using the above template.
+
+Open notepad (or your text editor of choice) paste the template above and save
+the transcodingOptions.json file in the following location.
+
+In Windows, %USERNAME% is already a built-in environment variable
+-> You can use it directly.
+
+``` bash icon="windows"
+C:\Users\%USERNAME%\.lpData\transcodingOptions.json
+```
+
+Modify Windows bat file to include the following command after
+`-pixelsPerUnit=1`
+
+``` bash icon="windows"
+-transcodingOptions=C:\Users\%USERNAME%\.lpData\transcodingOptions.json
+```
+
+
\ No newline at end of file
diff --git a/v2/pages/04_gateways/run-a-gateway/connect/connect-with-offerings.mdx b/v2/pages/04_gateways/run-a-gateway/connect/connect-with-offerings.mdx
new file mode 100644
index 00000000..f22dc174
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/connect/connect-with-offerings.mdx
@@ -0,0 +1,119 @@
+---
+title: 'Discover & Connect Marketplace Compute Services'
+description: 'This page explains how to find and broker Orchestrator AI & Video Offerings via your Gateway for Livepeer Application consumption.'
+sidebarTitle: 'Discover & Connect Services'
+---
+import { CustomCallout } from '/snippets/components/links.jsx';
+import { ScrollableDiagram } from '/snippets/components/zoomable-diagram.jsx';
+
+
+ This page should be streamlined.
+
+ Options are:
+ - on-chain vs off-chain
+ - ai vs video vs dual
+
+ What it explains:
+ - Discovery
+ - Filtering
+ - Routing
+
+ This page is a work in progress. Needs a lot of edits.
+
+ TODO:
+ - [ ] Overview,
+ - [ ] Edit (A LOT)
+ - [ ] Streamline,
+ - [ ] Format,
+ - [ ] Style,
+ - [ ] Link to github / otherresources
+
+
+
+# How to Discover & Connect Marketplace Offerings
+This page explains how Gateways can discover and offer Orchestrator Services,
+ available on the Marketplace, to Applications & Builders.
+
+## Discovery Process
+Gateways discover orchestrators through the orchestrator pool in `discovery/discovery.go` [discovery.go:64-111](https://github.com/livepeer/go-livepeer/blob/5691cb48/discovery/discovery.go#L64-L111)
+
+1. **Query orchestrators**: Get `OrchestratorInfo` from each orchestrator
+2. **Filter capabilities & price**: Match against required capabilities & pricing limits & optionally rank results
+3. **Expose results**: Make matching orchestrator services available through HTTP endpoints
+4. **Route requests**: Forward incoming requests to selected orchestrators
+
+## Find All Orchestrators & Offerings
+The `/getNetworkCapabilities` endpoint in [server/handlers.go](https://github.com/livepeer/go-livepeer/blob/5691cb48/server/handlers.go#L275-L295)
+exposes all available orchestrator offerings
+
+```go
+func (s *LivepeerServer) getNetworkCapabilitiesHandler() http.Handler {
+ return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
+ // Returns orchestrators with their capabilities, pricing, and hardware
+ })
+}
+```
+
+**Response Data Structure**
+
+The response uses NetworkCapabilities structure from `common/types.go` [types.go:166-176](https://github.com/livepeer/go-livepeer/blob/5691cb48/common/types.go#L166-L176)
+
+```go
+type NetworkCapabilities struct {
+ Orchestrators []*OrchNetworkCapabilities `json:"orchestrators"`
+}
+
+type OrchNetworkCapabilities struct {
+ Address string `json:"address"`
+ LocalAddress string `json:"local_address"`
+ OrchURI string `json:"orch_uri"`
+ Capabilities *net.Capabilities `json:"capabilities"`
+ CapabilitiesPrices []*net.PriceInfo `json:"capabilities_prices"`
+ Hardware []*net.HardwareInformation `json:"hardware"`
+}
+```
+
+## Gateway
+
+Gateways expose offerings describing:
+
+### **1. Supported Models**
+
+Example:
+
+- `stable-diffusion-v1.5`
+- `depth-anything`
+- `controlnet_lineart`
+- `ip_adapter`
+
+### **2. Supported Pipelines**
+
+- Daydream-style real-time style transfer
+- ComfyStream workflows
+- BYOC containers
+- Custom inference graphs
+
+### **3. Pricing**
+
+A Gateway may price:
+
+- `$0.004 / frame`
+- `$0.06 / second`
+- `$0.0005 / inference token`
+
+### **4. Regions**
+
+Example:
+
+- `us-east`
+- `eu-central`
+- `ap-southeast`
+
+### **5. Reliability Scores**
+
+Gateways may publish:
+
+- Availability %
+- Average inference latency
+- Failover configuration
+
diff --git a/v2/pages/04_gateways/run-a-gateway/connect/discover-offerings.mdx b/v2/pages/04_gateways/run-a-gateway/connect/discover-offerings.mdx
new file mode 100644
index 00000000..0a1aec08
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/connect/discover-offerings.mdx
@@ -0,0 +1,106 @@
+---
+title: 'Discover Marketplace Offerings'
+description: 'This page explains how to discover AI & Video compute services offered by Orchestrators via your Gateway. for Livepeer Application consumption.'
+sidebarTitle: 'Discover Compute Offerings'
+---
+
+import { StyledSteps, StyledStep } from '/snippets/components/steps.jsx'
+
+## Discovery Process
+Gateways discover orchestrators through the orchestrator pool in [discovery/discovery.go](https://github.com/livepeer/go-livepeer/blob/5691cb48/discovery/discovery.go)
+
+
+
+ Get `OrchestratorInfo` from each orchestrator
+
+
+ Match against required capabilities & pricing limits & optionally rank results
+
+
+ Make matching orchestrator services available through HTTP endpoints
+
+
+ Forward incoming requests to selected orchestrators
+
+
+
+## Find All Orchestrators & Offerings
+The `/getNetworkCapabilities` endpoint in [server/handlers.go](https://github.com/livepeer/go-livepeer/blob/5691cb48/server/handlers.go#L275-L295)
+exposes all available orchestrator offerings
+
+```go /getNetworkCapabilities icon="code"
+func (s *LivepeerServer) getNetworkCapabilitiesHandler() http.Handler {
+ return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
+ // Returns orchestrators with their capabilities, pricing, and hardware
+ })
+}
+```
+
+**Response Data Structure**
+
+The response uses NetworkCapabilities structure from `common/types.go` [types.go:166-176](https://github.com/livepeer/go-livepeer/blob/5691cb48/common/types.go#L166-L176)
+
+```go icon="code" title="NetworkCapabilities"
+type NetworkCapabilities struct {
+ Orchestrators []*OrchNetworkCapabilities `json:"orchestrators"`
+}
+
+type OrchNetworkCapabilities struct {
+ Address string `json:"address"`
+ LocalAddress string `json:"local_address"`
+ OrchURI string `json:"orch_uri"`
+ Capabilities *net.Capabilities `json:"capabilities"`
+ CapabilitiesPrices []*net.PriceInfo `json:"capabilities_prices"`
+ Hardware []*net.HardwareInformation `json:"hardware"`
+}
+```
+
+## Gateway
+
+Gateways expose offerings describing:
+
+### **1. Supported Models**
+
+Example:
+
+- `stable-diffusion-v1.5`
+- `depth-anything`
+- `controlnet_lineart`
+- `ip_adapter`
+
+### **2. Supported Pipelines**
+
+- Daydream-style real-time style transfer
+- ComfyStream workflows
+- BYOC containers
+- Custom inference graphs
+
+### **3. Pricing**
+
+A Gateway may price:
+
+- `$0.004 / frame`
+- `$0.06 / second`
+- `$0.0005 / inference token`
+
+### **4. Regions**
+
+Example:
+
+- `us-east`
+- `eu-central`
+- `ap-southeast`
+
+### **5. Reliability Scores**
+
+Gateways may publish:
+
+- Availability %
+- Average inference latency
+- Failover configuration
+
diff --git a/v2/pages/04_gateways/run-a-gateway/connect/lp-marketplace.mdx b/v2/pages/04_gateways/run-a-gateway/connect/lp-marketplace.mdx
new file mode 100644
index 00000000..c1d6295c
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/connect/lp-marketplace.mdx
@@ -0,0 +1,249 @@
+---
+title: 'Livepeer Marketplace Overview'
+description: 'This page provides an overview of the Livepeer Marketplace,
+including what offerings Orchestrators publish, in order to provide Gateway operators
+the context they need to discover & route application requests'
+sidebarTitle: 'Livepeer Marketplace'
+---
+import { ScrollableDiagram } from '/snippets/components/zoomable-diagram.jsx'
+
+
+
+ So... you have a gateway running - yay!
+
+
+
+
+
+
+
+
+
+
+
+# What is the Marketplace?
+The Livepeer Marketplace allows **_Orchestrators_** to advertise available compute,
+compute services (AI & Video), pricing, and performance characteristics.
+
+The Marketplace is **NOT** a public marketplace for end-users, rather, it is a programmatic
+interface for Gateways to discover and connect applications to available services.
+
+In the Livepeer Marketplace, **Gateways act like a search engine**
+
+They discover orchestrator offerings, apply selection and routing logic, and broker access to appropriate
+services for applications based on cost, performance, and policy requirements.
+
+
+
+> - **Orchestrators** publish services to the Livepeer Marketplace;
+> - **Gateways** filter & connect application requests to those services.
+
+
+
+
+```mermaid
+%%{init: {
+ 'theme': 'base',
+ 'themeVariables': {
+ 'primaryColor': '#1a1a1a',
+ 'primaryTextColor': '#ffffffff',
+ 'primaryBorderColor': '#ffffff',
+ 'lineColor': '#2d9a67',
+ 'secondaryColor': '#0d0d0d',
+ 'titleColor': '#2d9a67',
+ 'tertiaryColor': '#1a1a1a',
+ 'background': '#0d0d0d',
+ 'fontFamily': 'system-ui',
+ 'clusterBkg': '#1a1a1a',
+ 'clusterBorder': '#ffffff',
+ 'nodeTextColor': '#ffffff',
+ 'nodeBorder': '#ffffff',
+ 'mainBkg': '#1a1a1a',
+ 'edgeLabelBackground': 'transparent',
+ 'textColor': '#2d9a67'
+ },
+ 'flowchart': {
+ 'useMaxWidth': true,
+ 'htmlLabels': true
+ }
+}}%%
+flowchart TB
+
+ %% --- APPLICATION LAYER ---
+ subgraph App["APPLICATIONS / CLIENTS"]
+ A1["App / User Video or AI Request"]
+ end
+
+ %% --- GATEWAY LAYER ---
+ subgraph Gateway["GATEWAY (BROKER)"]
+ direction LR
+ G1["API Ingress"]
+ G2["Auth / Rate Limits"]
+ G3["Policy & Routing Logic"]
+ G4["SLA / Retry / Failover"]
+ end
+
+ %% --- LIVEPEER MARKETPLACE ---
+ subgraph Market["LIVEPEER MARKETPLACE"]
+ direction LR
+ M1["Capability Metadata"]
+ M2["Pricing Signals"]
+ M3["Performance Characteristics"]
+ M0[ ]
+ end
+
+ %% --- SUPPLY LAYER ---
+ subgraph Supply["COMPUTE PROVIDERS"]
+ direction LR
+ O1["Orchestrator A"]
+ O2["Orchestrator B"]
+ O3["Orchestrator C"]
+ end
+
+ %% --- FLOWS ---
+ A1 -->|API Request| G1
+ G1 --> G2
+ G2 --> G3
+ G3 --> G4
+
+ %% Marketplace lookup
+ G3 -.->|Query| Market
+
+ %% Brokered execution
+ G4 -->|Brokered Job| O1
+ G4 -->|Brokered Job| O2
+ G4 -->|Brokered Job| O3
+
+ %% Results
+ O1 -->|Results| G4
+ O2 -->|Results| G4
+ O3 -->|Results| G4
+
+ G4 -->|Response| A1
+
+ %% Compute Providers publish to Marketplace
+ O2 -.->|Publish Offerings| M0
+
+ %% Styling - white borders for main boxes, green borders for internal boxes
+ style App stroke:#ffffff,stroke-width:2px,rx:15,ry:15
+ style Gateway stroke:#ffffff,stroke-width:2px,rx:15,ry:15
+ style Market stroke:#ffffff,stroke-width:2px,rx:15,ry:15
+ style Supply stroke:#ffffff,stroke-width:2px,rx:15,ry:15
+ style A1 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style G1 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style G2 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style G3 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style G4 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style M1 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style M2 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style M3 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style O1 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style O2 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style O3 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style M0 fill:transparent,stroke:transparent,color:transparent
+```
+
+
+
+## Orchestrator Offering Details
+
+An offering is a structured declaration of:
+
+- Supported models (e.g., SDXL, ControlNet, depth models)
+- Supported pipelines (ComfyStream, Daydream, BYOC)
+- Pricing per frame / per second / per request
+- GPU tiers and performance metrics
+- Regional availability
+- SLAs and expected latency
+
+Orchestrators publish their offerings through the `OrchestratorInfo` data structure
+
+```protobuf
+message OrchestratorInfo {
+ string transcoder = 1; // Service URI
+ TicketParams ticket_params = 2; // Payment parameters
+ PriceInfo price_info = 3; // Pricing information
+ bytes address = 4; // ETH address
+ Capabilities capabilities = 5; // Supported features
+ AuthToken auth_token = 6; // Authentication
+ repeated HardwareInformation hardware = 7; // Hardware specs
+ repeated OSInfo storage = 32; // Storage options
+ repeated PriceInfo capabilities_prices = 33; // AI model pricing
+}
+```
+
+Orchestrators publish compute-level offerings to the Marketplace for Gateways to discover & route jobs to.
+
+
+```mermaid
+%%{init: {
+ 'theme': 'base',
+ 'themeVariables': {
+ 'primaryColor': '#1a1a1a',
+ 'primaryTextColor': '#ffffff',
+ 'primaryBorderColor': '#ffffff',
+ 'lineColor': '#2d9a67',
+ 'titleColor': '#2d9a67',
+ 'background': '#0d0d0d',
+ 'clusterBkg': '#1a1a1a',
+ 'clusterBorder': '#ffffff',
+ 'textColor': '#2d9a67'
+ },
+ 'flowchart': {
+ 'useMaxWidth': true,
+ 'htmlLabels': true,
+ 'subGraphTitleMargin': {
+ 'top': 15,
+ 'bottom': 30
+ }
+ }
+}}%%
+flowchart LR
+ subgraph Orchestrators["⚡ ORCHESTRATOR OFFERING DETAILS"]
+ O1["🧠 Models"]
+ O2["⚙️ Pipelines"]
+ O3["💰 Pricing"]
+ O4["🖥️ GPU Tiers"]
+ O5["🌍 Regions"]
+ O6["📊 SLAs"]
+ O1 ~~~ O2 ~~~ O3 ~~~ O4 ~~~ O5 ~~~ O6
+ end
+
+ subgraph Marketplace["🏪 LIVEPEER MARKETPLACE"]
+ MP1["Capability Metadata"]
+ MP2["Pricing Signals"]
+ MP3["Performance Data"]
+ MP1 ~~~ MP2 ~~~ MP3
+ end
+
+ subgraph Gateways["🌐 GATEWAYS DISCOVER OFFERS"]
+ GW["Discovery & Selection Route to Best Provider"]
+ end
+
+ Orchestrators -->|Publish| Marketplace
+ Marketplace <-->|Discover| Gateways
+
+ style Orchestrators fill:#1a1a1a,stroke:#ffffff,stroke-width:2px,rx:15,ry:15
+ style Marketplace fill:#1a1a1a,stroke:#ffffff,stroke-width:2px,rx:15,ry:15
+ style Gateways fill:#1a1a1a,stroke:#ffffff,stroke-width:2px,rx:15,ry:15
+
+ style GW fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style MP1 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style MP2 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style MP3 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style O1 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style O2 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style O3 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style O4 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style O5 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style O6 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+```
+
\ No newline at end of file
diff --git a/v2/pages/04_gateways/run-a-gateway/gateway-operator-opportunities.mdx b/v2/pages/04_gateways/run-a-gateway/gateway-operator-opportunities.mdx
new file mode 100644
index 00000000..e69de29b
diff --git a/v2/pages/04_gateways/run-a-gateway/get-AI-to-setup-the-gateway.mdx b/v2/pages/04_gateways/run-a-gateway/get-AI-to-setup-the-gateway.mdx
new file mode 100644
index 00000000..7a976e8a
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/get-AI-to-setup-the-gateway.mdx
@@ -0,0 +1,25 @@
+---
+title: 'Get AI to Setup the Gateway'
+description: 'Get AI to Setup the Gateway'
+sidebarTitle: 'Get AI to Setup the Gateway'
+---
+
+ Experimental (Idea Stage)
+
+This page is a downloadable task list for cursor or other AI coding agents to follow to set up your Livepeer Gateway for you - because who's got time for all that manual work?!
+
+
+
+Prompt Instructions for AI Agent:
+1. Read the instructions on the page
+2. Perform the tasks on the page
+3. Verify the tasks are completed correctly
+4. Update the page with the results of the tasks
+5. Repeat for all pages in the "Run a Gateway" section
+ - Install
+ - Configure & Fund
+ - Test
+ - Connect
+ - Monitor
+
+
diff --git a/v2/pages/04_gateways/run-a-gateway/install/community-projects.mdx b/v2/pages/04_gateways/run-a-gateway/install/community-projects.mdx
new file mode 100644
index 00000000..4345f38a
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/install/community-projects.mdx
@@ -0,0 +1,91 @@
+---
+title: Easy Install [DevOps & Community Projects]
+sidebarTitle: Single Click Deployment
+description: Community CICD Pipelines to make installation accessible & easy
+icon: timeline-arrow
+tag: beta
+---
+
+
+Page Not Finalised
+
+**Notes:**
+- Gateway hub will be an automated addition pipleine with human in the loop.
+
+**TODO:**
+- [ ] Verify all content
+- [ ] Add a real link for community submissions
+- [ ] Not happy with contribution layout
+
+
+import { YouTubeVideo } from '/snippets/components/video.jsx'
+import { GotoCard, GotoLink } from '/snippets/components/links.jsx'
+import { ExternalContent } from '/snippets/components/external-content.jsx'
+import GwidReadme from '/snippets/external/gwid-readme.mdx'
+
+# Gateway HUB
+
+A collection of community projects that make running a Livepeer Gateway easy.
+
+**Quick Links**
+
+
+ Fully Managed DevOps Platform for Livepeer
+
+
+ Coming Soon
+
+
+ Have a Guide or Project to Contribute?
+
+
+ Contribute to the Gateway Hub
+
+
+
+## GWID (Gateway Wizard)
+
+ This is a community contributed project. Please contact the team for help & support.
+
+GWID is a fully managed DevOps platform for Livepeer. It provides a simple and easy way to deploy and manage Livepeer gateways. It also provides easy integration with other services to test the gateway.
+
+
+
+
+ View the GWID repository on GitHub
+
+
+### GWID RFP & Updates
+
+- [GWID SPE Proposal: Gateway Wizard Phase 1](https://forum.livepeer.org/t/gwid-spe-pre-proposal-gateway-wizard-phase-1/2868)
+- [Get to know GWID - A Fully Managed DevOp Platfom for Livepeer](https://forum.livepeer.org/t/get-to-know-gwid-and-the-team-a-fully-managed-devop-platform-for-livepeer/2851)
+
+
+### GWID Documentation
+
+Below is the current README from the GWID repository.
+
+
+
+
+
diff --git a/v2/pages/04_gateways/run-a-gateway/install/docker-install.mdx b/v2/pages/04_gateways/run-a-gateway/install/docker-install.mdx
new file mode 100644
index 00000000..bfdcc51b
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/install/docker-install.mdx
@@ -0,0 +1,743 @@
+---
+title: Docker Install
+description: How to install a Livepeer Gateway using Docker
+sidebarTitle: Docker Install
+icon: docker
+---
+import { StyledSteps, StyledStep } from '/snippets/components/steps.jsx';
+import { DoubleIconLink } from '/snippets/components/links.jsx'
+
+ Dual AI & Video
+
+
+
+
+ TODO: Check all links and verify info
+
+
+
+ {/*
+ #### Directories & Folders
+ Livepeer will require files to be placed on the host and within the docker
+ container.
+
+
+
+ **Host Directory**
+
+ By default, docker will store all volumes in the directory at
+
+ ```bash
+ /var/lib/docker/volumes
+ ```
+
+ This installation will create a volume called: `gateway-lpData`
+ located at
+
+ ```bash
+ /var/lib/docker/volumes/gateway-lpData/_data
+ ```
+
+ **Container Directory**
+
+ Within the docker container, the volume `gateway-lpData` will be mounted at
+
+ ```bash
+ /root/.lpData
+ ```
+
+
+ For On-Chain Gateways, you will need to create a directory for your wallet
+
+ ```bash
+ # Create keystore directory
+ mkdir -p gateway-lpData/keystore
+
+ # Copy your Ethereum keystore files to gateway-lpData/keystore/
+ # Create password file with your Ethereum password
+ echo "your_password" > gateway-lpData/password.txt
+ ```
+
+
+ For AI gateways, you will need to create a directory for AI models & pipelines
+
+ ```bash
+ # AI keystore directory
+ mkdir -p ai-gateway-lpData/keystore
+ # AI Model directory
+ mkdir -p models
+ ```
+
+
+
+ */}
+
+ If docker is already installed at or above version 20.10.x, you can **skip this step**.
+
+ You can check your version by running
+ ```bash
+ docker --version
+ ```
+
+
+
+ If you have an older version of Docker installed - you will need to update the Docker Engine and CLI.
+
+ Follow the instructions for your OS and Docker type in the [Docker Docs](https://docs.docker.com/) to install the latest version of Docker or follow the terminal command guide below:
+
+ **Linux**
+ 1. Update package lists
+ ```bash
+ sudo apt-get update
+ ```
+ 2. Install the latest version of Docker
+ ```bash
+ sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
+ ```
+ 3. Verify the installation
+ ```bash
+ docker --version
+ ```
+
+ **Docker Desktop (Windows & MacOS)**
+ 1. Use the GUI
+
+ Open Application and go to `Settings > Software Updates` menu
+
+ 2. Use the CLI
+ ```bash
+ docker desktop update
+ ```
+
+
+
+ If docker is not installed, follow the instructions for your OS in the [Docker installation guide](https://app.docker.com/) to install Docker Engine & CLI or follow the (non-canonical) quick guide below:
+
+ **Linux**
+ 1. Update package lists & install dependencies
+ ```bash
+ sudo apt-get update
+ sudo apt-get install ca-certificates curl apt-transport-https lsb-release
+ ```
+ 2. Add Docker's official GPG key
+ ```bash
+ sudo mkdir -m 0755 -p /etc/apt/keyrings
+ sudo curl -fsSL download.docker.com -o /etc/apt/keyrings/docker.asc
+ sudo chmod a+r /etc/apt/keyrings/docker.asc
+ ```
+ 3. Setup the Repo
+ (Replace ubuntu with debian if you are using Debian).
+ ```bash
+ echo \
+ "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] download.docker.com \
+ $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
+ ```
+ 2. Install Docker Packages
+ ```bash
+ sudo apt-get update
+ sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
+ ```
+ 3. Verify the installation
+ ```bash
+ docker --version
+ ```
+ ```bash
+ sudo docker run hello-world
+ ```
+
+ **Windows & MacOS**
+ 1. Download Docker Desktop for [Mac](https://docs.docker.com/desktop/install/mac-install/)
+ or [Windows](https://docs.docker.com/desktop/install/windows-install/)
+ 2. Follow the instructions in the installer
+
+
+
+
+ {/*
+ Livepeer hosts a public docker image for the Livepeer Gateway.
+
+ You can pull the image from [Livepeer Docker Hub](https://hub.docker.com/r/livepeer/go-livepeer) (Recommended)
+
+ **_OR_**
+
+ You can create a docker volume for the Gateway data instead.
+
+
+
+ Fetch the latest with the following command
+ ```bash
+ docker pull livepeer/go-livepeer:master
+ ```
+
+
+ Create a Docker volume for the Gateway data
+ ```bash
+ docker volume create gateway-lpData
+ ```
+ Verify the volume was created
+ ```bash
+ docker volume ls
+ ```
+
+ Create Docker Compose file from the root user's home directory `_/root/_`
+ ```bash
+ nano docker-compose.yml
+ ```
+
+ Copy, paste & save the following volume for your Gateway mode
+
+
+ In onchain mode, the gateway requires an ETH wallet to pay for services.
+ See the [Fund Gateway Guide](/v2/pages/04_gateways/run-a-gateway/fund/fund-gateway) for more information.]
+
+ Ensure you have a directory for your wallet:
+ ```bash
+ # Create keystore directory
+ mkdir -p gateway-lpData/keystore
+
+ # Copy your Ethereum keystore files to gateway-lpData/keystore/
+ # Create password file with your Ethereum password
+ echo "your_password" > gateway-lpData/password.txt
+ ```
+
+ Video Only `docker-compose.yml`
+
+
+ ```bash
+ version: '3.9'
+
+ services:
+ gateway:
+ image: livepeer/go-livepeer:master
+ container_name: "gateway"
+ hostname: "gateway"
+ ports:
+ - 1935:1935
+ - 8935:8935
+ - 5935:5935 # CLI port
+ volumes:
+ - gateway-lpData:/root/.lpData
+ command: '-ethUrl=
+ -ethKeystorePath=/root/.lpData/keystore
+ -ethAcctAddr=
+ -ethPassword=/root/.lpData/password.txt
+ -network=arbitrum-one-mainnet
+ -cliAddr=0.0.0.0:5935
+ -gateway
+ -monitor=true
+ -v=6
+ -blockPollingInterval=20
+ -maxPricePerUnit=300
+ -pixelsPerUnit=1
+ -rtmpAddr=0.0.0.0:1935
+ -httpAddr=0.0.0.0:8935
+ -orchAddr=
+ -transcodingOptions=P240p30fps16x9,P360p30fps16x9'
+
+ volumes:
+ gateway-lpData:
+ external: true
+
+ ```
+
+
+ AI Only `docker-compose.yml`
+
+
+ Ensure you have a directory for AI models & keystore
+
+ ```bash
+ # Create directories
+ mkdir -p ai-gateway-lpData/keystore
+ mkdir -p models
+ ```
+
+ Then copy, paste & save this `docker-compose.yml`
+
+ ```bash
+ version: '3.9'
+
+ services:
+ ai-gateway:
+ image: livepeer/go-livepeer:master
+ container_name: "ai-gateway"
+ hostname: "ai-gateway"
+ ports:
+ - 8935:8935
+ - 5935:5935
+ volumes:
+ - ai-gateway-lpData:/root/.lpData
+ - ./aiModels.json:/root/.lpData/aiModels.json
+ - ./models:/root/.lpData/models
+ command: '-ethUrl=
+ -ethKeystorePath=/root/.lpData/keystore
+ -ethAcctAddr=
+ -ethPassword=/root/.lpData/password.txt
+ -network=arbitrum-one-mainnet
+ -cliAddr=0.0.0.0:5935
+ -gateway
+ -httpIngest
+ -aiServiceRegistry
+ -monitor=true
+ -v=6
+ -blockPollingInterval=20
+ -maxPricePerCapability={"capabilities_prices": [{"pipeline": "text-to-image", "model_id": "stabilityai/sd-turbo", "price_per_unit": 1000}]}
+ -httpAddr=0.0.0.0:8935
+ -orchAddr=
+ -aiModels=/root/.lpData/aiModels.json
+ -aiModelsDir=/root/.lpData/models
+ -livePaymentInterval=5s'
+ volumes:
+ ai-gateway-lpData:
+ external: true
+ ```
+
+
+
+ Dual AI & Video `docker-compose.yml`
+
+
+ Ensure you have a directory for AI models & keystore
+
+ ```bash
+ # Create directories
+ mkdir -p ai-gateway-lpData/keystore
+ mkdir -p models
+ ```
+
+ Then copy, paste & save this `docker-compose.yml`
+
+ ```bash
+ version: '3.9'
+
+ services:
+ gateway:
+ image: livepeer/go-livepeer:master
+ container_name: "gateway"
+ hostname: "gateway"
+ ports:
+ - 1935:1935
+ - 8935:8935
+ - 5935:5935
+ volumes:
+ - gateway-lpData:/root/.lpData
+ - ./aiModels.json:/root/.lpData/aiModels.json
+ - ./models:/root/.lpData/models
+ command: '-ethUrl=
+ -ethKeystorePath=/root/.lpData/keystore
+ -ethAcctAddr=
+ -ethPassword=/root/.lpData/password.txt
+ -network=arbitrum-one-mainnet
+ -cliAddr=0.0.0.0:5935
+ -gateway
+ -httpIngest
+ -monitor=true
+ -v=6
+ -blockPollingInterval=20
+ -maxPricePerUnit=300
+ -maxPricePerCapability={"capabilities_prices": [{"pipeline": "text-to-image", "model_id": "stabilityai/sd-turbo", "price_per_unit": 1000}]}
+ -pixelsPerUnit=1
+ -rtmpAddr=0.0.0.0:1935
+ -httpAddr=0.0.0.0:8935
+ -orchAddr=
+ -transcodingOptions=P240p30fps16x9,P360p30fps16x9
+ -aiModels=/root/.lpData/aiModels.json
+ -aiModelsDir=/root/.lpData/models
+ -aiServiceRegistry'
+
+ volumes:
+ gateway-lpData:
+ external: true
+ ```
+
+
+
+
+
+ You will need to run your own Orchestrator node for local development and have the `orchAddr=` point to it
+
+ In offchain mode, the gateway operates without blockchain integration, eliminating the need for ETH wallet configuration.
+ The ETH-related configuration fields default to empty strings.
+
+ `-network offchain` enables local & private operation without blockchain connectivity
+
+ Video Only `docker-compose.yml`
+
+
+ ```bash
+ version: '3.9'
+
+ services:
+ gateway:
+ image: livepeer/go-livepeer:master
+ container_name: "gateway"
+ hostname: "gateway"
+ ports:
+ - 1935:1935
+ - 8935:8935
+ - 5935:5935 # CLI port
+ volumes:
+ - gateway-lpData:/root/.lpData
+ command: '-network offchain
+ -cliAddr=0.0.0.0:5935
+ -gateway
+ -monitor=true
+ -v=6
+ -maxPricePerUnit=300
+ -pixelsPerUnit=1
+ -rtmpAddr=0.0.0.0:1935
+ -httpAddr=0.0.0.0:8935
+ -orchAddr=
+ -transcodingOptions=P240p30fps16x9,P360p30fps16x9'
+
+ volumes:
+ gateway-lpData:
+ external: true
+
+ ```
+
+ #### Notes
+ - Video Processing: RTMP ingest on `port 1935`, transcoding to multiple bitrates
+ - HTTP port 8935 for HLS output / API access
+ - `-transcodingOptions` configures video transcoding profiles (default: P240p30fps16x9,P360p30fps16x9)
+
+
+
+ AI Only `docker-compose.yml`
+
+
+ First, create a directory for AI models & pipelines
+
+ ```bash
+ # Create directories
+ mkdir -p ai-gateway-lpData/keystore
+ mkdir -p models
+ ```
+
+ Then copy, paste & save this `docker-compose.yml`
+
+ ```bash
+ version: '3.9'
+
+ services:
+ ai-gateway:
+ image: livepeer/go-livepeer:master
+ container_name: "ai-gateway"
+ hostname: "ai-gateway"
+ ports:
+ - 8935:8935
+ - 5935:5935
+ volumes:
+ - ai-gateway-lpData:/root/.lpData
+ - ./aiModels.json:/root/.lpData/aiModels.json
+ - ./models:/root/.lpData/models
+ command: '-network offchain
+ -cliAddr=0.0.0.0:5935
+ -gateway
+ -httpIngest
+ -aiServiceRegistry
+ -monitor=true
+ -v=6
+ -maxPricePerCapability={"capabilities_prices": [{"pipeline": "text-to-image", "model_id": "stabilityai/sd-turbo", "price_per_unit": 1000}]}
+ -httpAddr=0.0.0.0:8935
+ -orchAddr=
+ -aiModels=/root/.lpData/aiModels.json
+ -aiModelsDir=/root/.lpData/models
+ -livePaymentInterval=5s'
+
+ volumes:
+ ai-gateway-lpData:
+ external: true
+
+ ```
+
+ #### Notes
+ - `-aiServiceRegistry` enables AI service registry functionality
+ - `-httpIngest` required for AI HTTP endpoints livepeer.go:124
+ - `-aiModels` and `-aiModelsDir` configure AI model support
+ - AI Processing: HTTP endpoints for AI models on `port 8935`
+
+
+
+ Dual AI & Video `docker-compose.yml`
+
+
+ Ensure you have a directory for AI models & keystore
+
+ ```bash
+ # Create directories
+ mkdir -p ai-gateway-lpData/keystore
+ mkdir -p models
+ ```
+
+ Then copy, paste & save this `docker-compose.yml`
+
+ ```bash
+ services:
+ dual-gateway:
+ image: livepeer/go-livepeer:master
+ container_name: "dual-gateway"
+ hostname: "dual-gateway"
+ ports:
+ - 1935:1935 # RTMP for video ingest
+ - 8935:8935 # HTTP API for both video and AI
+ - 5935:5935 # CLI port
+ volumes:
+ - dual-gateway-lpData:/root/.lpData
+ - ./aiModels.json:/root/.lpData/aiModels.json
+ - ./models:/root/.lpData/models
+ command: '-network offchain
+ -cliAddr=0.0.0.0:5935
+ -gateway
+ -httpIngest
+ -aiServiceRegistry
+ -monitor=true
+ -v=6
+ -maxPricePerUnit=300
+ -maxPricePerCapability={"capabilities_prices": [{"pipeline": "text-to-image", "model_id": "stabilityai/sd-turbo", "price_per_unit": 1000}]}
+ -rtmpAddr=0.0.0.0:1935
+ -httpAddr=0.0.0.0:8935
+ -orchAddr=
+ -transcodingOptions=P240p30fps16x9,P360p30fps16x9
+ -aiModels=/root/.lpData/aiModels.json
+ -aiModelsDir=/root/.lpData/models
+ -livePaymentInterval=5s'
+
+ volumes:
+ dual-gateway-lpData:
+ external: true
+
+ ```
+
+ #### Notes
+ **Video-specific**
+ - Video Processing: RTMP ingest on `port 1935`, transcoding to multiple bitrates
+ - HTTP port 8935 for HLS output
+ - `-transcodingOptions` configures video transcoding profiles (default: P240p30fps16x9,P360p30fps16x9)
+
+ **AI-specific**
+ - AI Processing: HTTP endpoints for AI models on `port 8935`
+ - `-aiServiceRegistry` enables AI service registry functionality
+ - `-httpIngest` required for AI HTTP endpoints livepeer.go:124
+ - -`aiModels` and `-aiModelsDir` configure AI model support
+
+
+
+
+
+
+ */}
+
+ Fetch the latest with the following command
+
+ ```bash
+ docker pull livepeer/go-livepeer:master
+ ```
+
+
+ Start the Base Docker volume
+ ```bash
+ docker-compose up -d
+ ```
+
+ - **On-chain** files: `~/.lpData/arbitrum-one-mainnet`
+ - **Off-chain** files: `~/.lpData/offchain`
+ - **AI** files: `~/.ai-gateway-lpData`
+
+
+
+
+ Volume names can be customised as desired to avoid conflicts between different setups or Gateway instances (e.g., `ai-gateway-lpData`, `dual-gateway-lpData`)
+
+
+
+
+
+
+Jump to the configuration guide to see configuration options for the Gateway
+
+
+
+
+
+
+ I think the volumes section belongs in configuration not installation
+
+
+ Pull from Docker Hub (recommended) or build from source
+
+ You can also build locally instead of pulling from Docker Hub:
+
+ **Clone and build**
+ git clone https://github.com/livepeer/go-livepeer.git
+ cd go-livepeer
+ make livepeer
+ The Makefile shows the build process Makefile:110-112 and includes all dependencies including FFmpeg and CUDA support.
+ For development, the source build gives you more flexibility to modify and test changes.
+
+
+
+Installation vs Configuration
+Installation refers to obtaining the software:
+
+Pulling the Docker image: docker pull livepeer/go-livepeer:master
+Or building from source: make livepeer
+Configuration refers to setting up runtime parameters:
+
+Creating docker-compose.yml with command-line flags livepeer.go:112-197
+Specifying network settings, transcoding options, AI models, etc.
+More Accurate Installation Steps
+Install: Pull Docker image or build from source
+Configure: Create docker-compose.yml with your specific flags and settings
+Deploy: Run docker-compose up -d
+The docker-compose file is where you define all the configuration flags like -gateway, -network, -transcodingOptions, -aiModels, etc. starter.go:80-178 . This makes it fundamentally a configuration step that customizes how the installed software runs.
+
+Notes
+This distinction matters because:
+
+You can install the same software multiple ways (Docker, source build, binary)
+Each installation method requires different configuration approaches
+The configuration contains your business logic and operational parameters
+Installation is a one-time setup, configuration evolves with your needs
+The Livepeer repository provides examples in the box/ directory that demonstrate different configuration patterns box.md:1-119 .
+
+
+
+
+
+
+ # Create Livepeer Gateway ETH account
+
+ In this step we need to start the Gateway in order to create an Ethereum
+ account.
+
+ ```
+ docker compose run -it gateway
+ ```
+
+ When prompted for the ETH password, enter a strong password to secure your
+ Ethereum account. This password is used to decrypt and access the ETH private
+ key. Make sure to never share or lose access to either the password or
+ the keystore file.
+
+ Keep this password handy, we will use it in the following steps.
+
+ After you see the message that the Ethereum account has been unlocked, CTRL+C to
+ exit the Livepeer docker instance.
+
+ Using the previously created ETH password, create the eth-secret file
+
+ ```
+ nano -p /var/lib/docker/volumes/gateway-lpData/_data/eth-secret.txt
+ ```
+
+ # Modify Docker compose file to include eth-secret.txt
+
+ ```
+ nano docker-compose.yml
+ ```
+
+ Add the following line below the `-ethKeystorePath` and save
+
+ ```
+ -ethPassword=/root/.lpData/eth-secret.txt
+ ```
+
+ Here is the full modified version of the docker-compose.yml file
+
+ ```
+ version: '3.9'
+
+ services:
+ gateway:
+ image: livepeer/go-livepeer:
+ container_name: "gateway"
+ hostname: "gateway"
+ ports:
+ - 1935:1935
+ - 8935:8935
+ volumes:
+ - gateway-lpData:/root/.lpData
+ command: '-ethUrl=
+ -ethKeystorePath=/root/.lpData
+ -ethPassword=/root/.lpData/eth-secret.txt
+ -network=arbitrum-one-mainnet
+ -cliAddr=gateway:5935
+ -broadcaster=true
+ -monitor=true
+ -v=99
+ -blockPollingInterval=20
+ -maxPricePerUnit=300
+ -pixelsPerUnit=1
+ -rtmpAddr=0.0.0.0:1935
+ -httpAddr=0.0.0.0:8935
+ '
+ volumes:
+ gateway-lpData:
+ external: true
+ ```
+
+ Start Livepeer in the background
+
+ ```
+ docker compose up -d
+ ```
+
+ Launch the livepeer_cli
+
+ ```
+ docker exec -it gateway /bin/bash
+ livepeer_cli -host gateway -http 5935
+ ```
+
+
+
+ Broken Link
diff --git a/v2/pages/04_gateways/run-a-gateway/install/gateway-overview.mdx b/v2/pages/04_gateways/run-a-gateway/install/gateway-overview.mdx
new file mode 100644
index 00000000..f413413f
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/install/gateway-overview.mdx
@@ -0,0 +1,69 @@
+---
+title: Overview
+description:
+ This guide will walk you through the Livepeer Gateway installation and setup.
+ Steps to install for Ubuntu Linux, Docker, and Windows are provided. Choose
+ the environment you want, follow install instructions, then continue to the
+ configuration section.
+icon: Rocket
+---
+
+
+ The Livepeer Gateway was previously called the Livepeer Broadcaster so you
+ will see some commands and labels still use the Broadcaster name that haven't
+ been updated in the code.
+
+
+# Quick Links
+
+
+
+ Install & Configure Docker
+
+
+ Install & Configure Linux Binary
+
+
+ Install & Configure Windows Binary
+
+
+ Specify the resolution and bitrate for your encoding ladder
+
+
+ Add Funds to Gateway Wallet
+
+
+ Publish and consume content to the Livepeer Gateway.
+
+
+ Playback using VLC Media Player
+
+
diff --git a/v2/pages/04_gateways/run-a-gateway/install/install-overview.mdx b/v2/pages/04_gateways/run-a-gateway/install/install-overview.mdx
new file mode 100644
index 00000000..c5aae94e
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/install/install-overview.mdx
@@ -0,0 +1,102 @@
+---
+title: Installation Overview
+description: An overview of the installation process for Livepeer Gateways
+sidebarTitle: Installation Overview
+---
+
+import { DoubleIconLink } from "/snippets/components/links.jsx"
+import { GotoLink } from "/snippets/components/links.jsx"
+
+Please ensure you have read the before proceeding.
+
+## Installation Methods
+
+Installing a Gateway means installing the Gateway code.
+
+You can either install using
+1. **Docker** (recommended)
+2. Building from **source (binary)**
+3. Using community developed tooling like **GWID** Beta for one-click installation & deployment.
+
+
+## Gateway Modes
+
+You can run a gateway
+ - **Off-chain** -> dev or local mode
+ - **On-chain** -> production mode connected to the blockchain-based Livepeer network.
+
+If you plan to run in **On-Chain** mode, please read the additional requirements
+
+ View On-Chain Requirements
+
+
+## Gateway Capabilities
+
+You can run a Gateway for:
+ - Video Only -> traditional transcoding services
+ - AI Only -> AI inference services
+ - Dual: AI & Video -> both video transcoding and AI inference services
+
+
+The below installation applies to both on-chain and off-chain modes.
+
+
+
+ Install & Configure Docker
+
+
+
+ Dual
+ AI
+ Video
+
+
+ Install & Configure Linux Binary
+
+
+
+ Dual
+ AI
+ Video
+
+
+ Install & Configure Windows Binary
+
+ Linux in WSL2
+
+ Video
+
+
+ One-Click Deployment Options from the Livepeer Community
+
+ Dual
+ AI
+ Video
+
+
+
+
diff --git a/v2/pages/04_gateways/run-a-gateway/install/linux-install.mdx b/v2/pages/04_gateways/run-a-gateway/install/linux-install.mdx
new file mode 100644
index 00000000..742a5f8f
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/install/linux-install.mdx
@@ -0,0 +1,330 @@
+---
+title: Linux Install
+description: How to install a Livepeer Gateway from source binary
+sidebarTitle: Linux Install
+icon: linux
+---
+
+import { StyledStep, StyledSteps } from '/snippets/components/steps.jsx';
+import { CustomCodeBlock, CodeComponent } from '/snippets/components/code.jsx';
+import { LatestRelease } from '/snippets/automationData/globals/globals.jsx';
+
+ Dual AI & Video
+
+
+
+{/* Test - remove after verifying: */}
+
+Latest go-livepeer version: {LatestRelease} (dynamically fetched)
+
+This guide covers installing the Livepeer Gateway from source binary on Linux.
+
+
+
+
+ Ensure you have `wget` and `tar` installed & up-to-date on your system.
+ - `tar` is pre-installed on macOS and most linux distributions.
+
+ Quick Install `wget` with [Homebrew](https://brew.sh/)
+ ```bash lines icon="terminal" install wget with brew
+ # Check if wget is installed
+ brew list --versions wget
+ # Install wget if not already installed
+ brew install wget
+ ```
+
+ Other `wget` Install Options
+
+
+ You can use brew or your package manager to install `wget`
+
+
+ **Linux Ubuntu/Debian**
+ ```bash icon="terminal" lines
+ sudo apt-get update && sudo apt-get upgrade wget
+ sudo apt install -y wget
+ ```
+
+ **Alpine**
+ ```bash lines icon="terminal"
+ sudo apk update
+ sudo apk add wget
+ ```
+
+ **Fedora/RHEL/CentOS/Rocky**
+ ```bash lines icon="terminal"
+ sudo dnf update
+ sudo dnf install -y wget
+ ```
+
+ **Arch**
+ ```bash lines icon="terminal"
+ sudo pacman -Syu
+ sudo pacman -S wget
+ ```
+
+
+
+ ```bash lines icon="terminal" brew install wrap
+ # Install brew if not already installed
+ /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
+ ```
+ ```bash lines icon="terminal" version check
+ # Check if wget is installed
+ brew list --versions wget
+ brew list --versions tar
+ ```
+
+ ```bash lines icon="terminal" upgrade wget
+ # Upgrade wget if already installed
+ brew upgrade wget
+ brew upgrade tar
+ ```
+
+ ```bash lines icon="terminal" install wget
+ # Install wget if not already installed
+ brew install wget
+ ```
+
+ ```bash lines icon="terminal" update all brew packages
+ # Update all brew packages
+ brew update && bre upgrade
+ ```
+
+
+
+ MacOS users will also need to install `libx11` and `--cask xquartz`
+
+ You can use brew or curl to install `wget`
+
+ Using [brew](https://brew.sh/)
+ ```bash lines icon="terminal" brew wrap
+ # Install brew if not already installed
+ /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
+
+ # Check if wget is installed
+ brew list --versions wget
+
+ # Upgrade wget if already installed
+ brew upgrade wget
+
+ # Install wget if not already installed
+ brew install wget libx11 --cask xquartz
+
+ # Update all brew packages
+ brew update && bre upgrade
+ ```
+
+
+ Using [curl](https://curl.haxx.se/)
+
+ ```bash lines icon="terminal" curl wrap
+ curl -LO https://ftp.gnu.org/gnu/wget/wget-1.21.4.tar.gz
+ tar -xzf wget-1.21.4.tar.gz
+ cd wget-1.21.4
+ ./configure && make && sudo make install
+ ```
+
+
+
+
+
+
+
+
+ Note: {''} is dynamically fetched from the [go-livepeer releases page](https://github.com/livepeer/go-livepeer/releases) via Gtihub API.
+
+
+ In case of fetch issues: Replace {''} with the latest version number
+ ```bash lines icon="terminal" wrap wget
+ sudo wget https://github.com/livepeer/go-livepeer/releases/download//livepeer-linux-amd64.tar.gz
+ ```
+
+
+
+
+ Note: {''} is dynamically fetched from the [go-livepeer releases page](https://github.com/livepeer/go-livepeer/releases) via Gtihub API.
+
+ Intel
+
+
+
+ ```bash lines icon="terminal" wrap curl
+ curl -LO https://github.com/livepeer/go-livepeer/releases//download/livepeer-darwin-amd64.tar.gz
+ tar -zxvf livepeer-darwin-amd64.tar.gz
+ sudo mv livepeer-darwin-amd64/* /usr/local/bin/
+ livepeer -gateway
+ ```
+
+
+ Apple Silicon
+
+
+
+ ```bash lines icon="terminal" wrap curl
+ curl -LO https://github.com/livepeer/go-livepeer/releases//download/livepeer-darwin-arm64.tar.gz
+ tar -zxvf livepeer-darwin-arm64.tar.gz
+ sudo mv livepeer-darwin-arm64/* /usr/local/bin/
+ livepeer -gateway
+ ```
+
+
+
+
+
+ In case of fetch issues: Replace {''} with the latest version number
+ ```bash lines icon="terminal" wrap curl
+ curl -LO https://github.com/livepeer/go-livepeer/releases/download//livepeer-linux-amd64.tar.gz
+ ```
+
+
+
+
+ Unpack and remove the compressed file
+
+ ``` bash icon="terminal" lines
+ sudo tar -zxvf livepeer-linux-amd64.tar.gz
+ sudo rm livepeer-linux-amd64.tar.gz
+ sudo mv livepeer-linux-amd64/* /usr/local/bin/
+ ```
+
+
+
+
+
+ Off-chain mode is the default network and requires no blockchain connectivity (no wallet or RPC).
+
+ - defaultNetwork := "offchain"
+
+ ```bash icon="terminal" lines run the Gateway
+ # Run the gateway
+ livepeer -gateway
+ ```
+
+
+
+ You will need to **Generate Keystore File**
+
+
+ When generating a new keystore file, the program will prompt you for a
+ password. This password is used to decrypt the keystore file and access the
+ private key. Make sure to never share or lose access to either the password or
+ the keystore file
+
+
+ ```bash icon="terminal" lines Run the Gateway
+ # Set your Arbitrum RPC URL
+ export RPC_URL=""
+
+ # Run the gateway
+ livepeer -network arbitrum-one-mainnet -ethUrl $RPC_URL -gateway
+ ```
+
+
+ **Output Example**
+ ```bash icon="terminal" lines Off-Chain Gateway Example Output
+ >_ livepeer -gateway
+
+ *---------*------*
+ | Gateway | true |
+ *---------*------*
+ I1222 12:37:23.339916 97244 starter.go:537] ***Livepeer is running on the offchain network***
+ I1222 12:37:23.340276 97244 starter.go:554] Creating data dir: /Users//.lpData/offchain
+ I1222 12:37:23.344584 97244 starter.go:723] ***Livepeer is in off-chain mode***
+ E1222 12:37:23.345022 97244 starter.go:1586] No orchestrator specified; transcoding will not happen
+ I1222 12:37:23.350972 97244 starter.go:1827] ***Livepeer Running in Gateway Mode***
+ I1222 12:37:23.350991 97244 starter.go:1828] Video Ingest Endpoint - rtmp://127.0.0.1:1935
+ I1222 12:37:23.351002 97244 starter.go:1837] Livepeer Node version: 0.8.8
+ I1222 12:37:23.351124 97244 mediaserver.go:247] HTTP Server listening on http://127.0.0.1:9935
+ I1222 12:37:23.351398 97244 webserver.go:20] CLI server listening on 127.0.0.1:5935
+ ```
+
+
+
+
+Jump to [Configuration](/gateways/run-a-gateway/configure/configuration-overview) to
+finish configuring the Gateway
+
+
+
+
+
+# Create a file containing your Gateway Ethereum password
+
+```
+sudo mkdir /usr/local/bin/lptConfig
+sudo nano /usr/local/bin/lptConfig/node.txt
+```
+
+Enter your password and save the file
+
+
+
+# Create a system service
+
+```
+sudo nano /etc/systemd/system/livepeer.service
+```
+
+Paste and update the following startup script with your personal info:
+
+```
+[Unit]
+Description=Livepeer
+
+[Service]
+Type=simple
+User=root
+Restart=always
+RestartSec=4
+ExecStart=/usr/local/bin/livepeer -network arbitrum-one-mainnet \
+-ethUrl= \
+-cliAddr=127.0.0.1:5935 \
+-ethPassword=/usr/local/bin/lptConfig/node.txt \
+-maxPricePerUnit=300 \
+-broadcaster=true \
+-serviceAddr=:8935 \
+-transcodingOptions=/usr/local/bin/lptConfig/transcodingOptions.json \
+-rtmpAddr=0.0.0.0:1935 \
+-httpAddr=0.0.0.0:8935 \
+-monitor=true \
+-v 6
+
+[Install]
+WantedBy=default.target
+```
+
+Start the system service
+
+```
+sudo systemctl daemon-reload
+sudo systemctl enable --now livepeer
+```
+
+Open the Livepeer CLI
+
+```
+livepeer_cli -host 127.0.0.1 -http 5935
+```
+
+
\ No newline at end of file
diff --git a/v2/pages/04_gateways/run-a-gateway/install/windows-install.mdx b/v2/pages/04_gateways/run-a-gateway/install/windows-install.mdx
new file mode 100644
index 00000000..85588971
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/install/windows-install.mdx
@@ -0,0 +1,157 @@
+---
+title: Windows Install
+description: How to install a Livepeer Gateway using Windows
+sidebarTitle: Windows Install
+icon: windows
+---
+
+import { StyledSteps, StyledStep } from '/snippets/components/steps.jsx';
+import { CustomCodeBlock } from '/snippets/components/code.jsx';
+import { LatestRelease } from '/snippets/automationData/globals/globals.jsx';
+
+
+ This content is referenced from the [current docs windows install
+ guide](https://docs.livepeer.org/gateways/guides/windows-install)
+ **TODO**
+ - [ ] UNVERIFIED INSTALL DOCS - VERIFY CONTENT
+ - [ ] MOVE ETH WALLET SETUP CONTENT
+
+
+ Video Only
+
+
+Latest go-livepeer version: {LatestRelease} (dynamically fetched)
+
+This guide covers installing the Livepeer Gateway from source binary on Windows.
+
+
+ This is a Linux distribution operating in WSL2
+
+
+
+
+ Install WSL2 (Windows host)
+
+ ```bash icon="terminal" lines In Powershell(Admin)
+ wsl --install
+ # Reboot when prompted.
+ ```
+
+ ```bash icon="terminal" wrap lines Check
+ wsl --status
+ # Output: Version: WSL 2
+ # Output:Default distro: Ubuntu
+ ```
+
+ ```bash icon="terminal" wrap lines Enter WSL
+ wsl
+ ```
+
+
+ ## Download and unzip the Livepeer binary
+
+
+
+ In case of fetch issues: Replace {''} with the latest [go-livepeer release](https://github.com/livepeer/go-livepeer/releases) number
+ ```bash icon="terminal" wrap lines
+ https://github.com/livepeer/go-livepeer/releases/download//livepeer-windows-amd64.zip
+ ```
+
+
+
+
+ ## Create a bat file to launch Livepeer.
+
+ Create a file named gateway.bat:
+ ```bash icon="terminal" wrap lines
+ touch gateway.bat
+ ```
+
+ Use the following as a template, adding your personal info where needed (on-chain) and save a .bat file
+ in the same directory as the Livepeer executable.
+
+
+
+
+ ```bash icon="terminal" wrap lines
+ livepeer.exe -network=offchain -gateway -cliAddr=127.0.0.1:5935 -monitor=true -v=6 -rtmpAddr=0.0.0.0:1935 -httpAddr=0.0.0.0:8935
+
+ PAUSE
+ ```
+
+
+ ```bash icon="terminal" wrap lines
+ livepeer.exe -network=arbitrum-one-mainnet -ethUrl= -ethAcctAddr= -ethPassword= -ethKeystorePath= -gateway -cliAddr=127.0.0.1:5935 -rtmpAddr=0.0.0.0:1935 -httpAddr=0.0.0.0:8935 -maxPricePerUnit=300 -monitor=true -v=6
+
+ PAUSE
+ ```
+
+ **Required On-Chain Parameters**
+
+ Network Configuration
+ - `-network`: Must be set to the blockchain network `arbitrum-one-mainnet`
+
+ Ethereum Configuration
+ - `-ethUrl`: Ethereum JSON-RPC URL (required for on-chain)
+ - `-ethAcctAddr`: Your Ethereum account address
+ - `-ethPassword`: Password for your ETH account or path to password file
+ - `-ethKeystorePath`: Path to your keystore directory or keyfile
+
+
+
+
+
+
+ ## Start the Livepeer Gateway
+
+ Start the Livepeer Gateway using the .bat file.
+
+ ```bash icon="terminal" wrap lines
+ livepeer_cli.exe -host 127.0.0.1 -http 5935
+ ```
+
+
+ _If you'd like the Gateway to start with Windows you can create a System service
+ using [NSSM](https://nssm.cc/) or the Windows Task Scheduler._
+
+
+
+
+
+ Open the Livepeer CLI, then Jump to
+ [Configuration Options](/gateways/run-a-gateway/configure/configuration-overview) to finish
+ configuring the Gateway
+
+
+
+
+
+
+ When prompted enter and confirm a password.
+
+
+ This password is used to decrypt the keystore file and access the private key.
+ Make sure to never share or lose access to either the password or the keystore
+ file
+
+
+ After confirming your password close the terminal.
+
+
+
+ ## Create a file containing your Gateway Ethereum password
+
+ In `C:\Users\YOUR_USER_NAME\.lpData` create a txt file named `ethsecret.txt`
+ with the password you created in the previous step.
+
+ ## Add the `-ethPassword` flag to your .bat file
+
+ Add `-ethPassword=C:\Users\YOUR_USER_NAME\.lpData\ethsecret.txt` to the
+ previously created .bat file
+
+
diff --git a/v2/pages/04_gateways/run-a-gateway/monitor/monitor-and-optimise.mdx b/v2/pages/04_gateways/run-a-gateway/monitor/monitor-and-optimise.mdx
new file mode 100644
index 00000000..575d8eed
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/monitor/monitor-and-optimise.mdx
@@ -0,0 +1,107 @@
+---
+title: 'Monitor & Optimise Gateway Services'
+description: 'Monitor & Optimise Gateway Services'
+sidebarTitle: 'Monitor & Optimise'
+---
+
+import { DoubleIconLink } from '/snippets/components/links.jsx'
+import { ScrollableDiagram } from '/snippets/components/zoomable-diagram.jsx'
+
+ Currently operating as a brainstorming page
+
+## Request Routing
+
+**Request Processing Flow (both)**
+
+- **Request Validation**: OpenAPI validation middleware validates request structure
+- **Session Selection**: AISessionManager selects appropriate orchestrator based on model capability
+- **Payment Processing**: Calculates payment based on pixel count for non-live endpoints
+- **Model Execution**: Sends request to AI worker with specified model
+
+
+
+```mermaid
+%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui' }}}%%
+flowchart TB
+ A[Incoming Request] --> B[Request Validation]
+ B --> C[Session Selection]
+ C --> D[Payment Processing]
+ D --> E[Model Execution]
+ E --> F[Response]
+
+ style A fill:#1a1a1a,stroke:#2d9a67,color:#fff
+ style B fill:#1a1a1a,stroke:#2d9a67,color:#fff
+ style C fill:#1a1a1a,stroke:#2d9a67,color:#fff
+ style D fill:#1a1a1a,stroke:#2d9a67,color:#fff
+ style E fill:#1a1a1a,stroke:#2d9a67,color:#fff
+ style F fill:#1a1a1a,stroke:#2d9a67,color:#fff
+```
+
+
+
+#### Transcoding Requests
+Traditional video transcoding requests are handled through:
+
+- **RTMP ingest**: Port `1935` by default
+- **HTTP push**: `/live/{streamKey}` endpoint when `-httpIngest` is enabled
+- **HLS output**: Adaptive bitrate streams for playback
+
+#### AI Requests
+AI processing requests are routed through dedicated endpoints
+
+ (fixme) OpenAPI Spec is here: ai/worker/api/openapi.json
+
+
+ Generate images from text prompts.
+ Uses `jsonDecoder` for parsing
+
+
+ Transform images with prompts.
+ Uses `multipartDecoder` for file uploads
+
+
+ Create videos from images.
+ Uses `multipartDecoder` for file uploads
+
+
+ Upscale (enhance) images to higher resolution.
+ Uses `multipartDecoder` for file uploads
+
+
+ Apply transformations to a live video streamed to the returned endpoints.
+ Live video endpoint has specialized handling for real-time streaming with MediaMTX integration
+
+
+## Payment Models
+The dual setup handles two different payment models:
+
+#### Transcoding Payments
+
+Basis: Per video segment processed
+Method: Payment tickets sent with each segment
+Verification: Multi-orchestrator verification for quality assurance
+
+#### AI Payments
+Basis: Per pixel processed (width × height × outputs)
+Method: Pixel-based payment calculation
+Live Video: Interval-based payments during streaming
+
+
+## Operational Considerations
+#### Resource Allocation
+When running dual setup, consider:
+
+- GPU resources: Shared between transcoding and AI workloads
+- Memory: AI models require significant RAM when loaded ("warm")
+- Network: Bandwidth for both stream ingest and AI request/response
+
+#### Monitoring
+Monitor both workload types:
+
+- Transcoding: Segment processing latency, success rates
+- AI: Model loading times, inference latency, pixel processing rates
+
+#### Scaling Strategies
+- Horizontal: Deploy multiple gateway instances behind a load balancer
+- Vertical: Allocate more GPU resources for AI model parallelism
+- Specialized: Separate nodes for transcoding vs AI based on workload patterns
\ No newline at end of file
diff --git a/v2/pages/04_gateways/run-a-gateway/publish/connect-with-offerings.mdx b/v2/pages/04_gateways/run-a-gateway/publish/connect-with-offerings.mdx
new file mode 100644
index 00000000..8242ca2d
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/publish/connect-with-offerings.mdx
@@ -0,0 +1,322 @@
+---
+title: 'Discover & Connect Marketplace Compute Services'
+description: 'This page explains how to find and broker Orchestrator AI & Video Offerings via your Gateway for Livepeer Application consumption.'
+sidebarTitle: 'Discover & Connect Services'
+---
+import { CustomCallout } from '/snippets/components/links.jsx';
+import { ScrollableDiagram } from '/snippets/components/zoomable-diagram.jsx';
+
+
+ This page is a work in progress. Needs a lot of edits.
+
+ TODO:
+ - [ ] Overview,
+ - [ ] Edit (A LOT)
+ - [ ] Streamline,
+ - [ ] Format,
+ - [ ] Style,
+ - [ ] Link to github / otherresources
+
+
+
+
+
+ So... you have a gateway running - yay!
+
+ Let's find and share some Livepeer Marketplace Orchestrator Services!
+
+
+
+
+
+
+
+
+
+# What is the Marketplace?
+The Livepeer Marketplace allows **_Orchestrators_** to advertise available compute,
+compute services (AI & Video), pricing, and performance characteristics.
+
+In the Livepeer Marketplace, **Gateways act like talent agents**
+
+They discover orchestrator offerings, apply selection and routing logic, and broker access to appropriate
+services for applications based on cost, performance, and policy requirements -
+_like a talent agent scouts venues for promising artists and matches them to the right record deal._
+
+
+
+> - **Orchestrators** publish services to the Livepeer Marketplace;
+> - **Gateways** filter & connect application requests to those services.
+
+
+
+
+```mermaid
+%%{init: {
+ 'theme': 'base',
+ 'themeVariables': {
+ 'primaryColor': '#1a1a1a',
+ 'primaryTextColor': '#ffffffff',
+ 'primaryBorderColor': '#ffffff',
+ 'lineColor': '#2d9a67',
+ 'secondaryColor': '#0d0d0d',
+ 'titleColor': '#2d9a67',
+ 'tertiaryColor': '#1a1a1a',
+ 'background': '#0d0d0d',
+ 'fontFamily': 'system-ui',
+ 'clusterBkg': '#1a1a1a',
+ 'clusterBorder': '#ffffff',
+ 'nodeTextColor': '#ffffff',
+ 'nodeBorder': '#ffffff',
+ 'mainBkg': '#1a1a1a',
+ 'edgeLabelBackground': 'transparent',
+ 'textColor': '#2d9a67'
+ },
+ 'flowchart': {
+ 'useMaxWidth': true,
+ 'htmlLabels': true
+ }
+}}%%
+flowchart TB
+
+ %% --- APPLICATION LAYER ---
+ subgraph App["APPLICATIONS / CLIENTS"]
+ A1["App / User Video or AI Request"]
+ end
+
+ %% --- GATEWAY LAYER ---
+ subgraph Gateway["GATEWAY (BROKER)"]
+ direction LR
+ G1["API Ingress"]
+ G2["Auth / Rate Limits"]
+ G3["Policy & Routing Logic"]
+ G4["SLA / Retry / Failover"]
+ end
+
+ %% --- LIVEPEER MARKETPLACE ---
+ subgraph Market["LIVEPEER MARKETPLACE"]
+ direction LR
+ M1["Capability Metadata"]
+ M2["Pricing Signals"]
+ M3["Performance Characteristics"]
+ M0[ ]
+ end
+
+ %% --- SUPPLY LAYER ---
+ subgraph Supply["COMPUTE PROVIDERS"]
+ direction LR
+ O1["Orchestrator A"]
+ O2["Orchestrator B"]
+ O3["Orchestrator C"]
+ end
+
+ %% --- FLOWS ---
+ A1 -->|API Request| G1
+ G1 --> G2
+ G2 --> G3
+ G3 --> G4
+
+ %% Marketplace lookup
+ G3 -.->|Query| Market
+
+ %% Brokered execution
+ G4 -->|Brokered Job| O1
+ G4 -->|Brokered Job| O2
+ G4 -->|Brokered Job| O3
+
+ %% Results
+ O1 -->|Results| G4
+ O2 -->|Results| G4
+ O3 -->|Results| G4
+
+ G4 -->|Response| A1
+
+ %% Compute Providers publish to Marketplace
+ O2 -.->|Publish Offerings| M0
+
+ %% Styling - white borders for main boxes, green borders for internal boxes
+ style App stroke:#ffffff,stroke-width:2px,rx:15,ry:15
+ style Gateway stroke:#ffffff,stroke-width:2px,rx:15,ry:15
+ style Market stroke:#ffffff,stroke-width:2px,rx:15,ry:15
+ style Supply stroke:#ffffff,stroke-width:2px,rx:15,ry:15
+ style A1 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style G1 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style G2 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style G3 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style G4 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style M1 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style M2 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style M3 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style O1 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style O2 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style O3 fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,rx:10,ry:10
+ style M0 fill:transparent,stroke:transparent,color:transparent
+```
+
+
+
+# How to Discover & Connect Marketplace Offerings
+This page explains how Gateways can discover and offer Orchestrator Services,
+ available on the Marketplace, to Applications & Builders.
+
+
+## What Is an Orchestrator Offering?
+
+An offering is a structured declaration of:
+
+- Supported models (e.g., SDXL, ControlNet, depth models)
+- Supported pipelines (ComfyStream, Daydream, BYOC)
+- Pricing per frame / per second / per request
+- GPU tiers and performance metrics
+- Regional availability
+- SLAs and expected latency
+
+Gateways publish service-level offerings.
+Orchestrators publish compute-level offerings.
+
+
+```mermaid
+flowchart LR
+ subgraph Offerings["📦 What Is an Offering?"]
+ direction TB
+ O1["🧠 Supported Models SDXL, ControlNet, Depth"]
+ O2["⚙️ Supported Pipelines ComfyStream, Daydream, BYOC"]
+ O3["💰 Pricing per frame / second / request"]
+ O4["🖥️ GPU Tiers Performance metrics"]
+ O5["🌍 Regional Availability us-east, eu-central, ap-southeast"]
+ O6["📊 SLAs & Latency Uptime %, response time"]
+ end
+
+ subgraph Publishers["📡 Who Publishes?"]
+ direction TB
+ GW["🌐 Gateways Service-Level Offerings"]
+ ORCH["⚡ Orchestrators Compute-Level Offerings"]
+ end
+
+ subgraph Marketplace["🏪 Livepeer Marketplace"]
+ direction TB
+ MP["Discovery & Selection Fair Competition Differentiation"]
+ end
+
+ Offerings --> GW
+ Offerings --> ORCH
+ GW --> MP
+ ORCH --> MP
+
+ style Offerings fill:#1a1a1a,stroke:#2d9a67,stroke-width:2px,color:#fff
+ style Publishers fill:#1a1a1a,stroke:#2d9a67,stroke-width:2px,color:#fff
+ style Marketplace fill:#1a1a1a,stroke:#2d9a67,stroke-width:2px,color:#fff
+ style GW fill:#2d9a67,stroke:#fff,stroke-width:1px,color:#fff
+ style ORCH fill:#2d9a67,stroke:#fff,stroke-width:1px,color:#fff
+ style MP fill:#333,stroke:#2d9a67,stroke-width:2px,color:#fff
+ style O1 fill:#333,stroke:#2d9a67,stroke-width:1px,color:#fff
+ style O2 fill:#333,stroke:#2d9a67,stroke-width:1px,color:#fff
+ style O3 fill:#333,stroke:#2d9a67,stroke-width:1px,color:#fff
+ style O4 fill:#333,stroke:#2d9a67,stroke-width:1px,color:#fff
+ style O5 fill:#333,stroke:#2d9a67,stroke-width:1px,color:#fff
+ style O6 fill:#333,stroke:#2d9a67,stroke-width:1px,color:#fff
+```
+
+
+## Discovery Process
+Gateways discover orchestrators through the orchestrator pool in `discovery/discovery.go` [discovery.go:64-111](https://github.com/livepeer/go-livepeer/blob/5691cb48/discovery/discovery.go#L64-L111)
+
+1. **Query orchestrators**: Get `OrchestratorInfo` from each orchestrator
+2. **Filter capabilities & price**: Match against required capabilities & pricing limits & optionally rank results
+3. **Expose results**: Make matching orchestrator services available through HTTP endpoints
+4. **Route requests**: Forward incoming requests to selected orchestrators
+
+## Find All Orchestrators & Offerings
+The `/getNetworkCapabilities` endpoint in [server/handlers.go](https://github.com/livepeer/go-livepeer/blob/5691cb48/server/handlers.go#L275-L295)
+exposes all available orchestrator offerings
+
+```go
+func (s *LivepeerServer) getNetworkCapabilitiesHandler() http.Handler {
+ return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
+ // Returns orchestrators with their capabilities, pricing, and hardware
+ })
+}
+```
+
+**Response Data Structure**
+
+The response uses NetworkCapabilities structure from common/types.go types.go:166-176 :
+
+```go
+type NetworkCapabilities struct {
+ Orchestrators []*OrchNetworkCapabilities `json:"orchestrators"`
+}
+
+type OrchNetworkCapabilities struct {
+ Address string `json:"address"`
+ LocalAddress string `json:"local_address"`
+ OrchURI string `json:"orch_uri"`
+ Capabilities *net.Capabilities `json:"capabilities"`
+ CapabilitiesPrices []*net.PriceInfo `json:"capabilities_prices"`
+ Hardware []*net.HardwareInformation `json:"hardware"`
+}
+```
+
+## Publishing as a Gateway
+
+Gateways expose offerings describing:
+
+### **1. Supported Models**
+
+Example:
+
+- `stable-diffusion-v1.5`
+- `depth-anything`
+- `controlnet_lineart`
+- `ip_adapter`
+
+### **2. Supported Pipelines**
+
+- Daydream-style real-time style transfer
+- ComfyStream workflows
+- BYOC containers
+- Custom inference graphs
+
+### **3. Pricing**
+
+A Gateway may price:
+
+- `$0.004 / frame`
+- `$0.06 / second`
+- `$0.0005 / inference token`
+
+### **4. Regions**
+
+Example:
+
+- `us-east`
+- `eu-central`
+- `ap-southeast`
+
+### **5. Reliability Scores**
+
+Gateways may publish:
+
+- Availability %
+- Average inference latency
+- Failover configuration
+
+
+## Summary
+
+Publishing offerings to the Marketplace enables:
+
+- Discoverability
+- Fair competition
+- Informed selection
+- Differentiation and specialization
+
+This is crucial for the growth of Livepeer’s decentralized AI compute economy.
diff --git a/v2/pages/04_gateways/run-a-gateway/requirements/old_reqs.mdx b/v2/pages/04_gateways/run-a-gateway/requirements/old_reqs.mdx
new file mode 100644
index 00000000..ce590163
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/requirements/old_reqs.mdx
@@ -0,0 +1,103 @@
+
+### All Nodes
+
+
+ You should have a basic understanding of system administration and CLI tooling.
+
+
+ Gateways do not require GPU resources, but must be able to handle high network throughput.
+ This is necessary to route requests between applications and Orchestrators.
+
+
+ **[A typical setup includes]('')**
+
+
4–8 CPU cores
+
16–32 GB RAM
+
High-speed NVMe (optional, recommended)
+
Stable multi-region networking
+
Linux or containerised deployment environment
+
+
+
+
+ Your Gateway must be reachable and responsive.
+ - Public HTTPs endpoint
+ - Low-latency connectivity to Orchestrators
+ - Ability to handle high request throughput
+
+ Recommended:
+
+ - Multi-region deployment or failover
+ - Static IP or domain name (required for production)
+
+
+
+ Gateways install the [Go-Livepeer Gateway](https://github.com/livepeer/go-livepeer) Software.
+ Installation requires the following OS with root or sudo access:
+
+
+
**[OS Requirements]('')**
+
+ Video Only Gateway:
+
+
Linux, Windows or Docker containerised deployment environment
+
+
+
+ **AI or Dual Gateway:**
+
+
Linux OS (Windows and macOS support coming soon)
+
+
+
+
+
+
+
+ For real production deployments (rather than local testing),
+
+
Popular RPC services include [Infura](https://www.infura.io/) and [Alchemy](https://www.alchemy.com/)
+
These services provide free tiers that should be sufficient for a single Gateway
+
+ If scaling beyond this, an alternative is to self-host an Arbitrum node.
+ Self-hosting an RPC is covered in this
+
+
+
+
+ **A funded Ethereum account (wallet)**
+
+
with ETH funds on Arbitrum to pay for services
+
+
+
+
+
+
+
+ If you are running an AI Gateway, you must configure model and pipeline metadata.
+
+ **Linux host** (Windows/macOS are NOT currently supported - though coming soon) with root or sudo access.
+
+ This is covered in detail in
+
+
+
+
+
+
diff --git a/v2/pages/04_gateways/run-a-gateway/requirements/on-chain setup/fund-gateway.mdx b/v2/pages/04_gateways/run-a-gateway/requirements/on-chain setup/fund-gateway.mdx
new file mode 100644
index 00000000..95415bad
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/requirements/on-chain setup/fund-gateway.mdx
@@ -0,0 +1,86 @@
+---
+title: Fund The Livepeer Gateway
+sidebarTitle: 'Fund Gateway'
+icon: ethereum
+description:
+ The following steps will walk you through adding funds to your Gateway
+ ETH account, including funding the ETH account on Ethereum Mainnet,
+ bridging the funds to Arbritrum's L2 Network, and then using the Livepeer
+ CLI to allocate the proper deposit and reserve amounts.
+tag: on-chain
+---
+
+
+ Ported from v1 docs - needs review
+
+ - [ ] Verify all content
+ - [ ] Verify all links
+ - [ ] Needs Introduction - why are we doing this? In what context (production only)?
+
+
+
+# Add Funds to Gateway Wallet
+
+In order to operate the Gateway in production you need to have Ethereum on the [Arbitrum](https://arbitrum.io/) L2 Blockchain - which is where Livepeer's smart contracts are deployed and that provides the payment layer for Livepeer.
+
+
+ Not Web3 native?
+
+ Each blockchain operates as it's own network and uses it's own currency. Ethereum is the currency for the Ethereum L1 Network and Arbitrum ETH is the
+ currency for the Arbitrum L2 Network. Arbitrum is a scaling solution for the Ethereum network - it operates by batching transactions and processing them
+ off-chain then reconciling them with the Ethereum mainnet, kind of like a store would tally all their sales each day and reconcile their receipts.
+ This makes transactions on Arbitrum much cheaper than on Ethereum, while still providing the security and trust of the Ethereum network.
+
+
+
+You can send ETH to your Gateway address on Ethereum Mainnet and then bridge it to Arbitrum's L2 Network.
+
+
+ _If you have ETH on the Arbitrum L2 Network, you can simply transfer the funds
+ to the newly created Gateway ETH Account._
+
+
+ _Livepeer runs on the Arbitrium's L2 Network and requires the funds to be
+ bridged._
+
+
+# Bridge Funds to Arbitrum
+
+If you need to bridge ETH you can use the official bridge
+https://bridge.arbitrum.io/ or use an exchange that supports L2 transfers. For
+additonal information on bridging view the
+[Livepeer bridging guide.](/delegators/guides/bridge-lpt-to-arbitrum)
+
+Once you have ETH on the Arbitrum network, transfer it to your newly created
+Gateway address.
+
+# Deposit Gateway Funds via Livepeer CLI
+
+
+ **For production environments**, we recommend a **Reserve** of at least 0.36 ETH to prevent service interruptions during gas spikes. The higher reserve amount helps maintain service continuity during periods of high gas prices on the network. There is [an issue open](https://github.com/livepeer/go-livepeer/issues/3744) to reduce this requirement in the future.
+
+
+We now need to divide the Gateway funds into a **Deposit** and **Reserve**
+
+In this guide we are using a total of 0.1 ETH. This is minimum recommended and
+best suited for testing.
+
+To calculate the price your Gateway will pay for transcoding, divide the
+_Reserve_ amount by 100. In our example each payment will be 0.0003 ETH (0.03
+/ 100)
+
+As you pay for transcoding the amount paid is subtracted from your _Deposit_, so
+make sure to monitor your _Deposit_ balance and top it off to keep your Gateway
+transcoding.
+
+## Open the Livepeer CLI
+
+Open the Livepeer CLI by following the instructions for your platform.
+
+Choose **Option 11. Invoke "deposit broadcasting funds" (ETH)**
+
+- Enter 0.065 for the **Deposit** and 0.03 for the **Reserve** amounts when
+ prompted.
+
+Choose **Option 1. Get node status** and confirm that the correct amounts are
+visible in the **BROADCASTER STATS** section.
diff --git a/v2/pages/04_gateways/run-a-gateway/requirements/on-chain setup/on-chain.mdx b/v2/pages/04_gateways/run-a-gateway/requirements/on-chain setup/on-chain.mdx
new file mode 100644
index 00000000..9f20426e
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/requirements/on-chain setup/on-chain.mdx
@@ -0,0 +1,475 @@
+---
+title: On-Chain Setup Requirements
+description: This page will take you through setting up the additional requirements for running a Gateway in On-Chain mode including finding an RPC URL, and creating an Ethereum account and keystore.
+sidebarTitle: On-Chain Setup
+icon: chain
+---
+import { StyledSteps, StyledStep } from '/snippets/components/steps.jsx';
+import { DoubleIconLink } from '/snippets/components/links.jsx';
+import { ChainlistRPCs } from '/snippets/components/chainlist.jsx';
+
+
+Incomplete
+
+
+## On-Chain Requirements
+
+Livepeer is currently deployed on the Arbitrum L2 network (Arbitrum One).
+In order to interact with the Livepeer smart contracts you will need to connect to an Arbitrum RPC.
+
+If you plan to run your Gateway in **On-Chain** mode, you will need:
+- An Ethereum account with funds to pay for transaction fees
+- An Ethereum RPC URL to connect to the Arbitrum network where Livepeer is deployed
+
+#### Required On-Chain Flags
+
+ _Network Configuration_
+
+ `-network`
+
+
+ Set to the blockchain network `arbitrum-one-mainnet`
+
+
+
+ _Funding Account Configuration_
+
+ `-ethUrl`, `-ethAcctAddr`, `-ethPassword`, `-ethKeystorePath`
+
+
+ Ethereum JSON-RPC URL
+
+
+ Your Ethereum account address
+
+
+ Password for your ETH account or path to password file
+
+
+ Path to your keystore directory or keyfile
+
+
+
+## Security Notes
+
+- Never share your `keystore` files - they contain your encrypted private keys
+- Use strong passwords for `keystore` encryption
+- Back up your `keystore` securely
+- The `ethPassword` only protects the `keystore` file - your actual private key is stored encrypted within the keystore
+- Never share your wallet private key. In case of accidental public exposure - remove any funds & change your wallet immediately
+
+
+## TL;DR: Quickstart Setup
+
+Livepeer will automatically create a new wallet & keystore for you if you do not provide an existing wallet address.
+
+Use the below command to quickstart an on-chain gateway.
+
+```bash icon="terminal" wrap lines On-Chain Quickstart Command
+livepeer -gateway \
+ -network arbitrum-one-mainnet \
+ -ethUrl=https://arb1.arbitrum.io/rpc \
+ -ethAcctAddr="" \
+ -ethKeystorePath="" \
+ -ethPassword=""
+```
+
+**Where Your Account Data Is Stored**
+
+- _Account Address_: Created and stored in
+ ```bash
+ # Account Address
+ ~/.lpData/arbitrum-one-mainnet/keystore/
+ ```
+- _Keystore File_: Located at
+ ```bash wrap
+ # Keystore file
+ ~/.lpData/arbitrum-one-mainnet/keystore/UTC--{timestamp}--{address}
+ ```
+- _Password_: Livepeer prompts you to enter and confirm a password
+
+
+Next Steps
+
+
+
+
+
+
+
+## Setup: On-Chain Full Guide
+Full Guide to options for setting up an on-chain Gateway
+
+
+
+
+ Set to the blockchain network `arbitrum-one-mainnet`
+
+
+
+ You can use any Arbitrum One [RPC](https://en.wikipedia.org/wiki/Remote_procedure_call) URL.
+ - Public RPCs
+ - Third-party RPC providers
+ - Self-hosted RPC
+
+ {/* #### Quickstart
+
+ Skip the reading - use the Arbitrum-provided public RPC below
+
+ ```bash icon="terminal" wrap lines Quickstart: Arbitrum-provided public RPC
+ -ethUrl=https://arb1.arbitrum.io/rpc
+ ```
+ */}
+
+
+
+ #### Public RPCs
+ Many of the public RPCs apply rate-limits, including the third-party providers.
+ These free-tier RPC's should be sufficient to run a single Gateway with the latest versions of Livepeer.
+
+ Chainlist provides a full list of public Arbitrum One RPCs (including the Arbitrum public RPC):
+ - Original Source
+ - Dynamically Imported:
+
+
+
+ You can also check the RPC status on [Chainlist](https://chainlist.org/chain/42161)
+
+
+
+ #### Paid RPCs
+ If scaling beyond one Gateway, or running a large number of concurrent requests, you will need to pay for additional RPC capacity on one of the RPC providers.
+
+ Some popular third-party RPC providers include:
+
+ | Provider | Arbitrum One | Websocket (wss)? | Stylus Tracing? |
+ |----------|----------|------------|-----------------|
+ | [Alchemy](https://www.alchemy.com/docs/reference/arbitrum-api-quickstart) | ✅ | ✅ | Available on paid plans |
+ | [Ankr](https://www.ankr.com/) | ✅ | ✅ | Available on paid plans |
+ | [Chainstack](https://chainstack.com/) | ✅ | ✅ | Available on paid plans |
+ | [Infura](https://www.infura.io/) | ✅ | ✅ | Enabled on request |
+ | [Moralis](https://moralis.com/) | ✅ | | |
+ | [Quicknode](https://www.quicknode.com/) | ✅ | ✅ | Testnet supported in free tier |
+
+ Arbitrum One shares third-party providers in the
+
+
+
+
+ #### Self-Hosted RPC
+ Alternatively, you can also self-host your own Arbitrum node.
+
+ Self-hosting an RPC is covered in the
+
+
+
+
+
+ Blockchain wallets (accounts) have both a public account address (starting with "0x...") and a **private** key.
+
+ This field is for your **public** wallet address.
+
+
+
+ Livepeer automatically creates a wallet for you if this field is empty.
+
+ `-ethAcctAddr=""`
+
+
+ Your **public** wallet address: `0x...`
+
+ Example: 0xc7653d426f2ec8bc33cdde08b15f535e2eb2f523
+
+
+
+
+
+ ONLY use your _**PUBLIC**_ Wallet Address in this field.
+
+ _**NEVER**_ use your PRIVATE key.
+
+ A public address is akin to your bank account number, a private key is like your bank PIN.
+
+
+ You can
+ - Use an existing Ethereum wallet address (e.g., from MetaMask, hardware wallet, etc.)
+ - Let Livepeer automatically create a new wallet address. See code [accountmanager.go](https://github.com/livepeer/go-livepeer/blob/5691cb48/accountmanager.go#L50-L69)
+
+ **Account Address** will be stored in
+ ```bash
+ # Account Address
+ ~/.lpData/arbitrum-one-mainnet/keystore/
+ ```
+
+
+
+
+ You can use any existing Ethereum wallet address which can transact on Arbitrum.
+
+ You will use [Arbitrum One Mainnet](https://docs.arbitrum.io/get-started/arbitrum-introduction) to transact on the Livepeer network as this is significantly cheaper than using Ethereum, so ensure your wallet can transact on Arbitrum.
+
+ It's advisable to use a wallet you own the private keys for rather than an exchange wallet.
+
+ The following guides are provided as a reference only - no recommendation is made for any specific wallet provider.
+ -
+ -
+ -
+
+
+
+
+
+ Livepeer will automatically create a new wallet for you if you do not provide an existing wallet address.
+ Simply leave the -ethAcctAddr flag empty and Livepeer will create a new wallet for you.
+
+ ```bash
+ # Automatic Account Address
+ -ethAcctAddr=""
+ ```
+
+
+
+
+
+
+
+ This is **NOT** your wallet private key.
+
+ This password is used to decrypt the `keystore` file and access the (encrypted) private key.
+
+ Make sure to never share or lose access to either the password or the keystore
+ file
+
+
+
+
+
+
+
+ Jump to the funding your gateway guide
+
+
+
+
+
+
+ ### ETH Account
+
+ **Docker**
+
+ Create Livepeer Gateway ETH account
+
+ In this step we need to start the Gateway in order to create an Ethereum
+ account.
+
+ ```
+ docker compose run -it gateway
+ ```
+
+ When prompted for the ETH password, enter a strong password to secure your
+ Ethereum account. This password is used to decrypt and access the ETH private
+ key. Make sure to never share or lose access to either the password or
+ the keystore file.
+
+ Keep this password handy, we will use it in the following steps.
+
+ After you see the message that the Ethereum account has been unlocked, CTRL+C to
+ exit the Livepeer docker instance.
+
+ Using the previously created ETH password, create the eth-secret file
+
+ ```
+ nano -p /var/lib/docker/volumes/gateway-lpData/_data/eth-secret.txt
+ ```
+
+ Modify Docker compose file to include eth-secret.txt
+
+ ```bash
+ nano docker-compose.yml
+ ```
+
+ Add the following line below the `-ethKeystorePath` and save
+
+ ```bash
+ -ethPassword=/root/.lpData/eth-secret.txt
+ ```
+
+ Here is the full modified version of the docker-compose.yml file
+
+ ```bash
+ version: '3.9'
+
+ services:
+ gateway:
+ image: livepeer/go-livepeer:
+ container_name: "gateway"
+ hostname: "gateway"
+ ports:
+ - 1935:1935
+ - 8935:8935
+ volumes:
+ - gateway-lpData:/root/.lpData
+ command: '-ethUrl=
+ -ethKeystorePath=/root/.lpData
+ -ethPassword=/root/.lpData/eth-secret.txt
+ -network=arbitrum-one-mainnet
+ -cliAddr=gateway:5935
+ -broadcaster=true
+ -monitor=true
+ -v=99
+ -blockPollingInterval=20
+ -maxPricePerUnit=300
+ -pixelsPerUnit=1
+ -rtmpAddr=0.0.0.0:1935
+ -httpAddr=0.0.0.0:8935
+ '
+ volumes:
+ gateway-lpData:
+ external: true
+ ```
+
+ Start Livepeer in the background
+
+ ```bash
+ docker compose up -d
+ ```
+
+ Launch the livepeer_cli
+
+ ```bash
+ docker exec -it gateway /bin/bash
+ livepeer_cli -host gateway -http 5935
+ ```
+
+
+
+
+
+ **Linux**
+
+
+
+
+
+ Create a file containing your Gateway Ethereum password
+
+ ```
+ sudo mkdir /usr/local/bin/lptConfig
+ sudo nano /usr/local/bin/lptConfig/node.txt
+ ```
+
+ Enter your password and save the file
+
+
+
+
+
+ Create a system service
+
+ ```
+ sudo nano /etc/systemd/system/livepeer.service
+ ```
+
+ Paste and update the following startup script with your personal info:
+
+ ```
+ [Unit]
+ Description=Livepeer
+
+ [Service]
+ Type=simple
+ User=root
+ Restart=always
+ RestartSec=4
+ ExecStart=/usr/local/bin/livepeer -network arbitrum-one-mainnet \
+ -ethUrl= \
+ -cliAddr=127.0.0.1:5935 \
+ -ethPassword=/usr/local/bin/lptConfig/node.txt \
+ -maxPricePerUnit=300 \
+ -broadcaster=true \
+ -serviceAddr=:8935 \
+ -transcodingOptions=/usr/local/bin/lptConfig/transcodingOptions.json \
+ -rtmpAddr=0.0.0.0:1935 \
+ -httpAddr=0.0.0.0:8935 \
+ -monitor=true \
+ -v 6
+
+ [Install]
+ WantedBy=default.target
+ ```
+
+ Start the system service
+
+ ```
+ sudo systemctl daemon-reload
+ sudo systemctl enable --now livepeer
+ ```
+
+ Open the Livepeer CLI
+
+ ```
+ livepeer_cli -host 127.0.0.1 -http 5935
+ ```
+
+
+
+
+ **Windows**
+
+
+ When prompted enter and confirm a password.
+
+
+ This password is used to decrypt the keystore file and access the private key.
+ Make sure to never share or lose access to either the password or the keystore
+ file
+
+
+ After confirming your password close the terminal.
+
+
+
+ ## Create a file containing your Gateway Ethereum password
+
+ In `C:\Users\YOUR_USER_NAME\.lpData` create a txt file named `ethsecret.txt`
+ with the password you created in the previous step.
+
+ ## Add the `-ethPassword` flag to your .bat file
+
+ Add `-ethPassword=C:\Users\YOUR_USER_NAME\.lpData\ethsecret.txt` to the
+ previously created .bat file
+
+
+
+ ### Funding Your ETH Account
+ See
+
+
+ - `-ethUrl`: Ethereum JSON-RPC URL (required for on-chain)
+ - `-ethAcctAddr`: Your Ethereum account address
+ - `-ethPassword`: Password for your ETH account or path to password file
+ - `-ethKeystorePath`: Path to your keystore directory or keyfile
+
+
+
+ Development Setup
+ For testing, use the devtool to create keys :
+
+ ```
+ func CreateKey(keystoreDir string) string {
+ keyStore := keystore.NewKeyStore(keystoreDir, keystore.StandardScryptN, keystore.StandardScryptP)
+ account, err := keyStore.NewAccount(passphrase)
+ return account.Address.Hex()
+ }
+ ```
+
\ No newline at end of file
diff --git a/v2/pages/04_gateways/run-a-gateway/requirements/setup.mdx b/v2/pages/04_gateways/run-a-gateway/requirements/setup.mdx
new file mode 100644
index 00000000..7d7edc1f
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/requirements/setup.mdx
@@ -0,0 +1,158 @@
+---
+title: Gateway Node Requirements
+sidebarTitle: Setup Checklist
+description: Learn about the hardware, network, and software requirements for running a Livepeer Gateway.
+icon: clipboard-user
+---
+
+import { DoubleIconLink } from '/snippets/components/links.jsx'
+import { StyledSteps } from '/snippets/components/steps.jsx'
+
+
+ TODO: Verify
+
+
+## Gateway Modes
+
+You can run a gateway
+ - **Off-chain** -> dev or local mode
+ - **On-chain** -> production mode connected to the blockchain-based Livepeer network.
+
+## Gateway Capabilities
+
+You can run a Gateway for:
+ - Video Only -> traditional transcoding services
+ - AI Only -> AI inference services
+ - Dual: AI & Video -> both video transcoding and AI inference services
+
+## Gateway Set Up Requirements
+
+
+
+ Dual AI & Video
+
+ A basic understanding of system administration and CLI tooling... or know how to ask AI for help :)
+
+
+ Dual AI & Video
+
+ Gateways do not require GPU resources, but must be able to handle high network throughput.
+ This is necessary to route requests between applications and Orchestrators.
+
+
+ **[A typical setup includes](#)**
+
+
4–8 CPU cores
+
16–32 GB RAM
+
High-speed NVMe (optional, recommended)
+
Stable multi-region networking
+
Linux or containerised deployment environment
+
+
+
+
+ Dual AI & Video
+
+ Your Gateway must be reachable and responsive.
+ - Public HTTPs endpoint
+ - Low-latency connectivity to Orchestrators
+ - Ability to handle high request throughput
+
+ Recommended:
+
+ - Multi-region deployment or failover
+ - Static IP or domain name (required for production)
+
+
+
+
+
+ Gateways install the Software.
+
+ Installation requires the following OS with **root or sudo access**:
+
+
+
**[OS Requirements](#)**
+
+ Video Only Gateway:
+
+
Linux, Windows or Docker containerised deployment environment
+
+
+
+ **AI or Dual Gateway:**
+
+
Linux OS (Windows and macOS support coming soon)
+
+
+
+
+
+
+
+ Dual AI & Video
+
+ You can run a gateway
+ - ** Off-chain** -> dev or local mode
+ - ** On-chain** -> production mode connected to the blockchain-based Livepeer network.
+
+
+
+ Additional requirements apply when running a Gateway in off-chain mode:
+
+ You will **need to run an Orchestrator Node** locally to test Gateway functionality.
+
+
+ **[This requires that you]('')**
+
+ Have a GPU available (locally or cloud) with root or sudo access
+
+
+ Setup the GPU as an Orchestrator per the
+
+
+
+ Off-chain mode is ideal for:
+
+ - Local development and testing
+ - Learning the gateway functionality
+ - Prototyping without financial commitments
+ - Running private transcoding infrastructure
+
+
+ You will need a blockchain wallet and RPC to connect to the Livepeer Network (on [Arbitrum](https://arbitrum.io/)) and pay for services.
+
+
+
+
+
+ See the full on-chain setup guide
+
+
+ On-chain mode is for:
+ - Public Production Gateways
+ - Running a business
+
+
+
+
\ No newline at end of file
diff --git a/v2/pages/04_gateways/run-a-gateway/run-a-gateway.mdx b/v2/pages/04_gateways/run-a-gateway/run-a-gateway.mdx
new file mode 100644
index 00000000..c4f79d61
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/run-a-gateway.mdx
@@ -0,0 +1,216 @@
+---
+title: Run a Gateway
+sidebarTitle: Run A Gateway
+description: "Connect Applications with Video & AI services by running your own Gateway! \n This page gives an overview of the steps to run a Gateway node."
+---
+
+import { GotoLink } from '/snippets/components/links.jsx'
+import { ScrollableDiagram } from "/snippets/components/zoomable-diagram.jsx"
+import { StyledSteps, StyledStep } from '/snippets/components/steps.jsx'
+
+
+## Introduction
+Gateways are essential infrastructure in the Livepeer network.
+They provide the service coordination layer (routing & verification) that connects applications to the decentralized GPU compute layer (DePIN).
+This guide explains the requirements, setup steps, and best practices for running a Gateway node."
+
+## Gateway Modes
+
+You can run a gateway
+ - **Off-chain** -> dev or local mode
+ - **On-chain** -> production mode connected to the blockchain-based Livepeer network (on Arbitrum).
+
+## Gateway Capabilities
+
+You can run a Gateway for:
+ - Video Only -> traditional transcoding services
+ - AI Only -> AI inference services
+ - Dual: AI & Video -> both video transcoding and AI inference services
+
+
+## Gateway Architecture
+
+
+```mermaid
+%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui' }}}%%
+flowchart LR
+ subgraph INPUT["Input Sources"]
+ CAM["Camera / RTMP / WebRTC"]
+ VID["Video File"]
+ AIIN["AI Prompt / Model Request"]
+ end
+
+ GATEWAY["Gateway Node • Ingest (RTMP/HTTP/WebRTC) • Segment video • Queue + order jobs • AI pipeline routing • Orchestrator selection • Verification & receipts"]
+
+ CAM -->|"Live stream"| GATEWAY
+ VID -->|"VOD upload"| GATEWAY
+ AIIN -->|"AI job request"| GATEWAY
+
+ subgraph JOBS["Workflows"]
+ VJ["Video Transcoding Job"]
+ AIJ["AI Inference Job (Daydream / ComfyStream / BYOC)"]
+ end
+
+ GATEWAY --> VJ
+ GATEWAY --> AIJ
+
+ subgraph ORCH["Orchestrator Network (GPU Operators)"]
+ O1["Orchestrator A GPU Pool"]
+ O2["Orchestrator B GPU Pool"]
+ O3["Orchestrator C GPU Pool"]
+ end
+
+ VJ -->|"Transcode segments"| O1
+ VJ --> O2
+ AIJ -->|"Run model / inference"| O1
+ AIJ --> O3
+
+ subgraph OUTPUTS["Outputs"]
+ HLS["Adaptive Bitrate Video (HLS/LL-HLS)"]
+ AIOUT["AI Frames / Stylized Video"]
+ end
+
+ O1 --> GATEWAY
+ O2 --> GATEWAY
+ O3 --> GATEWAY
+
+ GATEWAY --> HLS
+ GATEWAY --> AIOUT
+
+ ETH[("Arbitrum Blockchain Payments • Tickets • Rewards")]
+ GATEWAY --> ETH
+ O1 --> ETH
+ O2 --> ETH
+ O3 --> ETH
+
+ classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px
+ style INPUT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style JOBS fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style ORCH fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+ style OUTPUTS fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px
+```
+
+
+
+
+## Gateway Operator Journey
+
+
+
+ B
+ B --> C1
+ C1 --> C2
+ C2 --> D
+ D --> E1
+ E1 --> E2
+ E2 --> F
+
+ classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px`}
+ />
+
+
+
+
+
+ Check hardware, network, and software requirements.
+
+
+
+ Install the Livepeer Gateway software.
+
+
+
+ Configure transcoding options, models, pipelines & pricing
+
+
+
+ Price & publish offerings to the Marketplace.
+
+
+
+ Connect with Orchestrators, price & route offerings in the Marketplace.
+
+
+
+ Monitor performance, optimize routing & service quality.
+
+
+
+
+
+
+
+## Related Pages
+
+ Looking for information on how gateways earn fees for services?
+
+
+
+ Just want to get started?
+
+
\ No newline at end of file
diff --git a/v2/pages/04_gateways/run-a-gateway/v1/transcoding-options.mdx b/v2/pages/04_gateways/run-a-gateway/v1/transcoding-options.mdx
new file mode 100644
index 00000000..202c3c67
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/v1/transcoding-options.mdx
@@ -0,0 +1,93 @@
+---
+title: Configure Transcoding Options
+icon: gear
+description:
+ To better control your encoding profiles it is recommended to use a json file
+ to specify the resolution and bitrate for your encoding ladder.
+---
+
+# Create the JSON file
+
+Use the following as a template for your json file
+
+```
+[
+{
+ "name": "480p0",
+ "fps": 0,
+ "bitrate": 1600000,
+ "width": 854,
+ "height": 480,
+ "profile": "h264constrainedhigh",
+ "gop": "1"
+},
+{
+ "name": "720p0",
+ "fps": 0,
+ "bitrate": 3000000,
+ "width": 1280,
+ "height": 720,
+ "profile": "h264constrainedhigh",
+ "gop": "1"
+},
+{
+ "name": "1080p0",
+ "fps": 0,
+ "bitrate": 6500000,
+ "width": 1920,
+ "height": 1080,
+ "profile": "h264constrainedhigh",
+ "gop": "1"
+}
+]
+```
+
+## Modify Docker Config
+
+Create the transcodingOptions.json file using the above template.
+
+```
+nano -p /var/lib/docker/volumes/gateway-lpData/_data/transcodingOptions.json
+```
+
+Modify the docker-compose.yml file from the root user's home directory _/root/_
+and add the following below `-pixelsPerUnit=1`
+
+```
+-transcodingOptions=/root/.lpData/transcodingOptions.json
+```
+
+## Modify Linux Config
+
+Create the transcodingOptions.json file using the above template.
+
+```
+sudo nano /usr/local/bin/lptConfig/transcodingOptions.json
+```
+
+Modify the Linux Service file /etc/systemd/system/livepeer.service and add the
+following below `-pixelsPerUnit=1`
+
+```
+-transcodingOptions=/usr/local/bin/lptConfig/transcodingOptions.json \
+```
+
+## Modify Windows Config
+
+Create the transcodingOptions.json file using the above template.
+
+Open notepad (or your text editor of choice) paste the template above and save
+the transcodingOptions.json file in the following location.
+
+**Note:** Replace **YOUR_USER_NAME** with your actual user name
+
+```
+C:\Users\YOUR_USER_NAME\.lpData\transcodingOptions.json
+```
+
+Modify Windows bat file to include the following command after
+`-pixelsPerUnit=1`
+
+```
+-transcodingOptions=C:\Users\YOUR_USER_NAME\.lpData\transcodingOptions.json
+```
diff --git a/v2/pages/04_gateways/run-a-gateway/why-run-a-gateway.mdx b/v2/pages/04_gateways/run-a-gateway/why-run-a-gateway.mdx
new file mode 100644
index 00000000..61df672c
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/why-run-a-gateway.mdx
@@ -0,0 +1,130 @@
+---
+title: 'Why You Should Run a Gateway'
+description: 'Reasons you should run a Livepeer Gateway'
+sidebarTitle: 'Why Run a Gateway'
+---
+ **Business Hat Time!**
+
+As discussed in the Gateway Economics section, Gateways in Livepeer do not currently earn _protocol_ fees - by design.
+
+
+Read about Gateway Economics Here
+
+
+Instead, Gateways sit at the demand, control, and product layer of the Livepeer network.
+
+They are not just services routers - they are also where businesses, products, SLAs, compliance,
+and customer relationships actually live.
+
+This is where customers connect, policy is enforced, workloads are shaped, and real businesses are built.
+
+
+ **Running a gateway is a strategic infrastructure decision**
+
+ Reasons include both technical and product needs.
+
+
+### Product Mental Model
+
+Gateways
+- own customer relationships
+- control ingress and demand
+- shape reliability and latency
+- enable compliance and enterprise sales
+- provide product differentiation
+
+In every mature infrastructure market (cloud, CDNs, payments, telecom), the
+control plane and edge capture durable value even when execution is commoditised
+(ie. by Orchestrators in the case of Livepeer).
+
+If orchestrators are "factories," gateways are the ports, customs offices, and logistics companies.
+
+
+
+# Why Run a Gateway?
+
+Below is some of the reasons you might decide to run a Livepeer Gateway - grouped into clear business and technical categories.
+
+ Change to Cards?
+
+
+
+ ## 1) Direct Usage & Platform Integration
+
+ Reasons related to *using a gateway as part of your own product or operations*.
+
+ * **Run your own workloads** – Process your own video or AI content end-to-end with full control over ingestion, routing, retries, and delivery.
+ * **Ensure SLAs on orchestrators** – Enforce latency, availability, retries, and failover through explicit orchestrator selection and routing logic.
+ * **Embed in a larger platform** – Use the gateway as internal infrastructure powering a broader media or AI product rather than exposing protocol primitives.
+
+
+
+
+ ## 2) Economics & Monetization
+
+ Reasons related to *where money is made or saved*.
+
+ * **Service-layer monetization** – Charge end users more than orchestrator cost for reliability, compliance, convenience, or performance guarantees.
+ * **Avoid third-party gateway fees** – Eliminate routing fees, pricing risk, and policy constraints imposed by another gateway operator.
+
+
+
+
+ ## 3) Demand Control & Traffic Ownership
+
+ Reasons related to *owning and shaping demand*.
+
+ * **Demand aggregation & traffic ownership** – Own ingress, customer relationships, usage data, and traffic predictability across apps or customers.
+ * **Workload normalization** – Smooth bursty demand into predictable, orchestrator-friendly workloads.
+
+
+
+
+ ## 4) Reliability, Performance & QoS
+
+ Reasons related to *making the system work in real production environments*.
+
+ * **QoS enforcement & workload shaping** – Control routing, retries, failover, and latency vs cost trade-offs beyond protocol defaults.
+ * **Geographic request steering** – Route users to regionally optimal orchestrators to reduce latency and improve reliability.
+
+
+
+
+ ## 5) Security & Compliance
+
+ Reasons related to *enterprise and production requirements*.
+
+ * **Enterprise policy enforcement** – IP allowlists, audit logs, authentication, rate limits, and deterministic behavior.
+ * **Cost-explosion & abuse protection** – Prevent buggy or malicious clients from generating runaway compute costs.
+
+
+
+
+ ## 6) Product Differentiation & UX
+
+ Reasons related to *building differentiated products on top of the protocol*.
+
+ * **Product differentiation above the protocol** – Custom APIs, SDKs, dashboards, billing abstractions, and AI workflow presets live at the gateway layer.
+ * **Stable API surface** – Shield customers from protocol or orchestrator churn with versioning and controlled change.
+
+
+
+
+ ## 7) Observability & Feedback Loops
+
+ Reasons related to *seeing and improving the system over time*.
+
+ * **Analytics & feedback loops** – Visibility into request patterns, failures, latency distributions, model performance, and customer behavior.
+
+
+
+
+ ## 8) Strategy, Optionality & Ecosystem Power
+
+ Reasons related to *long-term leverage and positioning*.
+
+ * **Strategic independence** – Avoid pricing, roadmap, availability, or censorship risk from other gateway operators.
+ * **Future optionality** – Early positioning if gateway incentives or economics evolve in the future.
+ * **Ecosystem influence** – Gateways shape standards, surface protocol gaps, and influence real-world usage patterns.
+
+
\ No newline at end of file
diff --git a/v2/pages/04_gateways/using-gateways/choosing-a-gateway.mdx b/v2/pages/04_gateways/using-gateways/choosing-a-gateway.mdx
new file mode 100644
index 00000000..0a0b8bc5
--- /dev/null
+++ b/v2/pages/04_gateways/using-gateways/choosing-a-gateway.mdx
@@ -0,0 +1,40 @@
+---
+title: 'Gateway Services'
+sidebarTitle: 'Find Gateway Services'
+description: 'Learn how to choose the right gateway for your needs.'
+---
+
+# Choosing a gateway
+
+
+ This page is a work in progress. Mostly gathering notes on this page atm.
+
+
+Rick -> feature coming soon
+https://explorer-arbitrum-one-git-feat-add-g-10dba1-livepeer-foundation.vercel.app/
+
+Explorer Showcases all gateways
+
+End-user friendly gateways: Based on user friendliness...
+
+- Daydream (1)
+- Livepeer Studio
+- Cloud SPE
+
+User friendly Gateways:
+
+Based on performance: expolorer (don't use total fees)
+
+The Livepeer Studio Gateway is a production-ready solution for interacting with the Livepeer AI network, offering advanced tools and resources for developers. Building on Livepeer AIShowcase. (docs)
+
+https://github.com/videoDAC/livepeer-gateway
+
+How to self-host a gateway: https://www.livepeer.cloud/self-hosted-livepeer-gateway/
+
+X: https://x.com/Livepeer/status/1805654248203731175?s=20
+
+-> AI Gateway Nodes
+
+The Livepeer AI Cloud Gateway is a hosted access point, making it easy for developers to leverage AI capabilities without running their own infratructure.
+
+Anyone can run a gateway to expand the network's reach.
diff --git a/v2/pages/04_gateways/using-gateways/gateway-providers.mdx b/v2/pages/04_gateways/using-gateways/gateway-providers.mdx
new file mode 100644
index 00000000..6becb86e
--- /dev/null
+++ b/v2/pages/04_gateways/using-gateways/gateway-providers.mdx
@@ -0,0 +1,69 @@
+---
+title: Gateway Providers
+description: Gateways to use in your applications
+sidebarTitle: Gateway Providers Portal
+---
+
+ WIP Section
+
+ This index should potentially be dynamic. This would require some scripting,
+ but could become an automated gateways HUB.
+
+
+import { GotoLink } from '/snippets/components/links.jsx'
+
+
+
+## Major Gateway Providers
+
+
+
+
+
+
+
+ Guide to Using the Daydream Gateway
+
+
+ Guide to Using the Livepeer Studio Gateway
+
+
+ Guide to Using the Cloud SPE Gateway
+
+
+ Other Gateway Services From The Livepeer Community
+
+
+
+## All Gateway Providers
+
+Embed a list from somewhere
diff --git a/v2/pages/04_gateways/using-gateways/gateway-providers/cloud-spe-gateway.mdx b/v2/pages/04_gateways/using-gateways/gateway-providers/cloud-spe-gateway.mdx
new file mode 100644
index 00000000..e69de29b
diff --git a/v2/pages/04_gateways/using-gateways/gateway-providers/daydream-gateway.mdx b/v2/pages/04_gateways/using-gateways/gateway-providers/daydream-gateway.mdx
new file mode 100644
index 00000000..e69de29b
diff --git a/v2/pages/04_gateways/using-gateways/gateway-providers/livepeer-studio-gateway.mdx b/v2/pages/04_gateways/using-gateways/gateway-providers/livepeer-studio-gateway.mdx
new file mode 100644
index 00000000..e69de29b
diff --git a/v2/pages/05_orchestrators/SUMMARY.mdx b/v2/pages/05_orchestrators/SUMMARY.mdx
new file mode 100644
index 00000000..e25eb89a
--- /dev/null
+++ b/v2/pages/05_orchestrators/SUMMARY.mdx
@@ -0,0 +1,40 @@
+# Table of contents
+
+## About Orchestrators (GPU Nodes)
+
+* [What is an Orchestrator](README.md)
+* [Orchestrator Functions](about-orchestrators-gpu-nodes/orchestrator-functions/README.md)
+ * [Transcoding](about-orchestrators-gpu-nodes/orchestrator-functions/transcoding.md)
+ * [AI Pipelines](about-orchestrators-gpu-nodes/orchestrator-functions/ai-pipelines.md)
+
+## Orchestrator Setup (Add a GPU to Livepeer)
+
+* [Hardware Requirements](orchestrator-setup-add-a-gpu-to-livepeer/hardware-requirements.md)
+* [Orchestrator Stats](orchestrator-setup-add-a-gpu-to-livepeer/orchestrator-stats.md)
+* [Setting up an Orchestrator](orchestrator-setup-add-a-gpu-to-livepeer/setting-up-an-orchestrator/README.md)
+ * [Quickstart: Add your GPU to Livepeer](orchestrator-setup-add-a-gpu-to-livepeer/setting-up-an-orchestrator/quickstart-add-your-gpu-to-livepeer.md)
+ * [Data Centres & Large Scale Hardware Providers](orchestrator-setup-add-a-gpu-to-livepeer/setting-up-an-orchestrator/data-centres-and-large-scale-hardware-providers.md)
+* [Join a Pool](orchestrator-setup-add-a-gpu-to-livepeer/join-a-pool.md)
+* [Data Centre Setup](orchestrator-setup-add-a-gpu-to-livepeer/data-centre-setup.md)
+* [Enterprise & Data Centres](orchestrator-setup-add-a-gpu-to-livepeer/enterprise-and-data-centres.md)
+
+## Orchestrator Tooling
+
+* [Orchestrator Tools](orchestrator-tooling/orchestrator-tools.md)
+* [Orchestrator Dashboards](orchestrator-tooling/orchestrator-dashboards.md)
+
+## Orchestrator Guides & References
+
+* [Orchestrator Guides & References](orchestrator-guides-and-references/orchestrator-guides-and-references.md)
+* [Orchestrator Resources](orchestrator-guides-and-references/orchestrator-resources.md)
+* [Orchestrator Community & Help](orchestrator-guides-and-references/orchestrator-community-and-help.md)
+
+## Technical References - SDKs. & APIs
+
+* [SDKs](technical-references-sdks.-and-apis/sdks.md)
+* [APIs](technical-references-sdks.-and-apis/apis.md)
+* [DeepWiki](technical-references-sdks.-and-apis/deepwiki.md)
+* [Livepeer Changelog](technical-references-sdks.-and-apis/livepeer-changelog/README.md)
+ * [Livepeer Changelog](technical-references-sdks.-and-apis/livepeer-changelog/livepeer-changelog.md)
+ * [Migration Guides](technical-references-sdks.-and-apis/livepeer-changelog/migration-guides.md)
+* [Migrations Guides](technical-references-sdks.-and-apis/migrations-guides.md)
diff --git a/v2/pages/05_orchestrators/about-orchestrators/orchestrator-functions/ai-pipelines.mdx b/v2/pages/05_orchestrators/about-orchestrators/orchestrator-functions/ai-pipelines.mdx
new file mode 100644
index 00000000..a1996496
--- /dev/null
+++ b/v2/pages/05_orchestrators/about-orchestrators/orchestrator-functions/ai-pipelines.mdx
@@ -0,0 +1,4 @@
+
+
+# AI Pipelines
+
diff --git a/v2/pages/05_orchestrators/about-orchestrators/orchestrator-functions/transcoding.mdx b/v2/pages/05_orchestrators/about-orchestrators/orchestrator-functions/transcoding.mdx
new file mode 100644
index 00000000..4dde0f81
--- /dev/null
+++ b/v2/pages/05_orchestrators/about-orchestrators/orchestrator-functions/transcoding.mdx
@@ -0,0 +1,4 @@
+
+
+# Transcoding
+
diff --git a/v2/pages/05_orchestrators/about-orchestrators/overview.mdx b/v2/pages/05_orchestrators/about-orchestrators/overview.mdx
new file mode 100644
index 00000000..f8b0615d
--- /dev/null
+++ b/v2/pages/05_orchestrators/about-orchestrators/overview.mdx
@@ -0,0 +1,47 @@
+---
+title: 'Orchestrator Explainer'
+sidebarTitle: 'Explainer'
+---
+
+
+### What is an Orchestrator?
+An orchestrator is a supply-side operator that contributes GPU resources to the network.
+They receive jobs, perform transcoding or AI inference, and get paid via LPT rewards + ETH fees.
+
+
+### What does an Orchestrator do?
+An orchestrator runs a node that performs transcoding or AI inference.
+They receive jobs from the network, execute them on their GPU resources, and return the results.
+
+### What are the different types of Orchestrators?
+There are two types of orchestrators on the Livepeer Network: GPU nodes and AI nodes.
+GPU nodes perform transcoding, while AI nodes perform AI inference.
+
+### Who Runs Orchestrators?
+Anyone with a GPU can run an orchestrator on the Livepeer Network, whether you want to add your GPU to the network for passive income in idle times, or you want to run a full-fledged business.
+
+If you're a hobbyist, the best place to start is by contributing your GPU to a pool.
+If you're a data center or want to have full control over your node, you can run your own GPU node.
+
+### Choose your own adventure!
+
+
+
+ See how to add your GPU to an Orchestrator pool.
+
+
+ See how to run your own GPU node on the Livepeer Network.
+
+
+
+
diff --git a/v2/pages/05_orchestrators/faq.mdx b/v2/pages/05_orchestrators/faq.mdx
new file mode 100644
index 00000000..8ec3c4ce
--- /dev/null
+++ b/v2/pages/05_orchestrators/faq.mdx
@@ -0,0 +1,4 @@
+
+
+# FAQ
+
diff --git a/v2/pages/05_orchestrators/orchestrator-guides-and-references/orchestrator-community-and-help.mdx b/v2/pages/05_orchestrators/orchestrator-guides-and-references/orchestrator-community-and-help.mdx
new file mode 100644
index 00000000..8da281a7
--- /dev/null
+++ b/v2/pages/05_orchestrators/orchestrator-guides-and-references/orchestrator-community-and-help.mdx
@@ -0,0 +1,2 @@
+# Orchestrator Community & Help
+
diff --git a/v2/pages/05_orchestrators/orchestrator-guides-and-references/orchestrator-guides-and-references.mdx b/v2/pages/05_orchestrators/orchestrator-guides-and-references/orchestrator-guides-and-references.mdx
new file mode 100644
index 00000000..17d2daf4
--- /dev/null
+++ b/v2/pages/05_orchestrators/orchestrator-guides-and-references/orchestrator-guides-and-references.mdx
@@ -0,0 +1,4 @@
+
+
+# Orchestrator Guides & References
+
diff --git a/v2/pages/05_orchestrators/orchestrator-guides-and-references/orchestrator-resources.mdx b/v2/pages/05_orchestrators/orchestrator-guides-and-references/orchestrator-resources.mdx
new file mode 100644
index 00000000..1756e123
--- /dev/null
+++ b/v2/pages/05_orchestrators/orchestrator-guides-and-references/orchestrator-resources.mdx
@@ -0,0 +1,4 @@
+
+
+# Orchestrator Resources
+
diff --git a/v2/pages/05_orchestrators/orchestrator-tooling/orchestrator-dashboards.mdx b/v2/pages/05_orchestrators/orchestrator-tooling/orchestrator-dashboards.mdx
new file mode 100644
index 00000000..6ec978d6
--- /dev/null
+++ b/v2/pages/05_orchestrators/orchestrator-tooling/orchestrator-dashboards.mdx
@@ -0,0 +1,2 @@
+# Orchestrator Dashboards
+
diff --git a/v2/pages/05_orchestrators/orchestrator-tooling/orchestrator-tools.mdx b/v2/pages/05_orchestrators/orchestrator-tooling/orchestrator-tools.mdx
new file mode 100644
index 00000000..37f2ee78
--- /dev/null
+++ b/v2/pages/05_orchestrators/orchestrator-tooling/orchestrator-tools.mdx
@@ -0,0 +1,4 @@
+
+
+# Orchestrator Tools
+
diff --git a/v2/pages/05_orchestrators/orchestrators-home.mdx b/v2/pages/05_orchestrators/orchestrators-home.mdx
new file mode 100644
index 00000000..16e2b8c2
--- /dev/null
+++ b/v2/pages/05_orchestrators/orchestrators-home.mdx
@@ -0,0 +1,64 @@
+---
+title: 'Orchestrator Portal'
+sidebarTitle: 'Orchestrator Home'
+tag: Start Here
+description: 'Welcome To The Orchestrator Portal: Explore, Navigate, Build'
+---
+
+## Orchestrator Portal: Map
+
+**Definition**
+Orchestrators are...
+
+**Quick Intro**
+Get Situated
+
+## Orchestrator Portal: Choose Your Mission
+Your Journey Starts Here / More "normal" Wording for AI/SEO
+
+
+
+..
+
+
+..
+
+
+ Orchestrator Level up: Deploy your own Gateway on the Livepeer Protocol.
+
+
+.
+
+
+ .
+
+
+
+---
+
+?Gateway Portal FAQs
+
+
+## Gateway Portal Jump Pad
+Bit irrelevant after the missions
+Jump to
+- [What's a Gateway?](#whats-a-gateway)
+- [Gateway Services & Providers](#gateway-services--providers)
+- [Run a Gateway](#run-a-gateway)
+- [Gateway Tools & Dashboards](#gateway-tools--dashboards)
+- [Gateway Guides & Resources](#gateway-guides--resources)
\ No newline at end of file
diff --git a/v2/pages/05_orchestrators/setting-up-an-orchestrator/README.mdx b/v2/pages/05_orchestrators/setting-up-an-orchestrator/README.mdx
new file mode 100644
index 00000000..42c5bff4
--- /dev/null
+++ b/v2/pages/05_orchestrators/setting-up-an-orchestrator/README.mdx
@@ -0,0 +1,4 @@
+
+
+# Setting up an Orchestrator
+
diff --git a/v2/pages/05_orchestrators/setting-up-an-orchestrator/data-centre-setup.mdx b/v2/pages/05_orchestrators/setting-up-an-orchestrator/data-centre-setup.mdx
new file mode 100644
index 00000000..f397af67
--- /dev/null
+++ b/v2/pages/05_orchestrators/setting-up-an-orchestrator/data-centre-setup.mdx
@@ -0,0 +1,2 @@
+# Data Centre Setup
+
diff --git a/v2/pages/05_orchestrators/setting-up-an-orchestrator/data-centres-and-large-scale-hardware-providers.mdx b/v2/pages/05_orchestrators/setting-up-an-orchestrator/data-centres-and-large-scale-hardware-providers.mdx
new file mode 100644
index 00000000..99fbf85a
--- /dev/null
+++ b/v2/pages/05_orchestrators/setting-up-an-orchestrator/data-centres-and-large-scale-hardware-providers.mdx
@@ -0,0 +1,4 @@
+
+
+# Data Centres & Large Scale Hardware Providers
+
diff --git a/v2/pages/05_orchestrators/setting-up-an-orchestrator/enterprise-and-data-centres.mdx b/v2/pages/05_orchestrators/setting-up-an-orchestrator/enterprise-and-data-centres.mdx
new file mode 100644
index 00000000..1bd740f1
--- /dev/null
+++ b/v2/pages/05_orchestrators/setting-up-an-orchestrator/enterprise-and-data-centres.mdx
@@ -0,0 +1,2 @@
+# Enterprise & Data Centres
+
diff --git a/v2/pages/05_orchestrators/setting-up-an-orchestrator/hardware-requirements.mdx b/v2/pages/05_orchestrators/setting-up-an-orchestrator/hardware-requirements.mdx
new file mode 100644
index 00000000..596ffbe9
--- /dev/null
+++ b/v2/pages/05_orchestrators/setting-up-an-orchestrator/hardware-requirements.mdx
@@ -0,0 +1,4 @@
+
+
+# Hardware Requirements
+
diff --git a/v2/pages/05_orchestrators/setting-up-an-orchestrator/join-a-pool.mdx b/v2/pages/05_orchestrators/setting-up-an-orchestrator/join-a-pool.mdx
new file mode 100644
index 00000000..354f3e94
--- /dev/null
+++ b/v2/pages/05_orchestrators/setting-up-an-orchestrator/join-a-pool.mdx
@@ -0,0 +1,2 @@
+# Join a Pool
+
diff --git a/v2/pages/05_orchestrators/setting-up-an-orchestrator/orchestrator-stats.mdx b/v2/pages/05_orchestrators/setting-up-an-orchestrator/orchestrator-stats.mdx
new file mode 100644
index 00000000..f626dd39
--- /dev/null
+++ b/v2/pages/05_orchestrators/setting-up-an-orchestrator/orchestrator-stats.mdx
@@ -0,0 +1,4 @@
+
+
+# Orchestrator Stats
+
diff --git a/v2/pages/05_orchestrators/setting-up-an-orchestrator/publish-offerings.mdx b/v2/pages/05_orchestrators/setting-up-an-orchestrator/publish-offerings.mdx
new file mode 100644
index 00000000..28e46e59
--- /dev/null
+++ b/v2/pages/05_orchestrators/setting-up-an-orchestrator/publish-offerings.mdx
@@ -0,0 +1,54 @@
+---
+title: Publish Offerings
+description: 'How to Publish Offerings to the Marketplace'
+sidebarTitle: 'Publish Offerings'
+---
+
+## Publishing as an Orchestrator (MOVE ME)
+
+Orchestrators publish compute offerings showing:
+
+### **GPU Inventory**
+
+- 4090
+- A40
+- L40S
+- V100
+
+### **Model Compatibility**
+
+- TensorRT support
+- Torch Compile accelerations
+
+### **Benchmarks**
+
+- Frames per second
+- Tokens per second
+- Latency per model
+
+
+## Marketplace Submission Workflow
+
+```mermaid
+sequenceDiagram
+ participant Operator
+ participant Marketplace
+ participant Applications
+
+ Operator->>Marketplace: Submit offering (models, pricing, regions)
+ Marketplace->>Applications: Expose offering via API
+ Applications->>Marketplace: Query offerings (filter by price, capability)
+ Marketplace->>Applications: Return best matches
+```
+
+## Updating Offerings
+
+Operators can dynamically update:
+
+- Pricing
+- Model support
+- Pipeline versions
+- GPU availability
+ Performance metrics
+
+Updates propagate automatically to Marketplace consumers.
\ No newline at end of file
diff --git a/v2/pages/05_orchestrators/setting-up-an-orchestrator/quickstart-add-your-gpu-to-livepeer.mdx b/v2/pages/05_orchestrators/setting-up-an-orchestrator/quickstart-add-your-gpu-to-livepeer.mdx
new file mode 100644
index 00000000..8945164d
--- /dev/null
+++ b/v2/pages/05_orchestrators/setting-up-an-orchestrator/quickstart-add-your-gpu-to-livepeer.mdx
@@ -0,0 +1,4 @@
+
+
+# Quickstart: Add your GPU to Livepeer
+
diff --git a/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/apis.mdx b/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/apis.mdx
new file mode 100644
index 00000000..add5dda5
--- /dev/null
+++ b/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/apis.mdx
@@ -0,0 +1,4 @@
+
+
+# APIs
+
diff --git a/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/deepwiki.mdx b/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/deepwiki.mdx
new file mode 100644
index 00000000..ae505ac9
--- /dev/null
+++ b/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/deepwiki.mdx
@@ -0,0 +1,4 @@
+
+
+# DeepWiki
+
diff --git a/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/livepeer-changelog/README.mdx b/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/livepeer-changelog/README.mdx
new file mode 100644
index 00000000..64da6b02
--- /dev/null
+++ b/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/livepeer-changelog/README.mdx
@@ -0,0 +1,4 @@
+
+
+# Livepeer Changelog
+
diff --git a/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/livepeer-changelog/livepeer-changelog.mdx b/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/livepeer-changelog/livepeer-changelog.mdx
new file mode 100644
index 00000000..64da6b02
--- /dev/null
+++ b/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/livepeer-changelog/livepeer-changelog.mdx
@@ -0,0 +1,4 @@
+
+
+# Livepeer Changelog
+
diff --git a/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/livepeer-changelog/migration-guides.mdx b/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/livepeer-changelog/migration-guides.mdx
new file mode 100644
index 00000000..e6d01acb
--- /dev/null
+++ b/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/livepeer-changelog/migration-guides.mdx
@@ -0,0 +1,4 @@
+
+
+# Migration Guides
+
diff --git a/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/migrations-guides.mdx b/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/migrations-guides.mdx
new file mode 100644
index 00000000..011f2c36
--- /dev/null
+++ b/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/migrations-guides.mdx
@@ -0,0 +1,4 @@
+
+
+# Migrations Guides
+
diff --git a/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/sdks.mdx b/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/sdks.mdx
new file mode 100644
index 00000000..0f3aff91
--- /dev/null
+++ b/v2/pages/05_orchestrators/technical-references-sdks.-and-apis/sdks.mdx
@@ -0,0 +1,4 @@
+
+
+# SDKs
+
diff --git a/v2/pages/06_delegators/README.mdx b/v2/pages/06_delegators/README.mdx
new file mode 100644
index 00000000..69c62a11
--- /dev/null
+++ b/v2/pages/06_delegators/README.mdx
@@ -0,0 +1,5 @@
+
+
+# Why have a token?
+
+Advantages of tokens for decentralised infrastructure
diff --git a/v2/pages/06_delegators/SUMMARY.mdx b/v2/pages/06_delegators/SUMMARY.mdx
new file mode 100644
index 00000000..b93343df
--- /dev/null
+++ b/v2/pages/06_delegators/SUMMARY.mdx
@@ -0,0 +1,29 @@
+# Table of contents
+
+## About LPT (Livepeer Token)
+
+* [Why have a token?](README.md)
+* [Livepeer Token Economics](about-lpt-livepeer-token/livepeer-token-economics.md)
+* [How to get LPT](about-lpt-livepeer-token/how-to-get-lpt.md)
+* [Delegators](about-lpt-livepeer-token/delegators.md)
+
+## Delegating LPT
+
+* [About Delegators](delegating-lpt/about-delegators.md)
+* [How to delegate LPT](delegating-lpt/how-to-delegate-lpt.md)
+* [Delegation Economics](delegating-lpt/delegation-economics.md)
+
+## Livepeer Governance
+
+* [Page 4](livepeer-governance/page-4.md)
+* [Page 1](livepeer-governance/page-1.md)
+
+## Livepeer Treasury
+
+* [Page 3](livepeer-treasury/page-3.md)
+* [Page](livepeer-treasury/page.md)
+
+## Token Resources
+
+* [LPT Exchanges](token-resources/lpt-exchanges.md)
+* [??](token-resources/undefined.md)
diff --git a/v2/pages/06_delegators/about-lpt-livepeer-token/delegators.mdx b/v2/pages/06_delegators/about-lpt-livepeer-token/delegators.mdx
new file mode 100644
index 00000000..764d3050
--- /dev/null
+++ b/v2/pages/06_delegators/about-lpt-livepeer-token/delegators.mdx
@@ -0,0 +1,2 @@
+# Delegators
+
diff --git a/v2/pages/06_delegators/about-lpt-livepeer-token/how-to-get-lpt.mdx b/v2/pages/06_delegators/about-lpt-livepeer-token/how-to-get-lpt.mdx
new file mode 100644
index 00000000..66b99c3b
--- /dev/null
+++ b/v2/pages/06_delegators/about-lpt-livepeer-token/how-to-get-lpt.mdx
@@ -0,0 +1,2 @@
+# How to get LPT
+
diff --git a/v2/pages/06_delegators/about-lpt-livepeer-token/livepeer-token-economics.mdx b/v2/pages/06_delegators/about-lpt-livepeer-token/livepeer-token-economics.mdx
new file mode 100644
index 00000000..8abc258a
--- /dev/null
+++ b/v2/pages/06_delegators/about-lpt-livepeer-token/livepeer-token-economics.mdx
@@ -0,0 +1,2 @@
+# Livepeer Token Economics
+
diff --git a/v2/pages/06_delegators/about-lpt-livepeer-token/overview.mdx b/v2/pages/06_delegators/about-lpt-livepeer-token/overview.mdx
new file mode 100644
index 00000000..0cf1aa31
--- /dev/null
+++ b/v2/pages/06_delegators/about-lpt-livepeer-token/overview.mdx
@@ -0,0 +1,4 @@
+---
+title: 'LPT & Delegation Overview'
+sidebarTitle: 'Explainer'
+---
diff --git a/v2/pages/06_delegators/delegating-lpt/about-delegators.mdx b/v2/pages/06_delegators/delegating-lpt/about-delegators.mdx
new file mode 100644
index 00000000..b47e1cf0
--- /dev/null
+++ b/v2/pages/06_delegators/delegating-lpt/about-delegators.mdx
@@ -0,0 +1,2 @@
+# About Delegators
+
diff --git a/v2/pages/06_delegators/delegating-lpt/delegation-economics.mdx b/v2/pages/06_delegators/delegating-lpt/delegation-economics.mdx
new file mode 100644
index 00000000..7f41882a
--- /dev/null
+++ b/v2/pages/06_delegators/delegating-lpt/delegation-economics.mdx
@@ -0,0 +1,2 @@
+# Delegation Economics
+
diff --git a/v2/pages/06_delegators/delegating-lpt/how-to-delegate-lpt.mdx b/v2/pages/06_delegators/delegating-lpt/how-to-delegate-lpt.mdx
new file mode 100644
index 00000000..de8f6a07
--- /dev/null
+++ b/v2/pages/06_delegators/delegating-lpt/how-to-delegate-lpt.mdx
@@ -0,0 +1,2 @@
+# How to delegate LPT
+
diff --git a/v2/pages/06_delegators/livepeer-governance/page-1.mdx b/v2/pages/06_delegators/livepeer-governance/page-1.mdx
new file mode 100644
index 00000000..6f8b4979
--- /dev/null
+++ b/v2/pages/06_delegators/livepeer-governance/page-1.mdx
@@ -0,0 +1,2 @@
+# Page 1
+
diff --git a/v2/pages/06_delegators/livepeer-governance/page-4.mdx b/v2/pages/06_delegators/livepeer-governance/page-4.mdx
new file mode 100644
index 00000000..e6b1a2c6
--- /dev/null
+++ b/v2/pages/06_delegators/livepeer-governance/page-4.mdx
@@ -0,0 +1,2 @@
+# Page 4
+
diff --git a/v2/pages/06_delegators/livepeer-treasury/page-3.mdx b/v2/pages/06_delegators/livepeer-treasury/page-3.mdx
new file mode 100644
index 00000000..40b4ed41
--- /dev/null
+++ b/v2/pages/06_delegators/livepeer-treasury/page-3.mdx
@@ -0,0 +1,2 @@
+# Page 3
+
diff --git a/v2/pages/06_delegators/livepeer-treasury/page.mdx b/v2/pages/06_delegators/livepeer-treasury/page.mdx
new file mode 100644
index 00000000..5c4b4d58
--- /dev/null
+++ b/v2/pages/06_delegators/livepeer-treasury/page.mdx
@@ -0,0 +1,2 @@
+# Page
+
diff --git a/v2/pages/06_delegators/token-home.mdx b/v2/pages/06_delegators/token-home.mdx
new file mode 100644
index 00000000..63c7e6b5
--- /dev/null
+++ b/v2/pages/06_delegators/token-home.mdx
@@ -0,0 +1,64 @@
+---
+title: 'Token Portal'
+sidebarTitle: 'Token Home'
+tag: Start Here
+description: 'Welcome To The Token Portal: Explore, Navigate, Build'
+---
+
+## Token Portal: Map
+
+**Definition**
+Tokens are...
+
+**Quick Intro**
+Get Situated
+
+## Token Portal: Choose Your Mission
+Your Journey Starts Here / More "normal" Wording for AI/SEO
+
+
+
+..
+
+
+..
+
+
+ Token Level up: Deploy your own Gateway on the Livepeer Protocol.
+
+
+.
+
+
+ .
+
+
+
+---
+
+?Gateway Portal FAQs
+
+
+## Gateway Portal Jump Pad
+Bit irrelevant after the missions
+Jump to
+- [What's a Gateway?](#whats-a-gateway)
+- [Gateway Services & Providers](#gateway-services--providers)
+- [Run a Gateway](#run-a-gateway)
+- [Gateway Tools & Dashboards](#gateway-tools--dashboards)
+- [Gateway Guides & Resources](#gateway-guides--resources)
\ No newline at end of file
diff --git a/v2/pages/06_delegators/token-resources/lpt-eth-usage.mdx b/v2/pages/06_delegators/token-resources/lpt-eth-usage.mdx
new file mode 100644
index 00000000..11b51977
--- /dev/null
+++ b/v2/pages/06_delegators/token-resources/lpt-eth-usage.mdx
@@ -0,0 +1,32 @@
+---
+title: LPT & ETH Token Functions
+sidebarTitle: 'Protocol Token Flows'
+description: What the LPT & ETH Tokens are used for in the Livepeer Protocol
+---
+
+ This is wild to me that Gateways do not use LPT to pay orchestrators. Need to dig into the why more
+
+### Payment Layers
+The Livpeer Protocol uses two distinct currencies for different purposes:
+
+| Currency | Purpose | Used By |
+| --- | --- | --- |
+| ETH/Wei | Service payments (transcoding, AI) | Gateways → Orchestrators |
+| LPT | Staking, governance, rewards | Orchestrators, Delegators |
+
+The separation is intentional: ETH handles actual service payments while LPT handles protocol governance and staking.
+This design keeps service costs predictable in a stable currency while allowing LPT to serve its governance function
+
+**Price Configuration**
+Prices can be specified in wei or converted from fiat currencies [starter.go:891-908](https://github.com/livepeer/go-livepeer/blob/5691cb48/cmd/livepeer/starter.go#L891-L908)
+
+```go
+pricePerUnit, currency, err := parsePricePerUnit(*cfg.PricePerUnit)
+// Supports: "1000", "0.50USD", "1.5EUR" etc.
+// Converts to wei for actual payments
+```
+
+
+## ETH Payments
+Gateways pay for transcoding and AI processing services using ETH (Ethereum), not Livepeer tokens (LPT).
+The payment system is built on Ethereum's currency.
diff --git a/v2/pages/06_delegators/token-resources/lpt-exchanges.mdx b/v2/pages/06_delegators/token-resources/lpt-exchanges.mdx
new file mode 100644
index 00000000..949c5e2b
--- /dev/null
+++ b/v2/pages/06_delegators/token-resources/lpt-exchanges.mdx
@@ -0,0 +1,520 @@
+---
+title: 'Exchanges with LPT Listed'
+sidebarTitle: 'LPT Exchanges'
+description: 'A list of exchanges where the Livepeer Token (LPT) is listed. Note: this information is fetched from Coingecko weekly'
+---
+
+
+ This (will be) a dynamic automation to fetch all exchange that list LPT.
+ It is generated via a n8n pipeline with data from Coingecko's API: GET `coingecko.com/api/v3/coins/livepeer`
+ It is currently a static pull in from a script in mintlify
+
+
+---
+
+## Centralized Exchanges (CEX)
+
+
+ **Last Updated:** 2025-12-15 | Data sourced from [CoinGecko](https://www.coingecko.com/en/coins/livepeer)
+
+
+
+ **Trust Score Legend:** 🟢 High | 🟡 Medium | 🔴 Low | ⚪ Unknown
+
+
+
+
+
+ Trading volumes are approximate 24-hour figures. Always verify current data on the exchange.
+
+
+## Decentralized Exchanges (DEX)
+
+
+
+ Trade LPT on Ethereum mainnet
+
+
+ Legacy Uniswap pool on Ethereum
+
+
+
+## Contract Addresses
+
+
+
+
+
+
Network
+
Contract Address
+
+
+
+
+
Ethereum
+
0x58b6a8a3302369daec383334672404ee733ab239
+
+
+
Arbitrum One
+
0x289ba1701c2f088cf0faf8b3705246331cb8a839
+
+
+
+
diff --git a/v2/pages/07_resources/changelog/changelog.mdx b/v2/pages/07_resources/changelog/changelog.mdx
new file mode 100644
index 00000000..0fb38538
--- /dev/null
+++ b/v2/pages/07_resources/changelog/changelog.mdx
@@ -0,0 +1,1305 @@
+---
+sidebarTitle: 'Changelog'
+---
+
+## Mintlify Changelog Example
+
+
+ {' '}
+ https://www.featurebase.app/: will be roadmap feature request (Ask
+ Mehrad){' '}
+
+
+
+ This is an example of a changelog only. This does not relate to Livepeer
+
+
+ Planned Changelog: Straight from github repo's with a n8n pipeline
+
+> New releases and improvements
+
+
+ ## .mintignore support
+
+- Added `.mintignore` file support to exclude specific files and directories from being processed and published to your documentation site.
+- Uses the same pattern syntax as `.gitignore` for familiar configuration.
+- Excluded files don't appear in published docs, aren't indexed for search, and aren't accessible to visitors.
+
+Learn more in the [.mintignore documentation](/organize/mintignore).
+
+
+
+
+ ## Vale version upgrade
+
+- Upgraded backend dependencies to use Vale version 3.11.2-r5, bringing native MDX support to the Vale CI check feature.
+
+
+
+
+ ## API playground improvements
+
+- Fixed issue where response section would disappear when switching between endpoints with different response codes. The playground now properly resets to the first available response code when navigating to a new endpoint.
+- Fixed double "Authorization" header display in HTTP Basic authentication schemes. The authentication section now shows a cleaner interface with proper field labels and descriptions.
+- Improved handling of `oneOf` schemas in nested objects and arrays. Complex API schemas with multiple type options now render correctly as dropdowns instead of tabs in appropriate contexts.
+- Fixed missing path parameters that were defined at the endpoint level in OpenAPI specs. Parameters specified above individual operations are now properly included in both the main page and playground.
+- Enhanced response example generation to include all required properties, even when examples only specify some fields. This ensures response examples are complete and accurate.
+- Fixed missing prefill examples in object arrays. Array items with example data now properly populate in the playground with correct indexing.
+- Improved description padding and spacing throughout the API playground for better readability and visual consistency.
+
+## Localization improvements
+
+- Enhanced translations in contextual menu options and assistant status messages for all supported languages.
+
+## CLI improvements
+
+- Added error message for users running `mint dev` on Node.js versions below 20.17. Users are guided to upgrade to an LTS version.
+
+
+
+
+ ## New features
+
+- **Badge component**: New Badge component for displaying status indicators, labels, and tags
+- **Custom Shiki languages**: Add support for custom programming languages in code blocks through `docs.json` configuration, enabling syntax highlighting for domain-specific languages
+- **Clarity analytics integration**: Microsoft Clarity is now available as an analytics integration for session recording and heatmap tracking
+
+## API playground improvements
+
+- Authentication keys now persist in the API playground across page navigation and browser sessions, eliminating the need to re-enter credentials when testing multiple endpoints
+- Authentication keys are automatically prefilled from your configuration, making it faster to start testing authenticated endpoints
+- Fixed authentication header names for Bearer auth and OAuth to use correct HTTP standards
+- Security inputs defined at the operation level in OpenAPI specs now properly override top-level security definitions
+- Fixed issue where header inputs marked as security parameters were incorrectly included in generated code examples
+- Improved handling of `deepObject` style parameters in API field displays
+- Better error messages when invalid URLs are provided in API configurations
+- Improved UI for API playground with better spacing, layout, and loading
+
+## Navigation and UI enhancements
+
+- Tab hover indicators now have improved styling for better visual feedback
+- Long words now wrap properly to prevent horizontal scrolling
+- Step component now handles cases where no step title is provided
+- Logo section spacing improved with better padding
+- Fixed heading IDs to properly handle question marks and special characters for anchor links
+- Icon component now accepts `className` prop for custom styling
+- Fixed theme toggle colors for better visibility in both light and dark modes
+
+## Web editor improvements
+
+- Branch switching is now integrated directly into the editor UI for easier navigation between branches
+- Fixed file creation and renaming to properly match original file locations in MDX frontmatter
+- Fixed handling of moving files to previously deleted paths
+- Folder state now persists in the editor across sessions
+
+## Component and styling enhancements
+
+- Images can now be zoomed with improved overlay styling for both light and dark modes
+- Fixed keyboard shortcut styles inside callouts for dark mode
+- Improved OG image generation with Google Fonts support and better truncation logic
+- Improved UI for tables with better alignment, spacing, and readability
+- Fixed scroll behavior for tables inside tabs and steps inside tabs
+- Improved sidebar styling for Palm theme
+
+## Performance and infrastructure
+
+- Shiki themes are now lazy loaded for improved initial page load performance
+- Reduced navigation lag by optimizing prefetching behavior
+
+## Bug fixes and reliability
+
+- Properly clear added values on object and array inputs in API playground
+- Fixed table of contents rendering issues
+- Fixed favicon isolation to prevent conflicts between different documentation sites
+- Fixed sidebar display on non-API pages
+- Fixed outline blinking on image zoom modal open/close
+- External links now properly open in new tabs
+- Fixed dashboard design inconsistencies and improved spacing
+
+
+
+
+ ## Assistant improvements
+
+- **Starter questions for assistant are here! You can add your own within the dashboard at [Assistant --> Settings](https://dashboard.mintlify.com/mintlify/mintlify/products/assistant/settings)**
+- Assistant insights quality has been improved with default spam protection for abusive keywords and JSON queries.
+
+## API playground improvements
+
+- The API playground now automatically fills in default values for parameters, which saves time when testing endpoints.
+- Issues with `allOf`, `oneOf`, and nested object schemas that previously caused rendering problems or incorrect field displays have been fixed, and complex API schemas now render correctly with all fields visible and properly structured.
+- Enum and nullable field types now display accurate labels in the playground, which makes it clearer what values are accepted and whether fields are optional.
+- When working with nested objects in API requests, the playground now shows proper descriptive labels for each field instead of generic placeholders, which makes it easier to understand what data to provide.
+- Enum const tables and API field displays now render with improved formatting and alignment, which makes it easier to scan available options and understand field requirements.
+- API playground modals now display rich MDX-formatted descriptions at the top, which gives better context for endpoints with formatted text, links, and code examples.
+
+## Analytics changes
+
+- Deferred analytics loading: PostHog and LogRocket now load after documentation content, which improves initial page load times and Core Web Vitals scores without affecting analytics data.
+- Conditional session recording: PostHog session recording can now be enabled conditionally based on user properties or page context for more control over when recordings happen.
+
+## Visual improvements
+
+- Tables now have better alignment, consistent spacing, and enhanced readability. Headers align properly with their content columns.
+
+## Bug fixes
+
+- Fixed link overflow issues that caused horizontal scrolling on mobile devices. Links now wrap properly within their containers.
+- Improved LaTeX/math block styling for better readability and consistent formatting.
+- Added `playsInline` and autoplay props to video embeds so they work correctly on iOS devices.
+- Updated Claude icon with proper border-radius for visual consistency.
+- Fixed `/llms.txt` routing so LLM agents can properly access documentation.
+- Prevented infinite schema expansion in complex OpenAPI specs that could cause browser crashes.
+- Removed x-overflow in Palm theme that was cutting off text in the API playground.
+- Increased content font-size to improve compatibility with browser reader modes.
+- Fixed Google login button styling for better visual consistency.
+
+
+
+
+ ## Insights improvements
+
+- Improved insights page with fixed date selectors for "today" and "yesterday"
+- Enhanced feedback table with improved search functionality
+- Added loading state for categories table
+
+## Assistant improvements
+
+- Added assistant placement configuration in dashboard
+- Improved assistant responses with fixes to context fetching and tool messages
+
+## API playground and OpenAPI enhancements
+
+- Refactored API playground endpoint fields to use new schema graph for better performance
+- Improved API examples display in playground modal even when assistant sidebar is open
+- Fixed props adjacent to `$refs` and `x-` props getting lost in OpenAPI parsing
+- Fixed API playground modal header styling
+
+## Web editor and deployment enhancements
+
+- Restored manual create preview button for easier preview deployment creation
+- Added fetcher in dashboard for branch protections data
+- Added fetcher in dashboard for PR status tracking
+- Improved editor state management, enabling state to persist across browser sessions
+- Fixed disabled state for editor publish button
+- Removed code block background in editor for cleaner appearance
+
+## Performance and infrastructure
+
+- Implemented full Git sync in the web editor for better repository synchronization
+- Cached MCP responses for improved performance
+- Improved sitemap to normalize `/index` paths
+
+## Bug fixes and reliability
+
+- Fixed authentication prefill values not getting properly prefilled in API playground
+- Fixed custom meta tags from `seo.metatags` to survive client-side hydration
+- Fixed page header text overflow with `break-all` styling
+- Removed full width constraint for page size options
+- Fixed button size for accept organization invitations
+- Fixed keyboard shortcut display showing "Ctrl+I" without plus sign on non-macOS computers
+
+
+
+
+ ## Assistant and AI improvements
+
+- Upgraded assistant prompt for better accuracy and context-aware responses
+- Added confidence scoring to improve decision-making in assistant responses
+- Enhanced assistant search with parallel documentation queries for faster results
+- Fixed assistant disappearing bug and improved visibility on small pages
+
+## Navigation and UI enhancements
+
+- Added stable scrollbar gutter to navigation components for consistent layout
+- Made "On this page" section clickable to quickly scroll to the top of a page
+- Fixed assistant bar positioning across all themes
+- Improved assistant bar to prevent overlapping content
+- Fixed Almond theme wide page max-width
+- Enhanced dropdown arrow icon sizing for consistent navigation group appearance
+
+## API playground and OpenAPI improvements
+
+- Added feature flag support for new API reference page design
+- Improved OpenAPI schema graph utilities to handle compositions properly
+- Added endpoint type to operation data for better API documentation
+- Fixed API playground description rendering when enum and table are in Markdown
+- Moved rendering of descriptions in API playground for better layout
+
+## Bug fixes and reliability
+
+- Fixed locale switching to stay on the same page instead of redirecting to the home page
+- Fixed broken links CLI to exit with code 1 for CI/CD integration
+- Fixed local font paths to properly prepend forward slash
+- Fixed redirect handling to ignore leading slashes in `docs.json`
+- Fixed canonical URL stripping of `/index` for better SEO
+- Fixed ordered list positioning inside accordions
+- Fixed `` tag styling to behave like `
` tags
+- Fixed display block for first `
` tag in lists
+- Fixed OG image display to show division name for index pages
+- Fixed icon paths to include `BASE_PATH` for relative paths
+- Fixed assistant background blur removal for better performance
+
+
+
+
+ ## Assistant and Agent AI features
+
+- Added list_pull_requests and list_commits tools for agent such that it can document a date range of PRs or multiple PRs at once
+- Upgraded agent and assistant to Claude Sonnet 4.5
+- Improved assistant search to query docs in parallel for faster assistant responses
+- Fixed conversation length counting to exclude tool calls
+
+## Insights improvements
+
+- Retitled analytics to insights
+- Removed click-to-load requirement for insights so you can see all your data immediately
+- Improved insights data accuracy with server-side timestamps
+
+## Web editor and dashboard improvements
+
+- Removed background from code blocks in editor for cleaner appearance
+- Fixed branch creation workflow to correctly navigate to newly created branches
+- Added deployment history pagination
+- Added cursor pagination to preview deployments table
+- Fixed preview deployments to only return preview environment deployments
+- Improved dashboard UI/UX with better spacing, input handling, and layout fixes
+- Added better handling for links in dashboard assistant chat
+- Fixed outline issues for chat assistant in Firefox
+
+## API playground enhancements
+
+- Improved rendering of API playground modals
+- Fixed API playground expandables not working with anchor links
+- Added support for merging example and user-inputted body in API playground
+- Fixed how video responses display in API playground
+
+## Bug fixes and reliability
+
+- Fixed duplicate base paths and links in 404 recommended pages
+- Auto-populated og:url tag with appropriate canonical URL
+- Added canonical tag for better SEO
+- Fixed code block overscroll issues
+- Made search engines ignore preview deployments for SEO purposes
+- Fixed referrer tracking to use domain instead of full URL
+- Fixed images always becoming MDX block elements (kept inline images inline)
+- Removed comments in raw markdown pages such that you can use TODO comments without them leaking to users
+- Fixed directory reading support for read_external_files
+
+## Component and styling
+
+- Added dropdowns support in products division
+- Fixed products and menu in middleware nav util function
+- Changed 404 page copy to be more clear
+
+
+
+
+ ## New features
+
+- **Products navigation**: Organize documentation for multiple products with the product switcher navigation
+- **Accessibility CLI command**: Run `mint a11y` to test your docs for accessibility issues
+- **Video responses in API playground**: API playground now supports displaying video response types
+- **API playground prefill**: New option to prefill API playground examples for faster testing
+- **Unauthenticated feedback**: For sites using partial authentication, users can now submit feedback without being authenticated
+- **Shiki theme support**: Shiki themes are now supported for code block styling
+- **Twoslash for code blocks**: TypeScript and JavaScript code blocks now support Twoslash for inline type information
+
+## Accessibility improvements
+
+- Added comprehensive ARIA attributes across components for better screen reader support
+- New "skip to main content" button for keyboard navigation
+- Arrow key navigation support in tab components
+- Enhanced tooltips, nested lists, and code group accessibility
+- Improved focus states and keyboard interaction patterns throughout the UI
+
+## Assistant and analytics enhancements
+
+- Added bar chart visualization for assistant query analytics
+- Unified date range picker in assistant analytics page
+- Zoom controls for assistant analytics charts
+- Better assistant history management with hotkeys and chat sheet improvements
+
+## Bug fixes and reliability
+
+- Fixed z-index issues with side panel overlays
+- Fixed light mode color fallbacks and theme-related styling bugs
+- Fixed API playground expandables not working with anchor links
+- Fixed `.md` link accessibility for ChatGPT and other LLM agents
+- Fixed image dimension handling for percentage-based widths and heights
+- Fixed code block rendering issues with language tags and custom themes
+- Fixed accordion link formatting and styling
+- Fixed footer spacing when assistant configuration is empty
+- Fixed card icon rendering for local repository images
+- Fixed audio file handling in API playground (prevented UTF-8 decoding)
+- Improved PR publish state management in web editor
+
+
+
+
+ ## Language support expansion
+
+- Added support for Romanian and Czech languages in the documentation interface
+- Enhanced localization capabilities with complete translation coverage for new languages
+- Improved language selector functionality across all themes
+
+## UI and user experience improvements
+
+- Fixed tab visibility issues on 404 pages to prevent incorrect active tab highlighting
+- Enhanced image handling with proper width and height attribute passing for non-optimized images
+- Improved 404 page layout and styling consistency
+
+## Infrastructure and performance enhancements
+
+- Enhanced GIF image processing by skipping costly Imgix auto-formatting to reduce processing time and bandwidth usage
+- Optimized image serving performance with special handling for animated content
+
+## Bug fixes and reliability
+
+- Fixed contact email routing in dashboard settings for Assistant add-on requests
+- Enhanced database schema updates for better user management
+
+
+
+
+ ## Web editor and dashboard login improvements
+
+- Continued app router migration for the web editor, removing blockers and improving performance
+- Enhanced login error handling with explicit email validation messages
+- Fixed whitespace handling in email address validation
+
+## Authentication improvements
+
+- Added support for validated redirect parameters in login callback to reduce login friction
+- Improved login flow for SSO with better redirect handling
+
+## Bug fixes and reliability
+
+- Fixed GitLab integration issues with larger repositories
+- Improved dashboard loading performance with optimized deployment queries
+- Fixed SVG path rendering issues in documentation
+- Fixed keyboard navigation in search and chat functionality
+
+
+
+
+ ## Major releases
+
+- **Major enhancement**: AI suggested pages on 404 pages, [when someone hits a dead link → AI agent reads the path → suggests semantically similar pages](https://x.com/mintlify/status/1966625627773059495)
+- **Major release**: web search for assistant can now include external sources\
+ _Note: Contact us to enable this feature for your site._
+
+## Assistant and MCP
+
+- Fixed a bug where the assistant would be incorrectly rate limited due to time window not sliding correctly
+- Fixed a bug with assistant tool calling to properly handle empty `text` blocks
+- Fixed a bug where MCP server name's concatenated with tool calls were sometimes exceeding the 60 character length MCP clients enforce
+- Fixed a bug where the assistant menu would have a height several times larger than the viewport and scroll forever
+- Fixed a bug where assistant spend values could display with greater than two decimal places in the dashboard
+
+## Web editor and deployments
+
+- Security enhancement added to editor such that only users with `write permissions` for the connected git hosting repository can make changes
+- Fixed a bug where preview deployments wouldn't work for branches with `=` in the name
+- Fixed a bug where long branch names would overflow modals on preview deployment creations
+- Quality of life improvement where email query parameter will prefill the input on signup invitations
+- Fixed a bug where copying a page from the context menu was not working on safari
+
+## API playground and navigation
+
+- Multiple API playground response codes now display in a controlled styled select menu instead of the system default select menu when focused
+- You can now use the [`expanded field on navigation groups in your docs.json to make them be default open`](https://mintlify.com/docs/navigation#default-expanded-state)
+
+## SEO and UI
+
+- Fixed a bug where favicons were not showing up in search engines by serving them from the same URL as the documentation site itself for each respective site
+- Fixed a bug where youtube embeds would flash in and out on load
+- Fixed a bug where expanding the feedback menu to include written responses would cause layout shift with the table of contents
+- Fixed a bug where text would leak above the topbar on the maple theme when a dismissed the notification banner
+- Enhanced the Maple and Willow themes by adding login/logout buttons to the sidebar for easier access
+
+## Analytics and exports
+
+- Fixed reliability issues with assistant analytics view and exports
+- Assistant analytics exports are now executed in the background and sent via email for a more reliable experience
+
+
+
+
+ ## Major release: Enhanced feedback collection
+
+- **Major improvement**: Readers can now give more detailed feedback after selecting _thumbs up/down_, including options and written comments. You can also collect feedback on code blocks and view all responses in your dashboard analytics.\
+ _Note: Contact us to enable this feature for your site._
+
+## Navigation and quality of life improvements
+
+- Quality of life improvement to ignore trailing slashes and double slashes so you don't have to worry about getting them exactly right in your docs.json
+- You can now add a `noAnchor` attribute to your `h1-6` HTML tags to avoid them having an anchor link
+- The Palm theme now has a floating language selector in the bottom left similar to Stripe's approach
+- Added a new field to the docs.json called [`drilldown`](https://mintlify.com/docs/navigation#enable-auto-navigation-for-groups) which allows you to control whether or not users are navigated to the first page in a navigation group when the group is expanded
+- Quality of life improvement to make nested ordered lists alternate styles from decimal/Roman to alpha
+
+## Bug fixes and reliability
+
+- Fixed a bug where scroll position anchor links weren't working correctly when there were JS components on a page
+- Fixed a bug where Google was indexing raw `*.md` files because they were missing a `x-robots-tag noindex` header
+- Fixed a bug with OAuth on protected docs where it wouldn't redirect you back to your starting page once you completed the flow successfully
+- Fixed a bug on previews of auth protected docs where you weren't able to see the entire navigation bar
+- Bug fixes to how SVGs are handled with our new image CDN
+
+## Component and styling enhancements
+
+- Added a new CSS selector for custom styles on `SidebarNavGroupDivider`
+- New regression tests for MDX defined API pages that have security defined on them will ensure a greater degree of stability
+
+## Performance improvements
+
+- Performance improvement by moving the KaTeX CSS from cdnjs to our own CDN on Cloudfront for reduced latency
+
+
+
+
+ ## Image handling improvements
+
+- **Major improvement**: Images no longer cause layout shift by default, even when width and height attributes aren't specified—automatic sizing prevents content jumping during page loads
+- All static files in your repository (PDF, TXT, XML, etc.) are now automatically uploaded and served when you deploy, providing complete asset coverage
+
+## Web editor and deployment enhancements
+
+- Fixed branch creation workflow in web editor to correctly navigate to and stay on newly created branches
+- Enhanced merge conflict dialog with proper escape functionality, no more page reloads required to dismiss conflicts
+- Optimized update workflow performance by cache-invalidating only changed pages during partial updates, reducing deployment times
+
+## Authentication and navigation improvements
+
+- New support for authentication on custom subpaths, if you serve docs at `https://yourdomain.com/docs`, authentication now works seamlessly
+- Fixed sidebar display bug that incorrectly showed when only one link was configured
+- Comprehensive mobile navigation overhaul: centered buttons with proper margin/padding, improved spacing in dropdown menus, removed unnecessary dividers and margins for empty sections, and fixed Maple theme gap/padding issues
+
+## Component and styling fixes
+
+- Resolved `` tag conversion issue that was incorrectly transforming them into Heading components and disrupting custom styling
+- One-click assistant configuration toggle added to dashboard for easier management
+
+## Technical improvements and reliability
+
+- Enhanced logging system for update workflows enabling faster debugging and issue resolution
+- Fixed GitHub rate limiting for customers with 10+ OpenAPI/AsyncAPI specs by switching from individual file fetching to repository cloning
+- Improved assistant reliability with backup LLM support, enhanced rate limit error handling, and more robust search tool functionality
+
+
+
+
+ ## Performance and build optimizations
+
+- MDX transpilation now happens at deployment time instead of on every page load in uncached NextJS serverless environments, improving time to first byte for uncached pages.
+- Content-based hashing prevents re-transpilation when MDX hasn't changed, reducing update workflow times by \~50% for customers with large page counts (deployments over 5 minutes should be roughly halved)
+- Preview deployment viewing in the dashboard is now faster with added database indexes and query parallelization in our backend
+- Reduced page size by eliminating duplicate `navigation` data in each page's `rsc` payload—performance gains most noticeable with high page counts or complex navigation structures
+- More aggressive prefetching enables instant page loads more frequently
+
+## API playground and OpenAPI enhancements
+
+- OpenAPI to MCP conversion moved to backend, enabling hosted MCP servers to contain tools (expect clearer documentation and config options soon)
+- Added Ruby support to API playground
+- We added a feature such that you can now [specify API pages using just your docs.json](/api-playground/openapi-setup#auto-populate-api-pages) without creating any new mdx files.
+- Support for [`webhook pages`](/api-playground/openapi-setup#webhooks) in docs navigation from OpenAPI specs
+- Optimized AI model context by removing anchor link specifications from markdown links when navigating to Anthropic, OpenAI, or other providers
+
+## Web editor improvements
+
+- File creation/renaming now saves changes when clicking away instead of requiring Enter key press
+- Fixed branch navigation where changing URL to specific branch would redirect to last active branch instead of intended destination
+- Properly URL encode branch titles containing `/` to prevent navigation breakage
+- Fixed `Ctrl+K` link shortcut in monorepo dashboard Editor that was prepending docs repo path and creating broken links
+
+## Analytics and LLM integrations
+
+- Custom `llms.txt` and `llms-full.txt` support—add to docs repo root to serve at `/llms.txt` and `/llms-full.txt` endpoints for LLM customization
+- Added [Hightouch analytics integration](/integrations/analytics/hightouch#hightouch)
+- Enhanced context menu analytics tracking (dashboard viewing coming soon)
+- Added e2e tests for `llms.txt` and `llms-full.txt` to ensure correct serving
+
+## Component and styling enhancements
+
+- Support for custom classnames in `h{1-4}` tags for applying custom heading styles
+- Fixed `h{1-4}` tags rendering as `Heading` components with chips in custom page mode
+- Added CSS selectors to [breadcrumbs](/organize/navigation#breadcrumbs) for custom CSS targeting
+- Fixed stretched open-graph images by analyzing dimensions to maintain proportions at 56px height
+- Corrected `VSCode` to `VS Code` in contextual menu when enabled
+- Fixed headings within custom components appearing in table of contents alongside semantic headings
+
+## Bug fixes and reliability
+
+- Fixed PDF render issues with certain page titles by sanitizing characters that cause generation problems
+- Resolved CLI error `Cannot convert undefined or null to object` when encountering empty OpenAPI JSON files
+- Fixed custom `docs.json` open-graph metatags being overwritten by generated ones
+- Fixed RSS feed button clicks when landing on anchor links by using origin + pathname for RSS links
+- Improved CLI download speed by removing sourcemaps
+
+## Technical improvements
+
+- Added visual tests to CI pipeline for earlier regression detection
+- Enhanced error handling and debugging capabilities
+- Comprehensive testing coverage for new features and edge cases
+
+
+
+
+ ## Authentication improvements
+
+- Group-level public access: make entire page groups public via `docs.json` so you don’t need `public: true` on each page ([learn more](https://mintlify.com/docs/authentication-personalization/authentication-setup#group-level))
+- Support [`logoutURL in OAuth configuration`](https://mintlify.com/docs/authentication-personalization/authentication-setup#implementation-3) to delete upstream cookies and complete sign-out
+- On OAuth errors, users are redirected to your specified `logoutURL` to restart the auth flow
+- Fixed a flash of a 500 error during OAuth/JWT flows before the callback
+- Auto-strip `https://` from URLs in OAuth/JWT auth configuration to prevent misconfiguration
+
+## API playground enhancements
+
+- New [Search API endpoint](https://mintlify.com/docs/api-reference/assistant/search) so you can build agents and MCP servers on top of your docs
+- `openapi` and `asyncapi` files are now served at their specified paths (for example, `https://mydocsurl.extension/{openapi-or-file-name}.json`)
+- You can now use the [`x-mint field in your openapi files`](https://mintlify.com/docs/api-playground/openapi-setup#x-mint-extension) to override generated fields, customize preface content, or change endpoint URLs in code samples
+- [`x-mcp is now x-mint.mcp`](https://mintlify.com/docs/api-playground/openapi-setup#mcp) in OpenAPI configurations to control which routes are exposed as MCP tools
+
+## Assistant updates
+
+- Fixed an issue where the action menu (containing options like copy and thumbs up) for older messages disappeared when new ones streamed in
+- Fixed accessibility of nested `/mcp/...` pages after the [hosted MCP servers release](https://mintlify.com/docs/ai/model-context-protocol#accessing-your-mcp-server) from last week
+
+## Performance and reliability
+
+- All image and video assets present in your docs repo are now served at the appropriate path on your domain. For example, if you have `/assets/marketing/my-logo.png` in your repo, it will be available at `https://mydocsurl.extension/assets/marketing/my-logo.png`.
+- Email field on login for the Mintlify dashboard now autofocuses so you can start typing immediately _(quality of life improvement)_
+- Both custom domains and subdomains in Redis for a performance improvement on navigation load times (\~50ms latency reduction)
+- Added retry logic for PDF exports to improve reliability
+- Fixed cookie consent popup reappearing after acceptance or dismissal—first selection is now respected
+- Fixed copying a page to clipboard on Safari by specifying a MIME `type` in `navigator.write`
+
+## Technical improvements
+
+- CLI bugfixes for windows and pnpm, plus CI tests to prevent regressions
+- Improved error logging output—a quality of life upgrade for our engineering team when debugging
+- Minor fixes to the broken-link CI action when `contentDirectory` files are missing
+- Fixed a regression caused by the auth-protected preview fixes from last week where the active tab was not being set correctly in the navigation UI
+- Fixed theme light background color not being applied to active tab icons
+- Fixed an issue where changing the auth type in the dashboard would update and then flip back to the previously saved type—now the new selection persists after saving
+- Internal DX improvements for enterprise customers with custom UI libraries—it's now easier for us to include your components and accommodate requests on shorter timelines
+
+
+
+
+ ## Authentication improvements
+
+- Local development improvements to auth, enabling faster development of auth features and bug fixes in this product area
+- Preview deployments now available for auth-protected sites
+- Fixed redirect behavior to properly return users to their original page after authentication
+- Fixed logout button display for full authentication (previously only worked for partial authentication)
+
+## API playground enhancements
+
+- Fixed `multipart/form-data` file upload functionality in the API playground
+- Fixed anchor link behavior so clicking them updates the URL without scrolling to top of page
+- Fixed anchor link issues in nested tabs
+
+## Assistant updates
+
+- New Assistant API so you can build it into your own products, compatible with AI SDK
+- Added copy button to chat responses
+- Fixed issue with retrying messages in the assistant
+- Improvements to default assistant prompt to make it less verbose by default
+
+## Performance and reliability
+
+- Made search feel more crisp and accurate by aborting debounced requests as you type
+- Resource provisions for a new CDN - expect image asset and page load times to improve soon
+- Fixed bugs for rendering complex Mermaid diagrams like GANTT charts
+- Fixed CLI bugs on Windows to improve stability and added tests to prevent regression
+
+## Technical improvements
+
+- Added OpenTelemetry for traces in NextJS application to improve time to first byte for customers
+- Migrated from Octokit to GitHub API Client to improve latency in the web editor experience
+- Fixed duplicate meta tags for OpenGraph
+- Upgraded MongoDB from version 6 to 7 for improved performance and new features
+
+
+
+
+ ## Slack app
+
+- Zero friction access: Bot responds to DMs, @mentions, and any question in your `#ask-ai` channel
+- One-click setup: Install directly from your Mintlify dashboard in seconds
+- Contextual answers: Searches your entire documentation to provide relevant, accurate responses
+- Deflect support interruptions: Turn daily questions into instant, self-serve answers
+
+Learn more in our [Slack app guide](/ai/slack-app).
+
+## Hosted MCP servers
+
+Deploy hosted Model Context Protocol (MCP) servers directly through Mintlify to integrate with AI tool like Claude, Cursor, and others. Learn more in our [MCP guide](/ai/model-context-protocol).
+
+Help users quickly connect your MCP server to Cursor or VS Code from any page in your docs via the contextual menu. See [Contextual menu](/ai/contextual-menu) for more information.
+
+## Code block improvements
+
+- Improved syntax highlighting
+- Added more customization options including focus mode, expandable code blocks, dark and light mode responsiveness, language dropdown menu, line numbering, and icons
+
+
+
+
+ ## AI assistant updates
+
+- Improved accuracy through agentic RAG with tool calling
+- Provides navigable links to referenced pages so that users can go directly to the source of answers
+- Copy shortcut for code examples generated by assistant
+- "Ask AI" shortcut on code blocks in documentation to generate explanations from the assistant
+
+Learn more in the [assistant docs](/ai/assistant).
+
+## Subscribable changelogs
+
+- Automatically generate an RSS feed from changelog pages
+- Integrate RSS-enabled updates with Slack, email, and other tools
+
+Learn more in our new [Changelog guide](/create/changelogs)
+
+
+
+
+ ## API playground stability updates
+
+- Search to find an endpoint
+- Indicate a deprecated endpoint with a tag
+- Hide auto-generated API pages from navigation
+- Upload multipart or form data files
+
+Learn more at [API playground docs.](/api-playground/)
+
+## `mint update`
+
+Can now use `mint update` to update your CLI.
+
+
+
+
+ ## Web Editor 3.0
+
+
+
+
+
+Overhauled usability in the WYSIWYG editor.
+
+**Major improvements**
+
+- Search for file names using ⌘ + P shortcut
+- Pages load 10x faster
+- Faster load times when searching for a branch
+- Page options tab to configure layout, title, & metadata for SEO
+- Floating toolbar when you highlight text
+
+**Additional fixes**
+
+- Fixed top margin for changelog components
+- Improved reliability of right click behavior
+- After clicking publish, you’ll stay on the same page instead of being brought to an empty state
+- Standardized colors in file icons
+- Improved reliability after selecting new branches several times in a row
+- Removed Diff mode
+- More consistency when creating a new folder from the dropdown
+- Fixed block quotes creating more block quotes when trying to deselect
+
+
+
+## AI Translations in beta
+
+
+
+
+
+Translate all of your documentation with AI. [Learn more.](organize/navigation#localization)
+
+## Export docs to PDF in beta
+
+Export all of your documentation, a subdirectory, or a singe page as a PDF.
+
+## React hook support
+
+Bring interactivity to your docs. All standard React hooks are automatically available in your MDX files. [Learn more.](customize/react-components)
+
+
+ ## MCP server generator
+
+
+
+
+
+Generate MCP servers so that AI applications can interact with your docs or APIs. Written content is automatically generated as an MCP server, and you can generate an MCP server from your OpenAPI spec with one click. Check out [docs on getting started with MCP.](/ai/model-context-protocol)
+
+## Improvements
+
+- Tag changelog updates so end users can filter updates
+- Sonnet-3.7 supported for AI Chat. Configure your preferred model through the dashboard
+- Change your deployment name directly in dashboard settings
+
+## Bug fixes
+
+- OG images fixed
+- Fixed icon style inconsistency for anchors without container
+- Improved styling nits for dashboard border for mobile-tablet-desktop responsiveness
+- Show code examples even when in simple mode for API playground
+- Support "command + k" shortcut for search in web editor
+- Codeblocks within callouts expand to fill the width of the callout area
+
+
+
+
+ ## New configuration schema `docs.json`
+
+
+
+
+
+We've introduced a new `docs.json` schema as a replacement for `mint.json`, to support better multi-level versioning, easier visual comprehension, and more consistent terminology. For more information on what's changed, [check out our blog](https://mintlify.com/blog/refactoring-mint-json-into-docs-json).
+
+Upgrade from `mint.json` to `docs.json` with the following steps:
+
+1. Make sure your CLI is the latest version
+
+```bash theme={null}
+npm i mint@latest -g
+```
+
+1. In your docs repository, run
+
+```bash theme={null}
+mint upgrade
+```
+
+1. Delete your old `mint.json` file and push your changes
+
+## CI Checks
+
+Automatically lint your docs to find broken links, discover spelling and grammar issues, or enforce writing styles with your own Vale config. Learn more in our [docs](deploy/ci).
+
+## .md support for LLMs
+
+All documentation pages are now automatically available as plain Markdown files—just append `.md` to the URL. This makes it easier for LLMs to ingest individual pages from your documentation.
+
+## More Themes
+
+
+
+
+
+New [pre-built themes](customize/themes) to modify the look & feel of your docs. Configure via your [docs.json file](organize/settings).
+
+Now available:
+
+- Maple
+- Palm
+- Willow
+
+## Other improvements
+
+- [Guide to Technical Writing:](https://mintlify.com/guides/introduction)Best practices for writing technical documentation, including audience research, content types, and writing tips.
+- [Dropdown component](organize/navigation#dropdowns): Organize navigation with a dropdown, in addition to tabs and anchors.
+- [AI syntax fixer](https://x.com/ricardonunez_io/status/1892334887644123192): The web editor will catch if there’s a parsing error and use AI to suggest fixes.
+
+
+
+
+ ## AI Assistant Improvements
+
+- New UI with dedicated chat page & pre-filled prompts
+- Stability improvements. For example, bug fixes of editing the wrong file or no files at all
+- More robust knowledge for adding & editing components
+- Improved `docs.json` file editing
+
+## Partial Authentication
+
+Customize access to any page or section of content depending on user permissions. Supports connecting with your own authentication system.
+
+## Revamped API Playground
+
+We’ve overhauled the design and performance of the [API Playground](/api-playground/). Updates include:
+
+- Easier detail expansion for an overview of a field
+- More intuitive nested design. For example, adding or deleting items
+- Faster response times
+
+## Quality Improvements
+
+- Support for requiring authentication to access preview deployments
+
+
+
+
+ ## Authentication
+
+
+
+
+
+Make docs private by setting up authentication via JWT, OAuth, or a universal password. With this privacy, you can create an internal knowledge base or prevent competitors from seeing your docs.
+
+
+
+
+ ## AI Writer
+
+
+
+
+
+You can now ask AI to make changes to your docs, with the context of all existing documentation. Type in a prompt and the writer will propose changes by generating a pull request.
+
+## GitLab Integration Upgrade
+
+We've improved our support for syncing with GitLab, such as enabling automated updates and preview deployments. Check out our [docs on GitLab](/deploy/gitlab) to get started.
+
+## Web Editor
+
+
+
+
+
+We've revamped our web editor so that you can now update docs with a fully WYSIWYG experience, while syncing with markdown.
+
+Check out our [docs on getting started with Web Editor](/editor).
+
+## /llms.txt support
+
+
+
+
+
+All docs instances are now automatically hosted at /llms.txt and /llms-full.txt so that LLMs can easily ingest your documentation. For more information, read the [docs on the new llms.txt standard.](https://llmstxt.org)
+
+## Localization
+
+You can now localize your docs which operates similarly to versioning. Add a `locale` to a version and fixed content in Mintlify like "Was this page helpful?" will also match the locale.
+
+### Quality Improvements
+
+- Return chat & search results based on the current version that the user is reading
+- Authenticate users with OAuth, in addition to JWT or Shared Session tokens.
+
+
+
+
+ ## Changelogs
+
+Launched a new [Update component](/components/update) to make it easier to display and report updates (like this one) to your users.
+
+
+
+
+
+## Code Line Highlighting
+
+You can now highlight lines of code in your docs to emphasize and bring attention to important parts by adding a special comment after the language identifier. Use curly braces `{}` and specify line numbers or ranges separated by commas.
+
+```javascript Line Highlighting Example {1,3,4,5} theme={null}
+const greeting = 'Hello, World!'
+function sayHello() {
+ console.log(greeting)
+}
+sayHello()
+```
+
+````mdx theme={null}
+```javascript Line Highlighting Example {1,3-5}
+const greeting = 'Hello, World!'
+function sayHello() {
+ console.log(greeting)
+}
+sayHello()
+```
+````
+
+## Light mode code blocks
+
+Code blocks now have a light mode variant which can be enabled by adding the following to your `docs.json`:
+
+```json theme={null}
+"codeBlock": {
+ "mode": "auto"
+}
+```
+
+## Advanced Footer
+
+
+
+
+
+You can now add more links to the standard footer. This upgrade provides more consistency between landing pages and docs, or greater customization if you want to spotlight specific pages like socials or status logs.
+
+## Filter search based on the current user
+
+When personalization is enabled, search results are now filtered based on the current logged in user so that they only see the relevant content.
+
+## Custom Prompts for AI Chat
+
+You can now customize the prompts for the AI chat. Please reach out to [support](mailto:support@mintlify.com) if you'd like to customize the prompts.
+
+## Dashboard Improvements
+
+- Added ability to change custom domain to be /docs directly through dashboard settings.
+- Consolidated the login and signup pages to decrease friction and confusion.
+- Implemented the discovery login flow so that users that are members of multiple organizations can now switch between them.
+- Added login with Google OAuth
+- Added ability to add new deployment through dashboard settings.
+
+## Bug Fixes
+
+- Can now use leading slashes in navigation.
+- Can now edit CSS & JS files in the web editor.
+- Fixed `suggestEdit` not showing up even when enabled.
+- Fixed keyboard navigation for Search and Chat such that you can now use the up and down arrow keys to navigate the results.
+- Don't allow search engines to crawl user-auth protected pages.
+- Revalidate the cache when an org is deleted.
+- We now use the Scalar OpenAPI parser to parse OpenAPI definitions which improves the performance, fixes parsing issues, and surfaces better error messages.
+- Top-level descriptions are now supported in API reference pages autogenerated from OpenAPI definitions.
+- Add in-line-style support for icons
+- Fixed the pop-in of custom CSS in docs.
+- Properly show in-line code styling in conjunction with links.
+- Maintain scroll position when you click the back button in a browser.
+
+
+
+
+ ## Custom Fonts
+
+
+
+
+
+Personalize the font of your docs to your own font hosted on a CDN or by choosing from Google fonts to match your docs with your brand.
+
+## Images in Card components
+
+Add an `img` property to a card to display an image on the top of the card. Learn more about it [here](/components/cards#image-card).
+
+## Update Speed Performances
+
+
+
+
+
+For large projects (\~3,000 files), the download step for docs updates is now \~440x faster - a 99.8% time reduction. Across the board, file downloads during updates are now \~5.5x faster - an 81.8% time reduction.
+
+## SEO improvements
+
+
+
+
+
+We've fixed both the mobile and desktop layout of our docs so that they are more SEO-friendly - including adding proper aria tags to navbar and toggle elements.
+
+## Dashboard Improvements
+
+- App router migration in the dashboard.
+- Search analytics are now available in the dashboard.
+- Delete an org functionality has been added to the dashboard.
+- Shipped GitLab connection UI.
+- Fix incorrect analytics data.
+- Add-on's can now be directly purchased through the dashboard.
+
+## Bug Fixes
+
+- Fixed a bug where the top bar would not stretch to the width of the screen when it's in custom mode and the sidebar layout is `sidenav`.
+- Fix relative positioning of the AI widget.
+
+## More
+
+- **Troubleshooting for API pages**: API pages could be complicated so we listed common issues to help you sort them out quickly — [Read the docs](/api-playground/troubleshooting)
+
+
+
+
+ ## OpenAPI Reference Pages
+
+- Endpoints defined by OpenAPI that are complex and recursive are now 98% smaller.
+- We now show [additionalProperties](https://swagger.io/docs/specification/data-models/dictionaries/) in OpenAPI pages.
+
+## File Uploads in API Playground
+
+By default, API playground requests are proxied by Mintlify. Now you can use `disableProxy` to disable this behavior and support request types like file uploads.
+
+- [Learn more about API configurations](organize/settings#api-configurations)
+
+## Mobile SEO improvements
+
+We've fixed the mobile layout of our docs so that they are more SEO-friendly - including adding proper aria tags to elements.
+
+## Support Form
+
+We added a more detailed support form to the Mintlify dashboard. You can now submit a form to get in touch with us.
+
+## Bug Fixes
+
+- Fixed a bug for the Segment integration functionality.
+- We now raise more granular error messages for GitHub permissions when interacting with the editor.
+- Fixed bugs where the navigation would not properly expand when a direct link was used.
+
+
+
+
+ ## AI Widget
+
+
+
+
+
+For `Pro` users, we introduced Mintlify Widget, an extension of your docs to answer your users' questions when and where they asked. You can add this AI-powered chatbot to any web page: your landing page, inside your product, or on your existing documentation pages.
+
+- [Read the blog announcement](https://mintlify.com/blog/widget)
+
+## Pro Plan
+
+We also updated our pricing plans for better customizability and scale.
+
+- [Read the blog announcement](https://mintlify.com/blog/pro-plan)
+
+## API Playground Code Example Sync
+
+When you browse API docs, the selected code example now syncs across your pages.
+
+## Insights
+
+Currently in beta, this feature summarizes common user questions and patterns into easy-to-digest reports with AI-powered suggestions on how to improve your product.
+
+
+
+
+ ## Launch Week Highlights
+
+- Themes: Customize your styling with pre-configured themes. Just add the theme Quill, Prism, or Venus to your `docs.json` file and it'll update your docs styling.
+- Search V2: directly query OpenAPI endpoint descriptions and titles to reach API Reference pages, remove hidden pages from search, and enjoy our updated search bar UI.
+- Web Editor branching: create branches in our web editor without an IDE.
+- User Personalization: authenticate users with Shared Session or JWT so that you can show them customized content, such as pre-filling API keys or showing specific content for customers.
+- OpenAPI Automation Upgrades: to auto-populate API Playground pages, you can add an `openapi` field to an object in tabs or anchors arrays in the `docs.json`.
+
+
+
+
+ ## Okta SSO
+
+We now support sign-on via Okta SAML and OIDC.
+
+## Mintlify REST API
+
+Programmatically rigger updates to your documentation.
+
+
+
+
+ ## Custom mode
+
+Add a configuration to the metadata to remove all elements except for the top bar. Example use cases:
+
+- Create a custom global landing page setup with custom components
+- Add full-screen videos or image galleries
+- Embed custom iFrame demo elements to add intractability to your docs
+
+Check out our [Custom Mode docs](organize/pages#custom-mode).
+
+
+
+
+ ## Mintlify MDX for VSCode
+
+Call snippets of our pre-built components and callouts without leaving VSCode. [Install the extension here](https://marketplace.visualstudio.com/items?itemName=mintlify.mintlify-snippets).
+
+
+
+
+ ## Quality Improvements
+
+- Dashboard upgrades: view update logs to see what's changed and status of an update, toggle between Mintlify projects to manage deployments
+- Versioning with tabs fully supported
+- Wildcard redirects now supported
+- CLI Error Detection: we now show the position of invalid frontmatter when there are parsing issues during local development
+
+
+
+
+ ## Launch Week Highlights
+
+- Preview Deployments: When you create a pull request, we'll generate a unique link that shows a live preview of what your docs look like in prod. You can share this link with teammates.
+- Snippets V2: We now support fully reusable components and variables for snippets.
+- Open-source MDX Engine: We've exposed two APIs—getCompiledMdx and MDXComponent—so you can access Mintlify markdown and code syntax highlighting. [Contributions to the project](https://github.com/mintlify/mdx) are welcome.
+- AI Chat Insights: Segment chat history by date and increase AI Chat quota from the dashboard, and see how often a specific query appears.
+
+
+
+---
+
+> To find navigation and other pages in this documentation, fetch the llms.txt file at: https://mintlify.com/docs/llms.txt
diff --git a/v2/pages/07_resources/changelog/migration-guide.mdx b/v2/pages/07_resources/changelog/migration-guide.mdx
new file mode 100644
index 00000000..e6d901d6
--- /dev/null
+++ b/v2/pages/07_resources/changelog/migration-guide.mdx
@@ -0,0 +1,3 @@
+---
+sidebarTitle: 'Migration Guide'
+---
diff --git a/v2/pages/07_resources/concepts/brief-history-of-video.mdx b/v2/pages/07_resources/concepts/brief-history-of-video.mdx
new file mode 100644
index 00000000..0baaa875
--- /dev/null
+++ b/v2/pages/07_resources/concepts/brief-history-of-video.mdx
@@ -0,0 +1,34 @@
+---
+title: 'Brief History of Video'
+---
+
+# Brief History of Video
+
+## Brief history of video technicals
+
+
+
+ Mechanical and then electronic television systems emerge.
+
+
+ Widespread broadcast TV; analog signals dominate.
+
+
+ VHS and Betacam introduce portable recording; digital experimentation begins.
+
+
+ Digital video (DV) and MPEG compression make video storage and transmission viable.
+
+
+ Broadband + codecs like H.264 transform online streaming; YouTube launches (2005).
+
+
+ Adaptive bitrate streaming (HLS/DASH) becomes standard; GPUs accelerate encoding.
+
+
+ Live streaming explodes (Twitch, Instagram Live); mobile video becomes the majority of internet traffic.
+
+
+ AI enters the pipeline — upscaling, captioning, generative video, real-time inference; decentralised GPU networks like Livepeer make video compute cheaper and globally accessible.
+
+
diff --git a/v2/pages/07_resources/concepts/livepeer-101.mdx b/v2/pages/07_resources/concepts/livepeer-101.mdx
new file mode 100644
index 00000000..40beeae4
--- /dev/null
+++ b/v2/pages/07_resources/concepts/livepeer-101.mdx
@@ -0,0 +1,17 @@
+
+
+# Livepeer 101
+
+## Key Concepts & Definitions
+**Developer**
+
+A developer is anyone building with Livepeer, usually via hosted services.
+They only become gateway operators if they need direct protocol access.
+-> A developer is someone building apps or integrations using Livepeer
+—usually via Studio, Daydream, or other developer platforms
+—but not necessarily running nodes or gateways.
+
+**Gateway Operator / Gateway**
+
+A gateway is a Livepeer node run by an operator—not a hosted product.
+Running a gateway = interacting directly with the protocol.
\ No newline at end of file
diff --git a/v2/pages/07_resources/concepts/livepeer-core-concepts.mdx b/v2/pages/07_resources/concepts/livepeer-core-concepts.mdx
new file mode 100644
index 00000000..a6a4d535
--- /dev/null
+++ b/v2/pages/07_resources/concepts/livepeer-core-concepts.mdx
@@ -0,0 +1,2 @@
+# Livepeer Core Concepts
+
diff --git a/v2/pages/07_resources/documentation-guide/contribute-to-the-docs.mdx b/v2/pages/07_resources/documentation-guide/contribute-to-the-docs.mdx
new file mode 100644
index 00000000..cc8cbd4d
--- /dev/null
+++ b/v2/pages/07_resources/documentation-guide/contribute-to-the-docs.mdx
@@ -0,0 +1,20 @@
+---
+sidebarTitle: 'Contribute'
+title: 'Contribute To The Docs'
+---
+
+We love community feedback and contributions, and it's our mission to make it easy for everyone to contribute to these docs and provide feedback for us to make them even better!
+
+## Provide Feedback
+
+Any page! -> Thumbs up / thumbs down and messages might be a custom mintlify feature - check
+
+## Contributing To The Docs
+
+### Non-Tech Guide
+
+Form
+
+### The 'I Like GIT & MD Guide'
+
+PRs
diff --git a/v2/pages/07_resources/documentation-guide/docs-features-and-ai-integrations.mdx b/v2/pages/07_resources/documentation-guide/docs-features-and-ai-integrations.mdx
new file mode 100644
index 00000000..21c75fbe
--- /dev/null
+++ b/v2/pages/07_resources/documentation-guide/docs-features-and-ai-integrations.mdx
@@ -0,0 +1,12 @@
+---
+sidebarTitle: 'Features & AI'
+title: 'Features and AI Integrations'
+---
+
+## Automations
+
+## AI features
+
+- Assistant
+- Integrations to OpenAI, Claude
+- Downloadable AI-friendly docs
diff --git a/v2/pages/07_resources/documentation-guide/documentation-guide.mdx b/v2/pages/07_resources/documentation-guide/documentation-guide.mdx
new file mode 100644
index 00000000..d82681c2
--- /dev/null
+++ b/v2/pages/07_resources/documentation-guide/documentation-guide.mdx
@@ -0,0 +1,14 @@
+---
+sidebarTitle: 'Guide'
+title: 'Guide To Using The Documentation'
+---
+
+## Using the Docs Effectively
+
+Docs Layout & Navigation Features
+
+### Doc's AI Features & Integrations
+
+### Contributing to the Docs
+
+- Github Link
diff --git a/v2/pages/07_resources/documentation-guide/documentation-overview.mdx b/v2/pages/07_resources/documentation-guide/documentation-overview.mdx
new file mode 100644
index 00000000..a0927951
--- /dev/null
+++ b/v2/pages/07_resources/documentation-guide/documentation-overview.mdx
@@ -0,0 +1,48 @@
+---
+sidebarTitle: 'Overview'
+title: 'Documentation Overview'
+description: 'This page outlines the ethos, objectives & features of the docs, giving you a clear navigational roadmap'
+---
+
+### Doc's Outline
+
+Livepeer is a vibrant and broad ecosystem, and the community is equally diverse, ranging from creators, developers, founders, hardware operators, AI scientists, web3 participants, end-users and many, many more.
+
+Learning is also different for everyone, with user preferences as unique as the community across the following:
+
+- Format (like text, engineering references or video)
+- Style of learning (hands-on, reading, visual)
+- Content (ELI5)
+- AI helpers
+
+These docs aim to cater, as much as possible, to all segments of the vibrant Livepeer Community.
+
+
+Have a suggestion for improvement for us? -> \[link]
+
+
+### Doc's Ethos
+
+These docs aim to make it easy for all users to
+
+- Find the information they are looking for
+- Understand the Livepeer protocol & products
+- Navigate the Livepeer ecosystem
+- Build on the Livepeer protocol
+- Use Livepeer & Ecosystem products
+-
+
+It utilises a streamlined setup & the diaxlis format
+
+### Doc's User Paths
+
+These doc's are intended to provide a clear zero to hero user journey for the many talented folks in the Livepeer Ecosystem.
+
+Recommended paths for user are below
+
+1. All users interested in understanding the Livepeer Network, Protocol & Ecosystem
+2. End-users looking for Livepeer Realtime Video or AI plug & play products
+3. Developers building on the Livepeer Video or AI Protocol from tinkerers to founders & enterprise clients
+4. GPU providers & data centres bringing compute to the Livepeer Network
+5. Livepeer Token Holders looking to stake LPT or participate in open governance
+6.
diff --git a/v2/pages/07_resources/livepeer-glossary.mdx b/v2/pages/07_resources/livepeer-glossary.mdx
new file mode 100644
index 00000000..48b34732
--- /dev/null
+++ b/v2/pages/07_resources/livepeer-glossary.mdx
@@ -0,0 +1,319 @@
+---
+title: 'Livepeer Glossary'
+sidebarTitle: 'Livepeer Glossary'
+description: 'A comprehensive glossary of terms used in the Livepeer Real-time AI & Video Network'
+---
+
+
+ A Searchable view would be ideal here
+
+Terms (Actors & Network)
+- Gateway
+- Orchestrator
+- Delegator
+- Developer
+-
+
+Terms (web3)
+- DePIN
+- LPT
+- ETH
+-
+
+
+Terms (video)
+- Transcoding
+- Ingest
+- Delivery
+- Streaming
+-
+
+Terms (AI)
+- Inference
+- Model
+- Pipeline
+- World Model
+- Agent
+
+
+Terms (Other)
+-
+
+
+
+====
+---
+title: 'Livepeer Glossary'
+sidebarTitle: 'Livepeer Glossary'
+description: 'A comprehensive glossary of terms used in the Livepeer Real-Time AI & Video Network'
+---
+
+A searchable view would be ideal here.
+Terms not verified, brainstorm list only
+
+# Livepeer Core Terms
+### Livepeer Protocol
+The protocol is the ruleset + on-chain logic governing:
+- staking
+- delegation
+- inflation & rewards
+- orchestrator selection
+- slashing
+- probabilistic payments
+- verification rules
+
+The economic and coordination layer that enforces correct behavior.
+
+### Livepeer Network
+The network is the actual running system of machines performing work:
+- Orchestrators (GPU nodes)
+- Transcoders / Workers
+- Gateways
+- Broadcasters
+- Verification processes
+- Job routing
+- Real-time AI & video compute
+
+It is the live, operational decentralized GPU mesh running video + AI jobs.
+
+
+### Protocol Actor
+Protocol Actors are the main participants in the protocol who make up the core functions of th~~e network~~ (wrong).
+Protocol Actors include gateways, orchestrators, and delegators.
+
+### Livepeer Actor
+A Livepeer actor is a participant in the protocol or network—human or machine—that performs a defined role such as submitting jobs, providing compute, verifying work, or securing the system.
+
+### Network Participant
+Same as Protocol Actor (..?)
+
+### Livepeer Ecosystem
+
+### Ecosystem Partner
+A complimentary company working with Livepeer eg Storage, Security, etc.
+
+### Developer Platform
+An abstraction layer on the livepeer protocol that provides tools and services for developers to use & build applications on top of Livepeer. Examples include Livepeer Studio, Daydream, and Streamplace.
+
+###
+
+
+
+# Actors & Network Roles
+### **Gateway**
+A *gateway* is a Livepeer node operated by a user or organization to interact **directly with the Livepeer protocol**.
+Gateways submit jobs, route work to orchestrators, manage payment flows, and provide a direct interface to the network.
+**Not** the same as hosted services like Studio or Daydream.
+
+### **Orchestrator (GPU Node)**
+A supply-side operator that contributes **GPU resources** to the network.
+Orchestrators receive jobs, perform transcoding or AI inference, and get paid via LPT rewards + ETH fees.
+
+### **Transcoder (Worker)**
+A worker process—often managed by an orchestrator—that performs the actual compute work (transcoding or AI inference).
+
+### **Delegator**
+A token holder who stakes their LPT to an orchestrator to help secure the network and earn a share of rewards.
+
+### **Developer**
+Anyone building applications *using* Livepeer, usually through **hosted services** (e.g., Studio, Daydream) or library SDKs.
+Developers only run gateways if they want direct protocol access.
+
+
+### **Broadcaster (-> Gateway)**
+Deprecated Term See **Gateways**
+A job submitter—often a user-facing service—that sends video or AI jobs into the network via a gateway.
+
+### **Verifier**
+A network component (protocol-level) responsible for validating work performed by orchestrators to ensure correctness.
+
+### **Protocol**
+The on-chain governance and incentive layer that coordinates orchestrators, staking rewards, inflation, slashing, and job payments.
+
+---
+
+# Core Network Concepts
+
+### **Job**
+A unit of work submitted to the network: video transcoding tasks, AI inference requests, or real-time processing pipelines.
+
+### **Segment**
+A short chunk of video that is independently transcoded, enabling parallel processing.
+
+### **Ticket / Payment Ticket**
+Livepeer’s probabilistic micropayment mechanism used to pay orchestrators efficiently at high throughput.
+
+### **Rounds**
+Discrete time intervals (Ethereum blocks) used to calculate staking rewards and coordinate global state.
+
+### **Slashing**
+A penalty applied to orchestrators for misbehavior (e.g., failing verification or submitting fraudulent results).
+
+### **Inflation**
+The issuance of new LPT each round, distributed to orchestrators and delegators.
+
+### **Reputation**
+A measure of an orchestrator’s performance, reliability, and trustworthiness, influencing job routing and payments.
+
+---
+
+# Web3 Terms
+
+### **DePIN**
+"Decentralized Physical Infrastructure Network."
+A network where physical or computational resources (GPUs, bandwidth, storage) are coordinated through crypto-economic incentives.
+
+### **LPT (Livepeer Token)**
+The governance and staking token used for orchestrator selection, delegation, reward distribution, and protocol security.
+The Livepeer Token id deployed to the Ethereum Mainnet, however multiple
+
+### Tokenomics (Token Economics)
+Main Definition: The study of designing economic systems for decentralized networks.
+This term is often used when describing both the protocol functions and which token incentives serve to create the optimal codified environment for the eficient operation of the network.
+Usage in Practice:
+This term is often used in multiple senses in web3, being used in both a macro economics sense (to describe high level actors incentives and their impact on behavior) and in a micro sense to describe inflation curves, token allocations, the tokenomics of a specific actor (e.g., orchestrator, delegator, broadcaster, etc.), token release schedules, etc.
+
+### Game Theory
+
+
+### On-chain
+On-chain refers to the data and operations that are recorded on the blockchain.
+In the context of Livepeer, it refers to the protocol layer that governs staking, delegation, rewards, and verification.
+
+### Off-chain
+Off-chain refers to the data and operations that are not recorded on the blockchain.
+In the context of Livepeer, it refers to the network layer that performs video transcoding,
+AI inference, and job routing, including orchestrators and gateways.
+
+### **ETH**
+Ethereum’s native token. Used to pay fees for transcoding, AI jobs, and network interactions.
+
+### **ARB**
+Arbitrum’s native token. Used to pay fees for transcoding, AI jobs, and network interactions.
+
+### **Layer 2**
+A scaling solution for Ethereum that enables high-throughput, low-cost transactions. Livepeer uses Arbitrum Layer 2 for its protocol.
+
+### **Staking**
+Locking LPT to an orchestrator to earn a share of rewards.
+
+### **Gas**
+The fee paid for on-chain operations.
+
+### **Slashing Conditions**
+Network-defined rules that determine when LPT is destroyed due to misbehavior.
+
+### Bridging
+The process of moving tokens between (eg Ethereum Layer 1 and Arbitrum L2)
+
+### Rollups
+One of the methods by which transactions on layer 2 blockchains are tallied and confirmed on the main chain.
+
+
+---
+
+# Video Engineering Terms
+
+### **Transcoding**
+Converting video from one format, resolution, or bitrate to another. Livepeer accelerates this distribution step economically.
+
+### **Ingest**
+The process of receiving a live video feed from a broadcaster.
+
+### **Delivery**
+Sending processed (transcoded) video to viewers via a CDN or playback service.
+
+### **Streaming**
+Continuous transmission of audio/video over the network.
+
+### **RTMP**
+A common ingest protocol for live streaming to gateways.
+
+### **HLS**
+A segmented streaming protocol widely used for delivery to end-users.
+
+### **Bitrate**
+The amount of data encoded per second of video; a key parameter in transcoding.
+
+### **RTMP**
+[Real-Time Messaging Protocol (RTMP)](https://en.wikipedia.org/wiki/Real-Time_Messaging_Protocol)
+is a communication protocol for streaming audio, video, and data over the Internet.
+
+---
+
+# AI Terms
+
+### **Inference**
+Running a model to generate outputs (frames, embeddings, predictions) from inputs.
+
+### **Model**
+A machine learning system (e.g., diffusion model, transformer, world model) hosted on an orchestrator or gateway.
+
+### **Pipeline**
+A sequence of inference steps: e.g., frame generation → upscaling → audio alignment → encoding.
+
+### **Real-Time AI**
+AI workflows that generate or transform video frames fast enough to maintain interactive/streaming use cases.
+
+### **World Model**
+A holistic model capable of understanding and generating coherent multi-modal worlds (video, audio, action).
+
+### **Agent**
+A system that uses models to make decisions or interact with an environment—potentially running on decentralized GPUs.
+
+### **TensorRT**
+An inference optimization framework used to accelerate model execution on NVIDIA GPUs.
+
+### **ControlNet**
+A conditioning mechanism for diffusion models that allows structural guidance (pose, depth, edges, etc).
+
+---
+
+# Payments & Economics
+
+### **Fee Pool**
+Accumulated fees available for orchestrators to earn based on their performance and stake weight.
+
+### **Reward Cut**
+The percentage of staking rewards kept by the orchestrator.
+
+### **Fee Cut**
+The percentage of job fees kept by the orchestrator.
+
+### **Delegator Rewards**
+LPT or ETH earned by delegators proportional to their stake.
+
+---
+
+# Operational Terms
+
+### **Node**
+Any machine running Livepeer software—gateway nodes, orchestrator nodes, or worker nodes.
+
+### **CLI**
+Command-line interface used to configure gateways or orchestrators.
+
+### **Configuration Parameters**
+Settings (flags/env vars) that control node behavior, payments, preferred orchestrators, etc.
+
+### **Health Check**
+A verification check to ensure orchestrators produce correct r
+
+
+# Other Terms
+
+### **Decentralized GPU Network**
+A marketplace of GPUs contributed by orchestrators worldwide, coordinated through crypto incentives.
+
+### **Open Source**
+Code that is publicly available and community-maintained—central to Livepeer’s philosophy.
+
+### **Edge Compute**
+Computing performed near the data source (e.g., near real-time video generation).
+
+### **Latency**
+The delay between receiving input and delivering output—critical in real-time video & AI.
+
+### **Quality Ladder**
+Multiple renditions of a video at different qualities, produced during transcoding for adaptive playback.
+
diff --git a/v2/pages/07_resources/media-kit.mdx b/v2/pages/07_resources/media-kit.mdx
new file mode 100644
index 00000000..2283e69d
--- /dev/null
+++ b/v2/pages/07_resources/media-kit.mdx
@@ -0,0 +1,4 @@
+
+
+# Media Kit
+
diff --git a/v2/pages/07_resources/references/contract-addresses.mdx b/v2/pages/07_resources/references/contract-addresses.mdx
new file mode 100644
index 00000000..56b86317
--- /dev/null
+++ b/v2/pages/07_resources/references/contract-addresses.mdx
@@ -0,0 +1,168 @@
+---
+title: Contract Addresses
+---
+
+# Contract Addresses
+
+Addresses of deployed contracts of the Livepeer protocol on various networks.
+
+## Current
+
+### Arbitrum Mainnet
+
+All contracts on Arbitrum Mainnet implement the Delta version of the protocol.
+
+- **Governor**: [`0xD9dEd6f9959176F0A04dcf88a0d2306178A736a6`](https://arbiscan.io/address/0xD9dEd6f9959176F0A04dcf88a0d2306178A736a6)
+- **Controller**: [`0xD8E8328501E9645d16Cf49539efC04f734606ee4`](https://arbiscan.io/address/0xD8E8328501E9645d16Cf49539efC04f734606ee4)
+- **LivepeerToken**: [`0x289ba1701C2F088cf0faf8B3705246331cB8A839`](https://arbiscan.io/address/0x289ba1701C2F088cf0faf8B3705246331cB8A839)
+- **Minter**: [`0xc20DE37170B45774e6CD3d2304017fc962f27252`](https://arbiscan.io/address/0xc20DE37170B45774e6CD3d2304017fc962f27252)
+- **BondingManager (Proxy)**: [`0x35Bcf3c30594191d53231E4FF333E8A770453e40`](https://arbiscan.io/address/0x35Bcf3c30594191d53231E4FF333E8A770453e40)
+- **BondingManager (Target)**: [`0xF62C30242fccd3a46721f155d4d367De3fD5B3b3`](https://arbiscan.io/address/0xF62C30242fccd3a46721f155d4d367De3fD5B3b3)
+- **TicketBroker (Proxy)**: [`0xa8bB618B1520E284046F3dFc448851A1Ff26e41B`](https://arbiscan.io/address/0xa8bB618B1520E284046F3dFc448851A1Ff26e41B)
+- **TicketBroker (Target)**: [`0xea1b0F6c8D158328a6e3D3F924B86A759F41465c`](https://arbiscan.io/address/0xea1b0F6c8D158328a6e3D3F924B86A759F41465c)
+- **RoundsManager (Proxy)**: [`0xdd6f56DcC28D3F5f27084381fE8Df634985cc39f`](https://arbiscan.io/address/0xdd6f56DcC28D3F5f27084381fE8Df634985cc39f)
+- **RoundsManager (Target)**: [`0x92d804Ed49D92438aEA6fe552BD9163aacb7E841`](https://arbiscan.io/address/0x92d804Ed49D92438aEA6fe552BD9163aacb7E841)
+- **BondingVotes (Proxy)**: [`0x0B9C254837E72Ebe9Fe04960C43B69782E68169A`](https://arbiscan.io/address/0x0B9C254837E72Ebe9Fe04960C43B69782E68169A)
+- **BondingVotes (Target)**: [`0x68AF80376Bc1CA0C25a83b28e5570E8c7bdD3119`](https://arbiscan.io/address/0x68AF80376Bc1CA0C25a83b28e5570E8c7bdD3119)
+- **Treasury**: [`0xf82C1FF415F1fCf582554fDba790E27019c8E8C4`](https://arbiscan.io/address/0xf82C1FF415F1fCf582554fDba790E27019c8E8C4)
+- **LivepeerGovernor (Proxy)**: [`0xcFE4E2879B786C3aa075813F0E364bb5acCb6aa0`](https://arbiscan.io/address/0xcFE4E2879B786C3aa075813F0E364bb5acCb6aa0)
+- **LivepeerGovernor (Target)**: [`0xd2Ce37BCB287CaDc40647f567C2D3C4220901634`](https://arbiscan.io/address/0xd2Ce37BCB287CaDc40647f567C2D3C4220901634)
+- **ServiceRegistry (Proxy)**: [`0xC92d3A360b8f9e083bA64DE15d95Cf8180897431`](https://arbiscan.io/address/0xC92d3A360b8f9e083bA64DE15d95Cf8180897431)
+- **ServiceRegistry (Target)**: [`0x38093CDca43aeCd7bb474983519A246e93A3b0a7`](https://arbiscan.io/address/0x38093CDca43aeCd7bb474983519A246e93A3b0a7)
+- **AIServiceRegistry (Target)**: [`0x04C0b249740175999E5BF5c9ac1dA92431EF34C5`](https://arbiscan.io/address/0x04C0b249740175999E5BF5c9ac1dA92431EF34C5) (detached from controller)
+- **SortedDoublyLL**: [`0xC45f6918F7Bcac7aBc8fe05302b3cDF39776cdeb`](https://arbiscan.io/address/0xC45f6918F7Bcac7aBc8fe05302b3cDF39776cdeb)
+- **PollCreator**: [`0x8bb50806D60c492c0004DAD5D9627DAA2d9732E6`](https://arbiscan.io/address/0x8bb50806D60c492c0004DAD5D9627DAA2d9732E6)
+- **MerkleSnapshot**: [`0x10736ffaCe687658F88a46D042631d182C7757f7`](https://arbiscan.io/address/0x10736ffaCe687658F88a46D042631d182C7757f7)
+- **DelegatorPool**: [`0xfdb06109032AD3671a8f14f5f2E78f4B9E81b567`](https://arbiscan.io/address/0xfdb06109032AD3671a8f14f5f2E78f4B9E81b567)
+- **L2LPTDataCache**: [`0xd78b6bD09cd28A83cFb21aFa0DA95c685A6bb0B1`](https://arbiscan.io/address/0xd78b6bD09cd28A83cFb21aFa0DA95c685A6bb0B1)
+- **L2LPTGateway**: [`0x6D2457a4ad276000A615295f7A80F79E48CcD318`](https://arbiscan.io/address/0x6D2457a4ad276000A615295f7A80F79E48CcD318)
+- **L2Migrator (Proxy)**: [`0x148D5b6B4df9530c7C76A810bd1Cdf69EC4c2085`](https://arbiscan.io/address/0x148D5b6B4df9530c7C76A810bd1Cdf69EC4c2085)
+- **L2Migrator (Target)**: [`0x93BB030735747708b4D33093A98d4c804Cd6B58C`](https://arbiscan.io/address/0x93BB030735747708b4D33093A98d4c804Cd6B58C)
+
+### Ethereum Mainnet
+
+The following contracts on Ethereum Mainnet implement the Delta version of the protocol:
+
+- Governor
+- LivepeerToken
+- L1Escrow
+- L1LPTDataCache
+- L1LPTGateway
+- L1Migrator
+- BridgeMinter
+
+Since the Confluence upgrade, the protocol has been deployed to Arbitrum Mainnet and all contracts on Ethereum Mainnet besides the above are paused.
+
+- **Governor**: [`0xFC3CBed6A3476F7616CC70f078397700136eEBFd`](https://etherscan.io/address/0xFC3CBed6A3476F7616CC70f078397700136eEBFd)
+- **Controller**: [`0xf96d54e490317c557a967abfa5d6e33006be69b3`](https://etherscan.io/address/0xf96d54e490317c557a967abfa5d6e33006be69b3)
+- **LivepeerToken**: [`0x58b6a8a3302369daec383334672404ee733ab239`](https://etherscan.io/address/0x58b6a8a3302369daec383334672404ee733ab239)
+- **Minter**: [`0x505F8c2ee81f1C6fa0D88e918eF0491222E05818`](https://etherscan.io/address/0x505F8c2ee81f1C6fa0D88e918eF0491222E05818)
+- **BondingManager (Proxy)**: [`0x511bc4556d823ae99630ae8de28b9b80df90ea2e`](https://etherscan.io/address/0x511bc4556d823ae99630ae8de28b9b80df90ea2e)
+- **BondingManager (Target)**: [`0x5FE3565dB7F1Dd8d6A9E968D45BD2Aee3836a1D4`](https://etherscan.io/address/0x5FE3565dB7F1Dd8d6A9E968D45BD2Aee3836a1D4)
+- **TicketBroker (Proxy)**: [`0x5b1ce829384eebfa30286f12d1e7a695ca45f5d2`](https://etherscan.io/address/0x5b1ce829384eebfa30286f12d1e7a695ca45f5d2)
+- **TicketBroker (Target)**: [`0x6F582E2bB19ac31D4B1e6eDD0c2eFEabD700f808`](https://etherscan.io/address/0x6F582E2bB19ac31D4B1e6eDD0c2eFEabD700f808)
+- **RoundsManager (Proxy)**: [`0x3984fc4ceeef1739135476f625d36d6c35c40dc3`](https://etherscan.io/address/0x3984fc4ceeef1739135476f625d36d6c35c40dc3)
+- **RoundsManager (Target)**: [`0xC89fE48382F8fda6992dC590786A84275bCD1C57`](https://etherscan.io/address/0xC89fE48382F8fda6992dC590786A84275bCD1C57)
+- **ServiceRegistry (Proxy)**: [`0x406a112f3218b988c66778fd72fc8467f2601366`](https://etherscan.io/address/0x406a112f3218b988c66778fd72fc8467f2601366)
+- **ServiceRegistry (Target)**: [`0x72d9dfa25f75a5f2c27b7336e643a559ae6aeb8e`](https://etherscan.io/address/0x72d9dfa25f75a5f2c27b7336e643a559ae6aeb8e)
+- **GenesisManager**: [`0x3a9543d4767b2c914ea22fd0b07e17b0901aaebf`](https://etherscan.io/address/0x3a9543d4767b2c914ea22fd0b07e17b0901aaebf)
+- **MerkleMine**: [`0x8e306b005773bee6ba6a6e8972bc79d766cc15c8`](https://etherscan.io/address/0x8e306b005773bee6ba6a6e8972bc79d766cc15c8)
+- **MultiMerkleMine**: [`0x182ebf4c80b28efc45ad992ecbb9f730e31e8c7f`](https://etherscan.io/address/0x182ebf4c80b28efc45ad992ecbb9f730e31e8c7f)
+- **SortedDoublyLL**: [`0x1a0b2ca69ca2c7f96e2529faa6d63f881655d81a`](https://etherscan.io/address/0x1a0b2ca69ca2c7f96e2529faa6d63f881655d81a)
+- **Refunder**: [`0x780c98cbb0cc21d6617c05332bd5cf6f847c71c2`](https://etherscan.io/address/0x780c98cbb0cc21d6617c05332bd5cf6f847c71c2)
+- **PollCreator**: [`0xBf824EDb6b94D9B52d972d5B25bCc19b4e6E3F3C`](https://etherscan.io/address/0xBf824EDb6b94D9B52d972d5B25bCc19b4e6E3F3C)
+- **MerkleSnapshot**: [`0x24ebEd82c681f435E944BEEbFAEEAaE443D08438`](https://etherscan.io/address/0x24ebEd82c681f435E944BEEbFAEEAaE443D08438)
+- **L1Escrow**: [`0x6A23F4940BD5BA117Da261f98aae51A8BFfa210A`](https://etherscan.io/address/0x6A23F4940BD5BA117Da261f98aae51A8BFfa210A)
+- **L1LPTDataCache**: [`0x1d24838b35A9c138Ac157A852e19e948aD6323D7`](https://etherscan.io/address/0x1d24838b35A9c138Ac157A852e19e948aD6323D7)
+- **L1LPTGateway**: [`0x6142f1C8bBF02E6A6bd074E8d564c9A5420a0676`](https://etherscan.io/address/0x6142f1C8bBF02E6A6bd074E8d564c9A5420a0676)
+- **L1Migrator**: [`0x21146B872D3A95d2cF9afeD03eE5a783DaE9A89A`](https://etherscan.io/address/0x21146B872D3A95d2cF9afeD03eE5a783DaE9A89A)
+- **BridgeMinter**: [`0x8dDDB96CF36AC8860f1DE5C7c4698fd499FAB405`](https://etherscan.io/address/0x8dDDB96CF36AC8860f1DE5C7c4698fd499FAB405)
+
+## Historical (DEPRECATED - FOR REFERENCE ONLY)
+
+### Arbitrum Mainnet
+
+#### BondingManager (Target)
+
+- **V1**: [`0xe479B9fbA2Cd65f822f451fC8C145c663B995CE6`](https://arbiscan.io/address/0xe479B9fbA2Cd65f822f451fC8C145c663B995CE6)
+- **V2**: [`0xC40df4db2f99e7e235780A93B192F1a934f0c45b`](https://arbiscan.io/address/0xC40df4db2f99e7e235780A93B192F1a934f0c45b)
+- **V3**: [`0x3757DB506ECd9CBE643660C0F5b70db5b321202C`](https://arbiscan.io/address/0x3757DB506ECd9CBE643660C0F5b70db5b321202C)
+- **V4**: [`0x0f9C425E7374602C20370d3fd263155B4c3bDc91`](https://arbiscan.io/address/0x0f9C425E7374602C20370d3fd263155B4c3bDc91)
+- **V5**: [`0x3a941e1094B9E33efABB26a9047a8ABb4b257907`](https://arbiscan.io/address/0x3a941e1094B9E33efABB26a9047a8ABb4b257907)
+- **V6**: [`0x9c9209c9ff6996513b3673d69ee7b36a6c58a8cf`](https://arbiscan.io/address/0x9c9209c9ff6996513b3673d69ee7b36a6c58a8cf)
+- **V7**: [`0x363cdB9BaE210Ef182c60b5a496139E980330127`](https://arbiscan.io/address/0x363cdB9BaE210Ef182c60b5a496139E980330127)
+- **V8**: [`0x557093B1Ab53412166beAd939f34244170b6525B`](https://arbiscan.io/address/0x557093B1Ab53412166beAd939f34244170b6525B)
+- **V9**: [`0x6b397f20DC227B4E23fEc20BBDBe166d0DFFC452`](https://arbiscan.io/address/0x6b397f20DC227B4E23fEc20BBDBe166d0DFFC452)
+- **V10**: [`0xd1C1F5d44D8F83ca2A05Baf40461e550cFDDecA2`](https://arbiscan.io/address/0xd1C1F5d44D8F83ca2A05Baf40461e550cFDDecA2)
+
+#### BondingVotes (Target)
+
+- **V1**: [`0x1561fC5F7Efc049476224005DFf38256dccfc509`](https://arbiscan.io/address/0x1561fC5F7Efc049476224005DFf38256dccfc509)
+
+#### TicketBroker (Target)
+
+- **V1**: [`0x7Beb84c52ce96DFd90431FAA97378994a8baa6df`](https://arbiscan.io/address/0x7Beb84c52ce96DFd90431FAA97378994a8baa6df)
+- **V2**: [`0xD906D192e2503Aafd1BC5F5fc4163E842D5B1d6e`](https://arbiscan.io/address/0xD906D192e2503Aafd1BC5F5fc4163E842D5B1d6e)
+
+#### Minter
+
+- **V1**: [`0x4969dcCF5186e1c49411638fc8A2a020Fdab752E`](https://arbiscan.io/address/0x4969dcCF5186e1c49411638fc8A2a020Fdab752E)
+
+#### L2Migrator (Target)
+
+- **V1**: [`0x4F59b39e2ea628fe8371BDfd51B063319339c7EE`](https://arbiscan.io/address/0x4F59b39e2ea628fe8371BDfd51B063319339c7EE)
+
+### Ethereum Mainnet
+
+#### LivepeerVerifier
+
+- **V1**: [`0xf623811b08b45792d0223d77d9c922dae29712ec`](https://etherscan.io/address/0xf623811b08b45792d0223d77d9c922dae29712ec)
+- **V2**: [`0xe4be2a35dec0063f9dfccb9b740b1acb7eefefec`](https://etherscan.io/address/0xe4be2a35dec0063f9dfccb9b740b1acb7eefefec)
+
+#### Minter
+
+- **V1**: [`0x8573f2f5a3bd960eee3d998473e50c75cdbe6828`](https://etherscan.io/address/0x8573f2f5a3bd960eee3d998473e50c75cdbe6828)
+
+#### BondingManager (Target)
+
+- **V1**: [`0x81eb0b10ff8703905904e4d91cf6aa575d59736f`](https://etherscan.io/address/0x81eb0b10ff8703905904e4d91cf6aa575d59736f)
+- **V2**: [`0x5A9512826EAAF1FE4190f89443314E95A515fE24`](https://etherscan.io/address/0x5A9512826EAAF1FE4190f89443314E95A515fE24)
+- **V3**: [`0x633101b3f15f93c5f415830d48e56b9b1f7ba584`](https://etherscan.io/address/0x633101b3f15f93c5f415830d48e56b9b1f7ba584)
+- **V4**: [`0x05C03EA0039f2e828A725A82939fc1e90de38B44`](https://etherscan.io/address/0x05C03EA0039f2e828A725A82939fc1e90de38B44)
+- **V5**: [`0xCBAa6eA4886b535FC7ABACe3F3985Ed03b3b80a0`](https://etherscan.io/address/0xCBAa6eA4886b535FC7ABACe3F3985Ed03b3b80a0)
+- **V6**: [`0xDC6eE74A18994caD3876a078B6fa4920FD9C507d`](https://etherscan.io/address/0xDC6eE74A18994caD3876a078B6fa4920FD9C507d)
+- **V7**: [`0x1a6007d1D0583452Bd6f45a4e1a9190B15Fbd7E3`](https://etherscan.io/address/0x1a6007d1D0583452Bd6f45a4e1a9190B15Fbd7E3)
+- **V8**: [`0xef5E170b679ddaF5e22ADC10fD23DDdB79E3C0c5`](https://etherscan.io/address/0xef5E170b679ddaF5e22ADC10fD23DDdB79E3C0c5)
+- **V9**: [`0xc8a695155648F18B0cfd6989498B6f8b2c4cc56A`](https://etherscan.io/address/0xc8a695155648F18B0cfd6989498B6f8b2c4cc56A)
+- **V10**: [`0x35F99F326681FE4F38719491be48Ab4950795013`](https://etherscan.io/address/0x35F99F326681FE4F38719491be48Ab4950795013)
+- **V11**: [`0xAC0153a8C5227e43506901a4f3f83FD000c8178f`](https://etherscan.io/address/0xAC0153a8C5227e43506901a4f3f83FD000c8178f)
+- **V12**: [`0x246edEBae14b186a67e3d466A485321169a8bcD5`](https://etherscan.io/address/0x246edEBae14b186a67e3d466A485321169a8bcD5)
+- **V13**: [`0x223398d0BF9cc24960b3886CC481dBf5276EdeD2`](https://etherscan.io/address/0x223398d0BF9cc24960b3886CC481dBf5276EdeD2)
+- **V14**: [`0x0da7c263eCF5cD3ddba275b9A2D63320E28fD287`](https://etherscan.io/address/0x0da7c263eCF5cD3ddba275b9A2D63320E28fD287)
+
+#### JobsManager (Proxy)
+
+- **V1**: [`0xbf07ff45f14c9ff0571b9fbdc7e2b62d29931224`](https://etherscan.io/address/0xbf07ff45f14c9ff0571b9fbdc7e2b62d29931224)
+
+#### JobsManager (Target)
+
+- **V1**: [`0x68b463bca7d561118636e9f028ff0f2e8398dd6a`](https://etherscan.io/address/0x68b463bca7d561118636e9f028ff0f2e8398dd6a)
+- **V2**: [`0xB620c762dd4bC350602936d7401BB8393Ee6687c`](https://etherscan.io/address/0xB620c762dd4bC350602936d7401BB8393Ee6687c)
+- **V3**: [`0x8eade5eec609572bf53deadb88d36f862ddec517`](https://etherscan.io/address/0x8eade5eec609572bf53deadb88d36f862ddec517)
+
+#### RoundsManager (Target)
+
+- **V1**: [`0xa3aa52ce79e85a21d9ccda705c57e426b160112c`](https://etherscan.io/address/0xa3aa52ce79e85a21d9ccda705c57e426b160112c)
+- **V2**: [`0x857d4bf18a80f03d3d11f438825cd3d0aa0d9d68`](https://etherscan.io/address/0x857d4bf18a80f03d3d11f438825cd3d0aa0d9d68)
+
+#### MerkleProof
+
+- **V1**: [`0x289ba1701c2f088cf0faf8b3705246331cb8a839`](https://etherscan.io/address/0x289ba1701c2f088cf0faf8b3705246331cb8a839)
+
+#### ECRecovery
+
+- **V1**: [`0xd8e8328501e9645d16cf49539efc04f734606ee4`](https://etherscan.io/address/0xd8e8328501e9645d16cf49539efc04f734606ee4)
+
+#### JobLib
+
+- **V1**: [`0x4969dccf5186e1c49411638fc8a2a020fdab752e`](https://etherscan.io/address/0x4969dccf5186e1c49411638fc8a2a020fdab752e)
diff --git a/v2/pages/07_resources/resources/videos.mdx b/v2/pages/07_resources/resources/videos.mdx
new file mode 100644
index 00000000..e5273472
--- /dev/null
+++ b/v2/pages/07_resources/resources/videos.mdx
@@ -0,0 +1,3 @@
+[Bad AI, decent script] Livepeer Explained | Decentralized Video Streaming on Ethereum with LPT Tokens
+https://www.youtube.com/shorts/e9A0QVra8fE short
+Imagine a YouTube where you own the network. Let's create new: Imagine a YouTube where viewers and creators share the network: Livepeer decentralizes video streaming. Anyone can contribute bandwidth and earn LPT tokens, broadcasters slash costs and viewers pay less—all on Ethereum with no central gatekeeper. #Livepeer #Web3Video #DecentralizedStreaming #Ethereum #LPT
diff --git a/v2/pages/07_resources/resources_hub.mdx b/v2/pages/07_resources/resources_hub.mdx
new file mode 100644
index 00000000..c9f165d4
--- /dev/null
+++ b/v2/pages/07_resources/resources_hub.mdx
@@ -0,0 +1,7 @@
+---
+title: 'Resource Hub'
+description: 'Livepeer Resource Compendium'
+sidebarTitle: 'Resource Hub'
+---
+
+## Resources Home
diff --git a/v2/pages/08_help/README.mdx b/v2/pages/08_help/README.mdx
new file mode 100644
index 00000000..3863d679
--- /dev/null
+++ b/v2/pages/08_help/README.mdx
@@ -0,0 +1,3 @@
+---
+title: 'Help & Support'
+---
diff --git a/v2/pages/09_internal/ally-notes.mdx b/v2/pages/09_internal/ally-notes.mdx
new file mode 100644
index 00000000..e31cabf1
--- /dev/null
+++ b/v2/pages/09_internal/ally-notes.mdx
@@ -0,0 +1,183 @@
+---
+title: 'Ally Notes'
+sidebarTitle: 'Ally Notes'
+---
+
+
+ Create github download links with cdn.jsdelivr.net
+
+- Protocol: https:// Service Domain cdn.jsdelivr.net
+- Command (gh = GitHub): /gh/
+- User/Organization and Repo: livepeer/
+- Branch Name: @master
+- File Path and Name: /WHITEPAPER.md
+
+Full path: https://cdn.jsdelivr.net/gh/livepeer/wiki@master/WHITEPAPER.md
+
+
+
+GitHub blocks iframe embedding due to X-Frame-Options security headers. This prevents their pages from being embedded in iframes on other sites.
+
+Alternative solutions:
+
+- Link directly to the GitHub file instead of embedding
+- Use GitHub's raw content and display it in a code block
+- Embed using GitHub Gist if you can convert the content (manual copy to mintlify files first) -> would be beginning of a n8n flow
+- Use GitHub's API to fetch and display the content
+
+
+
+
+
+
The Most Reliable Approach: Use a Pre-Build Script
+
The solution involves a script that runs automatically whenever you build or deploy your Mintlify documentation. This script downloads the latest version of the file from GitHub and puts it in your local repository.
+
+
Step 1: Add a Fetch Script to Your Project
+
Create a simple script in your project root (e.g., fetch-whitepaper.sh for Linux/macOS or fetch-whitepaper.js if using Node.js).
This method provides automatically rendered markdown that stays updated while respecting Mintlify's technical limitations during the build process.
+
+
+
+
+ Create github download links with cdn.jsdelivr.net
+
+- Protocol: https:// Service Domain cdn.jsdelivr.net
+- Command (gh = GitHub): /gh/
+- User/Organization and Repo: livepeer/
+- Branch Name: @master
+- File Path and Name: /WHITEPAPER.md
+
+Full path: https://cdn.jsdelivr.net/gh/livepeer/wiki@master/WHITEPAPER.md
+
+
+
+GitHub blocks iframe embedding due to X-Frame-Options security headers. This prevents their pages from being embedded in iframes on other sites.
+
+Alternative solutions:
+
+- Link directly to the GitHub file instead of embedding
+- Use GitHub's raw content and display it in a code block
+- Embed using GitHub Gist if you can convert the content (manual copy to mintlify files first) -> would be beginning of a n8n flow
+- Use GitHub's API to fetch and display the content
+
+
+
+
+
+
The Most Reliable Approach: Use a Pre-Build Script
+
The solution involves a script that runs automatically whenever you build or deploy your Mintlify documentation. This script downloads the latest version of the file from GitHub and puts it in your local repository.
+
+
Step 1: Add a Fetch Script to Your Project
+
Create a simple script in your project root (e.g., fetch-whitepaper.sh for Linux/macOS or fetch-whitepaper.js if using Node.js).
![\"Rick](\"https://media0.giphy.com/media/v1.Y2lkPTc5MGI3NjExN2FteDJ4bno5MHU5Y3QxdGx3eWR2emdhejRhc2c1Y2d3ejY5ajlxMSZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw/Ju7l5y9osyymQ/giphy.gif\")
+
+ )
+}
+
+export const LinkImage = ({ src, alt, caption, icon, hint, href }) => {
+ icon = icon ? icon : 'arrow-turn-down-right'
+ return (
+
+
+ 
+//
diff --git a/snippets/components/image.tsx b/snippets/components/image.tsx
new file mode 100644
index 00000000..dfeb946f
--- /dev/null
+++ b/snippets/components/image.tsx
@@ -0,0 +1,31 @@
+export type imageProps = Record
@@ -26,13 +26,13 @@ few that have agreed to be featured.
title="Dream (by livepeer.cloud)"
href="https://dream.livepeer.cloud/generate"
>
- 
+ 
An open-source platform, built on **Stability-AI/StableStudio**, designed for
experimenting with all pipelines on the AI Subnet.
@@ -40,7 +40,7 @@ few that have agreed to be featured.
diff --git a/ai/contributors/coming-soon.mdx b/v1/ai/contributors/coming-soon.mdx
similarity index 100%
rename from ai/contributors/coming-soon.mdx
rename to v1/ai/contributors/coming-soon.mdx
diff --git a/ai/contributors/developers.mdx b/v1/ai/contributors/developers.mdx
similarity index 100%
rename from ai/contributors/developers.mdx
rename to v1/ai/contributors/developers.mdx
diff --git a/ai/contributors/get-started.mdx b/v1/ai/contributors/get-started.mdx
similarity index 100%
rename from ai/contributors/get-started.mdx
rename to v1/ai/contributors/get-started.mdx
diff --git a/ai/contributors/guides/add-model.mdx b/v1/ai/contributors/guides/add-model.mdx
similarity index 100%
rename from ai/contributors/guides/add-model.mdx
rename to v1/ai/contributors/guides/add-model.mdx
diff --git a/ai/contributors/guides/add-pipeline.mdx b/v1/ai/contributors/guides/add-pipeline.mdx
similarity index 100%
rename from ai/contributors/guides/add-pipeline.mdx
rename to v1/ai/contributors/guides/add-pipeline.mdx
diff --git a/ai/gateways/get-started.mdx b/v1/ai/gateways/get-started.mdx
similarity index 100%
rename from ai/gateways/get-started.mdx
rename to v1/ai/gateways/get-started.mdx
diff --git a/ai/gateways/onchain.mdx b/v1/ai/gateways/onchain.mdx
similarity index 100%
rename from ai/gateways/onchain.mdx
rename to v1/ai/gateways/onchain.mdx
diff --git a/ai/gateways/start-gateway.mdx b/v1/ai/gateways/start-gateway.mdx
similarity index 100%
rename from ai/gateways/start-gateway.mdx
rename to v1/ai/gateways/start-gateway.mdx
diff --git a/ai/introduction.mdx b/v1/ai/introduction.mdx
similarity index 100%
rename from ai/introduction.mdx
rename to v1/ai/introduction.mdx
diff --git a/ai/orchestrators/ai-worker.mdx b/v1/ai/orchestrators/ai-worker.mdx
similarity index 100%
rename from ai/orchestrators/ai-worker.mdx
rename to v1/ai/orchestrators/ai-worker.mdx
diff --git a/ai/orchestrators/benchmarking.mdx b/v1/ai/orchestrators/benchmarking.mdx
similarity index 100%
rename from ai/orchestrators/benchmarking.mdx
rename to v1/ai/orchestrators/benchmarking.mdx
diff --git a/ai/orchestrators/get-started.mdx b/v1/ai/orchestrators/get-started.mdx
similarity index 100%
rename from ai/orchestrators/get-started.mdx
rename to v1/ai/orchestrators/get-started.mdx
diff --git a/ai/orchestrators/models-config.mdx b/v1/ai/orchestrators/models-config.mdx
similarity index 100%
rename from ai/orchestrators/models-config.mdx
rename to v1/ai/orchestrators/models-config.mdx
diff --git a/ai/orchestrators/models-download.mdx b/v1/ai/orchestrators/models-download.mdx
similarity index 100%
rename from ai/orchestrators/models-download.mdx
rename to v1/ai/orchestrators/models-download.mdx
diff --git a/ai/orchestrators/onchain.mdx b/v1/ai/orchestrators/onchain.mdx
similarity index 97%
rename from ai/orchestrators/onchain.mdx
rename to v1/ai/orchestrators/onchain.mdx
index 3b7eb839..69258d3e 100644
--- a/ai/orchestrators/onchain.mdx
+++ b/v1/ai/orchestrators/onchain.mdx
@@ -124,7 +124,7 @@ contract on the [Arbitrum Mainnet](https://arbitrum.io).
@@ -48,7 +48,7 @@ will use Arbitrum in lieu of Ethereum Mainnet for all protocol actions.
@@ -61,7 +61,7 @@ will use Arbitrum in lieu of Ethereum Mainnet for all protocol actions.
diff --git a/delegators/guides/yield-calculation.mdx b/v1/delegators/guides/yield-calculation.mdx
similarity index 100%
rename from delegators/guides/yield-calculation.mdx
rename to v1/delegators/guides/yield-calculation.mdx
diff --git a/developers/introduction.mdx b/v1/delegators/introduction.mdx
similarity index 100%
rename from developers/introduction.mdx
rename to v1/delegators/introduction.mdx
diff --git a/developers/livepeer-studio-cli.mdx b/v1/delegators/livepeer-studio-cli.mdx
similarity index 100%
rename from developers/livepeer-studio-cli.mdx
rename to v1/delegators/livepeer-studio-cli.mdx
diff --git a/developers/quick-start.mdx b/v1/delegators/quick-start.mdx
similarity index 98%
rename from developers/quick-start.mdx
rename to v1/delegators/quick-start.mdx
index e87293e7..a1b7aa3d 100644
--- a/developers/quick-start.mdx
+++ b/v1/delegators/quick-start.mdx
@@ -19,7 +19,7 @@ an API key by clicking on the "Create API Key" button on Developers page.
+ page](/v1/images/tutorials/studio-create-api.png)
You can now use this API key in Livepeer SDKs and APIs in order to authenticate
diff --git a/developers/core-concepts/core-api/access-control.mdx b/v1/developers/core-concepts/core-api/access-control.mdx
similarity index 100%
rename from developers/core-concepts/core-api/access-control.mdx
rename to v1/developers/core-concepts/core-api/access-control.mdx
diff --git a/developers/core-concepts/core-api/asset.mdx b/v1/developers/core-concepts/core-api/asset.mdx
similarity index 100%
rename from developers/core-concepts/core-api/asset.mdx
rename to v1/developers/core-concepts/core-api/asset.mdx
diff --git a/developers/core-concepts/core-api/multistream.mdx b/v1/developers/core-concepts/core-api/multistream.mdx
similarity index 100%
rename from developers/core-concepts/core-api/multistream.mdx
rename to v1/developers/core-concepts/core-api/multistream.mdx
diff --git a/developers/core-concepts/core-api/stream.mdx b/v1/developers/core-concepts/core-api/stream.mdx
similarity index 100%
rename from developers/core-concepts/core-api/stream.mdx
rename to v1/developers/core-concepts/core-api/stream.mdx
diff --git a/developers/core-concepts/livepeer-network/delegators.mdx b/v1/developers/core-concepts/livepeer-network/delegators.mdx
similarity index 100%
rename from developers/core-concepts/livepeer-network/delegators.mdx
rename to v1/developers/core-concepts/livepeer-network/delegators.mdx
diff --git a/developers/core-concepts/livepeer-network/gateways.mdx b/v1/developers/core-concepts/livepeer-network/gateways.mdx
similarity index 100%
rename from developers/core-concepts/livepeer-network/gateways.mdx
rename to v1/developers/core-concepts/livepeer-network/gateways.mdx
diff --git a/developers/core-concepts/livepeer-network/orchestrators.mdx b/v1/developers/core-concepts/livepeer-network/orchestrators.mdx
similarity index 97%
rename from developers/core-concepts/livepeer-network/orchestrators.mdx
rename to v1/developers/core-concepts/livepeer-network/orchestrators.mdx
index 25eb1a17..b782cbfd 100644
--- a/developers/core-concepts/livepeer-network/orchestrators.mdx
+++ b/v1/developers/core-concepts/livepeer-network/orchestrators.mdx
@@ -10,7 +10,7 @@ join the Livepeer network as Orchestrators.
Livepeer network.
-
+
#### Micropayments
diff --git a/developers/core-concepts/player/overview.mdx b/v1/developers/core-concepts/player/overview.mdx
similarity index 100%
rename from developers/core-concepts/player/overview.mdx
rename to v1/developers/core-concepts/player/overview.mdx
diff --git a/developers/core-concepts/studio/in-browser-broadcast.mdx b/v1/developers/core-concepts/studio/in-browser-broadcast.mdx
similarity index 95%
rename from developers/core-concepts/studio/in-browser-broadcast.mdx
rename to v1/developers/core-concepts/studio/in-browser-broadcast.mdx
index 0d700963..563ddb8c 100644
--- a/developers/core-concepts/studio/in-browser-broadcast.mdx
+++ b/v1/developers/core-concepts/studio/in-browser-broadcast.mdx
@@ -4,7 +4,7 @@ by Livepeer's low latency WebRTC technology. This method eliminates the need for
specialized broadcasting equipment or external software such as OBS, allowing
content creators to engage with their viewers effortlessly.
-
+
1. **Initialization:**
diff --git a/developers/core-concepts/studio/stream-health.mdx b/v1/developers/core-concepts/studio/stream-health.mdx
similarity index 97%
rename from developers/core-concepts/studio/stream-health.mdx
rename to v1/developers/core-concepts/studio/stream-health.mdx
index 76c29328..39a31701 100644
--- a/developers/core-concepts/studio/stream-health.mdx
+++ b/v1/developers/core-concepts/studio/stream-health.mdx
@@ -1,7 +1,7 @@
Stream Health is a multi-faceted indicator representing the operational and
performance status of a video stream within Livepeer.
-
+
1. **Global Health Status** is a holistic status of the stream. It can be one of
the following:
diff --git a/developers/core-concepts/studio/webhooks.mdx b/v1/developers/core-concepts/studio/webhooks.mdx
similarity index 98%
rename from developers/core-concepts/studio/webhooks.mdx
rename to v1/developers/core-concepts/studio/webhooks.mdx
index 0aef3a09..5468774f 100644
--- a/developers/core-concepts/studio/webhooks.mdx
+++ b/v1/developers/core-concepts/studio/webhooks.mdx
@@ -13,7 +13,7 @@ information or notifications to the application endpoint.
Webhooks can be created in Studio under the Developer/Webhooks page:
-
+
### Types of Events
diff --git a/developers/guides/access-control-jwt.mdx b/v1/developers/guides/access-control-jwt.mdx
similarity index 100%
rename from developers/guides/access-control-jwt.mdx
rename to v1/developers/guides/access-control-jwt.mdx
diff --git a/developers/guides/access-control-webhooks.mdx b/v1/developers/guides/access-control-webhooks.mdx
similarity index 100%
rename from developers/guides/access-control-webhooks.mdx
rename to v1/developers/guides/access-control-webhooks.mdx
diff --git a/developers/guides/clip-a-livestream.mdx b/v1/developers/guides/clip-a-livestream.mdx
similarity index 100%
rename from developers/guides/clip-a-livestream.mdx
rename to v1/developers/guides/clip-a-livestream.mdx
diff --git a/developers/guides/create-livestream.mdx b/v1/developers/guides/create-livestream.mdx
similarity index 100%
rename from developers/guides/create-livestream.mdx
rename to v1/developers/guides/create-livestream.mdx
diff --git a/developers/guides/encrypted-asset.mdx b/v1/developers/guides/encrypted-asset.mdx
similarity index 100%
rename from developers/guides/encrypted-asset.mdx
rename to v1/developers/guides/encrypted-asset.mdx
diff --git a/developers/guides/get-engagement-analytics-via-api.mdx b/v1/developers/guides/get-engagement-analytics-via-api.mdx
similarity index 98%
rename from developers/guides/get-engagement-analytics-via-api.mdx
rename to v1/developers/guides/get-engagement-analytics-via-api.mdx
index 4395b073..a9b8297d 100644
--- a/developers/guides/get-engagement-analytics-via-api.mdx
+++ b/v1/developers/guides/get-engagement-analytics-via-api.mdx
@@ -179,7 +179,7 @@ the dashboard to retrieve viewership metrics.
### Navigate to the assets page
-
+
### Click on an existing asset
@@ -187,12 +187,12 @@ Click on an existing asset and you'll be brought to that asset's specific
details page. If you haven't created an asset yet, you can follow the
[upload a video asset guide](/developers/guides/upload-video-asset).
-
+
### View your asset's viewership metrics
In the asset's specific detail page you can view its total number of views.
-
+
## Retrieving views from the API
### Get the `playbackId` of an existing stream/asset
diff --git a/developers/guides/get-engagement-analytics-via-grafana.mdx b/v1/developers/guides/get-engagement-analytics-via-grafana.mdx
similarity index 95%
rename from developers/guides/get-engagement-analytics-via-grafana.mdx
rename to v1/developers/guides/get-engagement-analytics-via-grafana.mdx
index 985527c4..a1176388 100644
--- a/developers/guides/get-engagement-analytics-via-grafana.mdx
+++ b/v1/developers/guides/get-engagement-analytics-via-grafana.mdx
@@ -36,7 +36,7 @@ With that we are ready to set up our dashboard!
@@ -58,7 +58,7 @@ With that we are ready to set up our dashboard!
diff --git a/developers/guides/get-engagement-analytics-via-timeplus.mdx b/v1/developers/guides/get-engagement-analytics-via-timeplus.mdx
similarity index 97%
rename from developers/guides/get-engagement-analytics-via-timeplus.mdx
rename to v1/developers/guides/get-engagement-analytics-via-timeplus.mdx
index 3957b9b2..eeee8a78 100644
--- a/developers/guides/get-engagement-analytics-via-timeplus.mdx
+++ b/v1/developers/guides/get-engagement-analytics-via-timeplus.mdx
@@ -41,7 +41,7 @@ to:
combining diverse data sources.
- 
+ 
# How to get started using Timeplus with Livepeer's Engagement Data
@@ -101,7 +101,7 @@ deployed to Timeplus:
diff --git a/developers/guides/listen-to-asset-events.mdx b/v1/developers/guides/listen-to-asset-events.mdx
similarity index 97%
rename from developers/guides/listen-to-asset-events.mdx
rename to v1/developers/guides/listen-to-asset-events.mdx
index 72defe6f..101b4d03 100644
--- a/developers/guides/listen-to-asset-events.mdx
+++ b/v1/developers/guides/listen-to-asset-events.mdx
@@ -33,7 +33,7 @@ Log in to the [Livepeer Studio](https://livepeer.studio/) and navigate to the
[Developers/Webhooks](https://livepeer.studio/dashboard/developers/webhooks)
page.
-
+
Click the "Create Webhook" button and enter the URL of the webhook endpoint. Select any
asset event (with an `asset` prefix) and click "Create Webhook".
diff --git a/developers/guides/listen-to-stream-events.mdx b/v1/developers/guides/listen-to-stream-events.mdx
similarity index 98%
rename from developers/guides/listen-to-stream-events.mdx
rename to v1/developers/guides/listen-to-stream-events.mdx
index 80007d16..2218bd88 100644
--- a/developers/guides/listen-to-stream-events.mdx
+++ b/v1/developers/guides/listen-to-stream-events.mdx
@@ -36,7 +36,7 @@ Log in to the [Livepeer Studio](https://livepeer.studio/) and navigate to the
[Developers/Webhooks](https://livepeer.studio/dashboard/developers/webhooks)
page.
-
+
Click the "Create Webhook" button and enter URL of webhook endpoint. Select any
stream event (with stream/multistream prefix) to receive notifications for and
diff --git a/developers/guides/livestream-from-browser.mdx b/v1/developers/guides/livestream-from-browser.mdx
similarity index 100%
rename from developers/guides/livestream-from-browser.mdx
rename to v1/developers/guides/livestream-from-browser.mdx
diff --git a/developers/guides/managing-projects.mdx b/v1/developers/guides/managing-projects.mdx
similarity index 98%
rename from developers/guides/managing-projects.mdx
rename to v1/developers/guides/managing-projects.mdx
index 88fe781e..1da18a78 100644
--- a/developers/guides/managing-projects.mdx
+++ b/v1/developers/guides/managing-projects.mdx
@@ -4,7 +4,7 @@ description:
"Explore best practices for managing multiple environments in Livepeer Studio"
---
-
+
## Overview
diff --git a/developers/guides/monitor-stream-health.mdx b/v1/developers/guides/monitor-stream-health.mdx
similarity index 100%
rename from developers/guides/monitor-stream-health.mdx
rename to v1/developers/guides/monitor-stream-health.mdx
diff --git a/developers/guides/multistream.mdx b/v1/developers/guides/multistream.mdx
similarity index 100%
rename from developers/guides/multistream.mdx
rename to v1/developers/guides/multistream.mdx
diff --git a/developers/guides/optimize-latency-of-a-livestream.mdx b/v1/developers/guides/optimize-latency-of-a-livestream.mdx
similarity index 100%
rename from developers/guides/optimize-latency-of-a-livestream.mdx
rename to v1/developers/guides/optimize-latency-of-a-livestream.mdx
diff --git a/developers/guides/overview.mdx b/v1/developers/guides/overview.mdx
similarity index 100%
rename from developers/guides/overview.mdx
rename to v1/developers/guides/overview.mdx
diff --git a/developers/guides/playback-a-livestream.mdx b/v1/developers/guides/playback-a-livestream.mdx
similarity index 100%
rename from developers/guides/playback-a-livestream.mdx
rename to v1/developers/guides/playback-a-livestream.mdx
diff --git a/developers/guides/playback-an-asset.mdx b/v1/developers/guides/playback-an-asset.mdx
similarity index 100%
rename from developers/guides/playback-an-asset.mdx
rename to v1/developers/guides/playback-an-asset.mdx
diff --git a/developers/guides/setup-and-listen-to-webhooks.mdx b/v1/developers/guides/setup-and-listen-to-webhooks.mdx
similarity index 99%
rename from developers/guides/setup-and-listen-to-webhooks.mdx
rename to v1/developers/guides/setup-and-listen-to-webhooks.mdx
index 1e997335..0bde68ea 100644
--- a/developers/guides/setup-and-listen-to-webhooks.mdx
+++ b/v1/developers/guides/setup-and-listen-to-webhooks.mdx
@@ -102,7 +102,7 @@ Log in to [Livepeer Studio](https://livepeer.studio/) and navigate to the
[Developers/Webhooks](https://livepeer.studio/dashboard/developers/webhooks)
page.
-
+
Click the Create Webhook button and enter your Ngrok URL as the webhook
endpoint. Select the an event to receive notifications for and click Create
diff --git a/developers/guides/stream-via-obs.mdx b/v1/developers/guides/stream-via-obs.mdx
similarity index 96%
rename from developers/guides/stream-via-obs.mdx
rename to v1/developers/guides/stream-via-obs.mdx
index 9b451135..1573adea 100644
--- a/developers/guides/stream-via-obs.mdx
+++ b/v1/developers/guides/stream-via-obs.mdx
@@ -28,11 +28,11 @@ The creator will then need to:
browser window, select **Window Capture**.
2. Give the device a name:
-
+
@@ -116,7 +116,7 @@ Alternatively, you can:
2. Navigate to the L2 Migration Tool to begin migration to Arbitrum:
@@ -133,7 +133,7 @@ Alternatively, you can:
browser extension.
@@ -149,7 +149,7 @@ Alternatively, you can:
> enter your Ethereum account address.
@@ -163,7 +163,7 @@ Alternatively, you can:
{' '}
@@ -176,7 +176,7 @@ Alternatively, you can:
{' '}
@@ -186,7 +186,7 @@ Alternatively, you can:
{' '}
diff --git a/orchestrators/guides/monitor-metrics.mdx b/v1/orchestrators/guides/monitor-metrics.mdx
similarity index 100%
rename from orchestrators/guides/monitor-metrics.mdx
rename to v1/orchestrators/guides/monitor-metrics.mdx
diff --git a/orchestrators/guides/o-t-split.mdx b/v1/orchestrators/guides/o-t-split.mdx
similarity index 100%
rename from orchestrators/guides/o-t-split.mdx
rename to v1/orchestrators/guides/o-t-split.mdx
diff --git a/orchestrators/guides/set-pricing.mdx b/v1/orchestrators/guides/set-pricing.mdx
similarity index 100%
rename from orchestrators/guides/set-pricing.mdx
rename to v1/orchestrators/guides/set-pricing.mdx
diff --git a/orchestrators/guides/set-session-limits.mdx b/v1/orchestrators/guides/set-session-limits.mdx
similarity index 100%
rename from orchestrators/guides/set-session-limits.mdx
rename to v1/orchestrators/guides/set-session-limits.mdx
diff --git a/orchestrators/guides/troubleshoot.mdx b/v1/orchestrators/guides/troubleshoot.mdx
similarity index 100%
rename from orchestrators/guides/troubleshoot.mdx
rename to v1/orchestrators/guides/troubleshoot.mdx
diff --git a/orchestrators/guides/vote.mdx b/v1/orchestrators/guides/vote.mdx
similarity index 91%
rename from orchestrators/guides/vote.mdx
rename to v1/orchestrators/guides/vote.mdx
index e98ee1c0..91d2505a 100644
--- a/orchestrators/guides/vote.mdx
+++ b/v1/orchestrators/guides/vote.mdx
@@ -16,7 +16,7 @@ Follow the steps herein to access and vote with the `livepeer_cli`:
- 
+ 
@@ -24,7 +24,7 @@ Follow the steps herein to access and vote with the `livepeer_cli`:
- 
+ 
@@ -33,7 +33,7 @@ Follow the steps herein to access and vote with the `livepeer_cli`:
- 
+ 
diff --git a/v1/orchestrators/introduction.mdx b/v1/orchestrators/introduction.mdx
new file mode 100644
index 00000000..897dfbdf
--- /dev/null
+++ b/v1/orchestrators/introduction.mdx
@@ -0,0 +1,61 @@
+---
+title: "Introduction"
+description: "Explore APIs, guides, and examples"
+icon: "hand-wave"
+---
+
+
+
+
+
+
+
+
+#### Videos
+
+Use the HTML video element for self-hosted video content:
+
+
+
+Embed YouTube videos using iframe elements:
+
+
+
+#### Tooltips
+
+Example of tooltip usage:
+
+
+
+
+{/* Livepeer powers on-demand real-time video streaming and AI pipelines through a full-stack open hardware network, providing users with affordable, verifiable, permissionless enterprise-grade software solutions. */}
+## 
+
+
+
+From -> https://github.com/videoDAC/livepeer-gateway?tab=readme-ov-file
+
+They are not block producers, not orchestrators, and not on-chain components.
+They are an infrastructure role that apps connect to for low-latency coordination.
+
+### Why Gateways Exist
+
+Across the transcripts and ecosystem discussions, gateways consistently appear in one context:
+
+Gateways solve the “coordination layer” problem
+
+Orchestrators handle compute (GPU jobs).
+
+Gateways handle:
+
+- Job intake
+- Routing
+- Pricing
+- Matching workloads to the right orchestrator
+- Providing an interface for applications
+
+## Why Gateways Matter
+
+As Livepeer transitions into a high-demand, real-time AI network, Gateways become essential infrastructure. They enable:
+
+- Low-latency workflows for Daydream, ComfyStream, and other real-time AI video tools
+- Dynamic GPU routing for inference-heavy workloads
+- A decentralized marketplace of compute capabilities
+- Flexible integration via the BYOC pipeline model
+
+Gateways simplify the developer experience while preserving the decentralization, performance, and competitiveness of the Livepeer network.
+
+# Understanding Gateways
+
+Gateways are the entry point for applications into the Livepeer decentralized compute network. They provide the coordination layer that connects real-time AI and video workloads to the orchestrators who perform the GPU compute.
+
+---
+
+## What Gateways Do
+
+Gateways handle all service-level logic required to operate a scalable, low-latency AI video network:
+
+- **Job Intake**
+ They receive workloads from applications using Livepeer APIs, PyTrickle, or BYOC integrations.
+
+- **Capability & Model Matching**
+ Gateways determine which orchestrators support the required GPU, model, or pipeline.
+
+- **Routing & Scheduling**
+ They dispatch jobs to the optimal orchestrator based on performance, availability, and pricing.
+
+- **Marketplace Exposure**
+ Gateway operators can publish the services they offer, including supported models, pipelines, and pricing structures.
+
+Gateways do _not_ perform GPU compute. Instead, they focus on coordination and service routing.
+
+---
+
+## Relationship to Orchestrators
+
+Orchestrators are GPU operators who execute the actual workload—transcoding, AI inference, or BYOC containers. Gateways route jobs _to_ orchestrators, collect results, and return them to the application.
+
+**Applications → Gateway → Orchestrator → Gateway → Application**
+
+This separation allows:
+
+- Clean abstraction for developers
+- Efficient load balancing
+- Competition and specialization across operators
+- Support for a broad range of real-time AI pipelines
+
+---
+
+## Summary
+
+Gateways are the coordination and routing layer of the Livepeer ecosystem. They expose capabilities, price services, accept workloads, and dispatch them to orchestrators for GPU execution. This design enables a scalable, low-latency, AI-ready decentralized compute marketplace.
+
+### CALLOUT YOU CAN RUN A GATEWAY & EARN!
+
+.png)
+ 
+
+
+Livepeer Founder Eric Tang demonstrating the capability for real-time avatar animation from a Livestream video input. [Ref: [Introducing Livepeer Cascade](https://mirror.xyz/livepeer.eth/bCruUtv0PJWWlFxfbCMATGM_h15hUncwvyFW1A3z7Ag) - Nov 2024]
+
diff --git a/v2/pages/03_developers/ai-inference-on-livepeer/livepeer-ai/realtime-ai.mdx b/v2/pages/03_developers/ai-inference-on-livepeer/livepeer-ai/realtime-ai.mdx
new file mode 100644
index 00000000..466b5418
--- /dev/null
+++ b/v2/pages/03_developers/ai-inference-on-livepeer/livepeer-ai/realtime-ai.mdx
@@ -0,0 +1,4 @@
+
+
+# Realtime AI
+
diff --git a/v2/pages/03_developers/ai-inference-on-livepeer/livepeer-ai/using-ai-on-livepeer.mdx b/v2/pages/03_developers/ai-inference-on-livepeer/livepeer-ai/using-ai-on-livepeer.mdx
new file mode 100644
index 00000000..06df7292
--- /dev/null
+++ b/v2/pages/03_developers/ai-inference-on-livepeer/livepeer-ai/using-ai-on-livepeer.mdx
@@ -0,0 +1,4 @@
+
+
+# Using AI on Livepeer
+
diff --git a/v2/pages/03_developers/ai-inference-on-livepeer/page-2.mdx b/v2/pages/03_developers/ai-inference-on-livepeer/page-2.mdx
new file mode 100644
index 00000000..1dbccb19
--- /dev/null
+++ b/v2/pages/03_developers/ai-inference-on-livepeer/page-2.mdx
@@ -0,0 +1,2 @@
+# Page 2
+
diff --git a/v2/pages/03_developers/builder-opportunities/dev-programs.mdx b/v2/pages/03_developers/builder-opportunities/dev-programs.mdx
new file mode 100644
index 00000000..52064ace
--- /dev/null
+++ b/v2/pages/03_developers/builder-opportunities/dev-programs.mdx
@@ -0,0 +1,27 @@
+---
+title: 'Dev Programs'
+sidebarTitle: 'Dev Programs'
+---
+
+This page is intended as a guide for startup projects building on Livepeer, OSS Developers looking to contribute and community member participation pathways.
+
+
+
+ Daydream provides the tools to build with open world models and real-time AI, and the community where creatives, builders, and researchers advance the field together.
+ 
+
+ Livepeer Studio is a developer-friendly gateway and toolkit for the Livepeer decentralized video infrastructure.
+
+ Livepeer Studio offers easy-to-use APIs and dashboards for builders to add scalable, cost-efficient, and censorship-resistant live streaming and video-on-demand (VOD) features to applications.
+
+ Unlock Innovation with Livepeer Studio's Next-Generation APIs: 
+
+ The only streaming platform that combines full self-hosting capabilities with hosted processing, backed by unique features you won’t find anywhere else.
+
+ The MistServer team is on a mission to democratize video infrastructure by leveraging decentralized protocols and open source technology -> creating a streaming infrastructure that doesn't lock you in.
+
+ Run it yourself, use Frameworks' hosted services, or mix and match.
+
+ Uncloud your infrastructure.
+
+ 
+
+ Streamplace is building open-source infrastructure to bring high-quality
+ video experiences to the AT Protocol ecosystem, while preserving user
+ sovereignty and content authenticity.
+
+ 
+
+Prompt Instructions for AI Agent:
+1. Read the instructions on the page
+2. Perform the tasks on the page
+3. Verify the tasks are completed correctly
+4. Update the page with the results of the tasks
+5. Repeat for all pages in the "Run a Gateway" section
+ - Install
+ - Configure & Fund
+ - Test
+ - Connect
+ - Monitor
+
+
diff --git a/v2/pages/04_gateways/run-a-gateway/install/community-projects.mdx b/v2/pages/04_gateways/run-a-gateway/install/community-projects.mdx
new file mode 100644
index 00000000..4345f38a
--- /dev/null
+++ b/v2/pages/04_gateways/run-a-gateway/install/community-projects.mdx
@@ -0,0 +1,91 @@
+---
+title: Easy Install [DevOps & Community Projects]
+sidebarTitle: Single Click Deployment
+description: Community CICD Pipelines to make installation accessible & easy
+icon: timeline-arrow
+tag: beta
+---
+
+
+
+
+Overhauled usability in the WYSIWYG editor.
+
+**Major improvements**
+
+- Search for file names using ⌘ + P shortcut
+- Pages load 10x faster
+- Faster load times when searching for a branch
+- Page options tab to configure layout, title, & metadata for SEO
+- Floating toolbar when you highlight text
+
+**Additional fixes**
+
+- Fixed top margin for changelog components
+- Improved reliability of right click behavior
+- After clicking publish, you’ll stay on the same page instead of being brought to an empty state
+- Standardized colors in file icons
+- Improved reliability after selecting new branches several times in a row
+- Removed Diff mode
+- More consistency when creating a new folder from the dropdown
+- Fixed block quotes creating more block quotes when trying to deselect
+
+
+
+
+Translate all of your documentation with AI. [Learn more.](organize/navigation#localization)
+
+## Export docs to PDF in beta
+
+Export all of your documentation, a subdirectory, or a singe page as a PDF.
+
+## React hook support
+
+Bring interactivity to your docs. All standard React hooks are automatically available in your MDX files. [Learn more.](customize/react-components)
+
+
+
+
+Generate MCP servers so that AI applications can interact with your docs or APIs. Written content is automatically generated as an MCP server, and you can generate an MCP server from your OpenAPI spec with one click. Check out [docs on getting started with MCP.](/ai/model-context-protocol)
+
+## Improvements
+
+- Tag changelog updates so end users can filter updates
+- Sonnet-3.7 supported for AI Chat. Configure your preferred model through the dashboard
+- Change your deployment name directly in dashboard settings
+
+## Bug fixes
+
+- OG images fixed
+- Fixed icon style inconsistency for anchors without container
+- Improved styling nits for dashboard border for mobile-tablet-desktop responsiveness
+- Show code examples even when in simple mode for API playground
+- Support "command + k" shortcut for search in web editor
+- Codeblocks within callouts expand to fill the width of the callout area
+
+
+
+
+We've introduced a new `docs.json` schema as a replacement for `mint.json`, to support better multi-level versioning, easier visual comprehension, and more consistent terminology. For more information on what's changed, [check out our blog](https://mintlify.com/blog/refactoring-mint-json-into-docs-json).
+
+Upgrade from `mint.json` to `docs.json` with the following steps:
+
+1. Make sure your CLI is the latest version
+
+```bash theme={null}
+npm i mint@latest -g
+```
+
+1. In your docs repository, run
+
+```bash theme={null}
+mint upgrade
+```
+
+1. Delete your old `mint.json` file and push your changes
+
+## CI Checks
+
+Automatically lint your docs to find broken links, discover spelling and grammar issues, or enforce writing styles with your own Vale config. Learn more in our [docs](deploy/ci).
+
+## .md support for LLMs
+
+All documentation pages are now automatically available as plain Markdown files—just append `.md` to the URL. This makes it easier for LLMs to ingest individual pages from your documentation.
+
+## More Themes
+
+
+ 
+
+
+New [pre-built themes](customize/themes) to modify the look & feel of your docs. Configure via your [docs.json file](organize/settings).
+
+Now available:
+
+- Maple
+- Palm
+- Willow
+
+## Other improvements
+
+- [Guide to Technical Writing:](https://mintlify.com/guides/introduction)Best practices for writing technical documentation, including audience research, content types, and writing tips.
+- [Dropdown component](organize/navigation#dropdowns): Organize navigation with a dropdown, in addition to tabs and anchors.
+- [AI syntax fixer](https://x.com/ricardonunez_io/status/1892334887644123192): The web editor will catch if there’s a parsing error and use AI to suggest fixes.
+
+
+
+
+Make docs private by setting up authentication via JWT, OAuth, or a universal password. With this privacy, you can create an internal knowledge base or prevent competitors from seeing your docs.
+
+
+
+
+You can now ask AI to make changes to your docs, with the context of all existing documentation. Type in a prompt and the writer will propose changes by generating a pull request.
+
+## GitLab Integration Upgrade
+
+We've improved our support for syncing with GitLab, such as enabling automated updates and preview deployments. Check out our [docs on GitLab](/deploy/gitlab) to get started.
+
+## Web Editor
+
+
+ 
+
+
+We've revamped our web editor so that you can now update docs with a fully WYSIWYG experience, while syncing with markdown.
+
+Check out our [docs on getting started with Web Editor](/editor).
+
+## /llms.txt support
+
+
+ 
+
+
+All docs instances are now automatically hosted at /llms.txt and /llms-full.txt so that LLMs can easily ingest your documentation. For more information, read the [docs on the new llms.txt standard.](https://llmstxt.org)
+
+## Localization
+
+You can now localize your docs which operates similarly to versioning. Add a `locale` to a version and fixed content in Mintlify like "Was this page helpful?" will also match the locale.
+
+### Quality Improvements
+
+- Return chat & search results based on the current version that the user is reading
+- Authenticate users with OAuth, in addition to JWT or Shared Session tokens.
+
+
+
+
+## Code Line Highlighting
+
+You can now highlight lines of code in your docs to emphasize and bring attention to important parts by adding a special comment after the language identifier. Use curly braces `{}` and specify line numbers or ranges separated by commas.
+
+```javascript Line Highlighting Example {1,3,4,5} theme={null}
+const greeting = 'Hello, World!'
+function sayHello() {
+ console.log(greeting)
+}
+sayHello()
+```
+
+````mdx theme={null}
+```javascript Line Highlighting Example {1,3-5}
+const greeting = 'Hello, World!'
+function sayHello() {
+ console.log(greeting)
+}
+sayHello()
+```
+````
+
+## Light mode code blocks
+
+Code blocks now have a light mode variant which can be enabled by adding the following to your `docs.json`:
+
+```json theme={null}
+"codeBlock": {
+ "mode": "auto"
+}
+```
+
+## Advanced Footer
+
+
+ 
+
+
+You can now add more links to the standard footer. This upgrade provides more consistency between landing pages and docs, or greater customization if you want to spotlight specific pages like socials or status logs.
+
+## Filter search based on the current user
+
+When personalization is enabled, search results are now filtered based on the current logged in user so that they only see the relevant content.
+
+## Custom Prompts for AI Chat
+
+You can now customize the prompts for the AI chat. Please reach out to [support](mailto:support@mintlify.com) if you'd like to customize the prompts.
+
+## Dashboard Improvements
+
+- Added ability to change custom domain to be /docs directly through dashboard settings.
+- Consolidated the login and signup pages to decrease friction and confusion.
+- Implemented the discovery login flow so that users that are members of multiple organizations can now switch between them.
+- Added login with Google OAuth
+- Added ability to add new deployment through dashboard settings.
+
+## Bug Fixes
+
+- Can now use leading slashes in navigation.
+- Can now edit CSS & JS files in the web editor.
+- Fixed `suggestEdit` not showing up even when enabled.
+- Fixed keyboard navigation for Search and Chat such that you can now use the up and down arrow keys to navigate the results.
+- Don't allow search engines to crawl user-auth protected pages.
+- Revalidate the cache when an org is deleted.
+- We now use the Scalar OpenAPI parser to parse OpenAPI definitions which improves the performance, fixes parsing issues, and surfaces better error messages.
+- Top-level descriptions are now supported in API reference pages autogenerated from OpenAPI definitions.
+- Add in-line-style support for icons
+- Fixed the pop-in of custom CSS in docs.
+- Properly show in-line code styling in conjunction with links.
+- Maintain scroll position when you click the back button in a browser.
+
+
+
+
+Personalize the font of your docs to your own font hosted on a CDN or by choosing from Google fonts to match your docs with your brand.
+
+## Images in Card components
+
+Add an `img` property to a card to display an image on the top of the card. Learn more about it [here](/components/cards#image-card).
+
+## Update Speed Performances
+
+
+ 
+
+
+For large projects (\~3,000 files), the download step for docs updates is now \~440x faster - a 99.8% time reduction. Across the board, file downloads during updates are now \~5.5x faster - an 81.8% time reduction.
+
+## SEO improvements
+
+
+ 
+
+
+We've fixed both the mobile and desktop layout of our docs so that they are more SEO-friendly - including adding proper aria tags to navbar and toggle elements.
+
+## Dashboard Improvements
+
+- App router migration in the dashboard.
+- Search analytics are now available in the dashboard.
+- Delete an org functionality has been added to the dashboard.
+- Shipped GitLab connection UI.
+- Fix incorrect analytics data.
+- Add-on's can now be directly purchased through the dashboard.
+
+## Bug Fixes
+
+- Fixed a bug where the top bar would not stretch to the width of the screen when it's in custom mode and the sidebar layout is `sidenav`.
+- Fix relative positioning of the AI widget.
+
+## More
+
+- **Troubleshooting for API pages**: API pages could be complicated so we listed common issues to help you sort them out quickly — [Read the docs](/api-playground/troubleshooting)
+
+
+
+
+For `Pro` users, we introduced Mintlify Widget, an extension of your docs to answer your users' questions when and where they asked. You can add this AI-powered chatbot to any web page: your landing page, inside your product, or on your existing documentation pages.
+
+- [Read the blog announcement](https://mintlify.com/blog/widget)
+
+## Pro Plan
+
+We also updated our pricing plans for better customizability and scale.
+
+- [Read the blog announcement](https://mintlify.com/blog/pro-plan)
+
+## API Playground Code Example Sync
+
+When you browse API docs, the selected code example now syncs across your pages.
+
+## Insights
+
+Currently in beta, this feature summarizes common user questions and patterns into easy-to-digest reports with AI-powered suggestions on how to improve your product.
+
+
+ 
+ 
+ 
+ 
+ 
+ 
+
+