refactor: improve pipeline formatting

livepeer · Nov 18, 2024 · 9524deb · 9524deb
1 parent a4a3cfd
commit 9524deb
Show file tree

Hide file tree

Showing 6 changed files with 71 additions and 54 deletions.
diff --git a/ai/pipelines/audio-to-text.mdx b/ai/pipelines/audio-to-text.mdx
@@ -109,15 +109,18 @@ The following system requirements are recommended for optimal performance:
 
 ## Recommended Pipeline Pricing
 
-<Note>We are planning to simplify the pricing in the future so orchestrators can set
-one AI price per compute unit and have the system automatically scale based on the
-model's compute requirements.</Note>
-
-The pricing for the `audio-to-text` pipeline is based on competitor pricing. However,
-we strongly encourage orchestrators to set their own pricing based on their costs and
-requirements. Setting a competitive price will help attract more jobs, as Gateways can
-set their maximum price for a job. The currently recommended pricing for this pipeline
-is `0.02e-6 USD` per **milliseconds** of audio input.
+<Note>
+  We are planning to simplify the pricing in the future so orchestrators can set
+  one AI price per compute unit and have the system automatically scale based on
+  the model's compute requirements.
+</Note>
+
+The pricing for the `audio-to-text` pipeline is based on competitor pricing.
+However, we strongly encourage orchestrators to set their own pricing based on
+their costs and requirements. Setting a competitive price will help attract more
+jobs, as Gateways can set their maximum price for a job. The currently
+recommended pricing for this pipeline is `0.02e-6 USD` per **milliseconds** of
+audio input.
 
 ## API Reference
 

diff --git a/ai/pipelines/image-to-image.mdx b/ai/pipelines/image-to-image.mdx
@@ -143,15 +143,18 @@ The following system requirements are recommended for optimal performance:
 
 ## Recommended Pipeline Pricing
 
-<Note>We are planning to simplify the pricing in the future so orchestrators can set 
-one AI price per compute unit and have the system automatically scale based on the 
-model's compute requirements.</Note>
-
-The pricing for the `image-to-image` pipeline is based on competitor pricing. However, 
-we strongly encourage orchestrators to set their own pricing based on their costs and 
-requirements. Setting a competitive price will help attract more jobs, as Gateways can 
-set their maximum price for a job. The current recommended pricing for this pipeline 
-is `1.9073484e-08 USD` per **input pixel** (`height * width * output_images`)
+<Note>
+  We are planning to simplify the pricing in the future so orchestrators can set
+  one AI price per compute unit and have the system automatically scale based on
+  the model's compute requirements.
+</Note>
+
+The pricing for the `image-to-image` pipeline is based on competitor pricing.
+However, we strongly encourage orchestrators to set their own pricing based on
+their costs and requirements. Setting a competitive price will help attract more
+jobs, as Gateways can set their maximum price for a job. The current recommended
+pricing for this pipeline is `1.9073484e-08 USD` per **input pixel**
+(`height * width * output_images`).
 
 ## API Reference
 

diff --git a/ai/pipelines/image-to-video.mdx b/ai/pipelines/image-to-video.mdx
@@ -128,15 +128,18 @@ The following system requirements are recommended for optimal performance:
 
 ## Recommended Pipeline Pricing
 
-<Note>We are planning to simplify the pricing in the future so orchestrators can set 
-one AI price per compute unit and have the system automatically scale based on the 
-model's compute requirements.</Note>
-
-The pricing for the `image-to-video` pipeline is based on competitor pricing. However, 
-we strongly encourage orchestrators to set their own pricing based on their costs and 
-requirements. Setting a competitive price will help attract more jobs, as Gateways can 
-set their maximum price for a job. The current recommended pricing for this pipeline 
-is  `1.3563368e-08 USD` per **output pixel** (`height * width * frames`).
+<Note>
+  We are planning to simplify the pricing in the future so orchestrators can set
+  one AI price per compute unit and have the system automatically scale based on
+  the model's compute requirements.
+</Note>
+
+The pricing for the `image-to-video` pipeline is based on competitor pricing.
+However, we strongly encourage orchestrators to set their own pricing based on
+their costs and requirements. Setting a competitive price will help attract more
+jobs, as Gateways can set their maximum price for a job. The current recommended
+pricing for this pipeline is `1.3563368e-08 USD` per **output pixel**
+(`height * width * frames`).
 
 ## API Reference
 

diff --git a/ai/pipelines/segment-anything-2.mdx b/ai/pipelines/segment-anything-2.mdx
@@ -106,15 +106,18 @@ The following system requirements are recommended for optimal performance:
 
 ## Recommended Pipeline Pricing
 
-<Note>We are planning to simplify the pricing in the future so orchestrators can set 
-one AI price per compute unit and have the system automatically scale based on the 
-model's compute requirements.</Note>
-
-The pricing for the `segment-anything-2` pipeline is based on competitor pricing. However, 
-we strongly encourage orchestrators to set their own pricing based on their costs and 
-requirements. Setting a competitive price will help attract more jobs, as Gateways can 
-set their maximum price for a job. The current recommended pricing for this pipeline 
-is `3.22e-11 USD` per **input pixel** (`height * width`).
+<Note>
+  We are planning to simplify the pricing in the future so orchestrators can set
+  one AI price per compute unit and have the system automatically scale based on
+  the model's compute requirements.
+</Note>
+
+The pricing for the `segment-anything-2` pipeline is based on competitor
+pricing. However, we strongly encourage orchestrators to set their own pricing
+based on their costs and requirements. Setting a competitive price will help
+attract more jobs, as Gateways can set their maximum price for a job. The
+current recommended pricing for this pipeline is `3.22e-11 USD` per **input
+pixel** (`height * width`).
 
 ### Pipeline-Specific Image
 

diff --git a/ai/pipelines/text-to-speech.mdx b/ai/pipelines/text-to-speech.mdx
@@ -85,15 +85,17 @@ The following system requirements are recommended for optimal performance:
 
 ## Recommended Pipeline Pricing
 
-<Note>We are planning to simplify the pricing in the future so orchestrators can set 
-one AI price per compute unit and have the system automatically scale based on the 
-model's compute requirements.</Note>
-
-The pricing for the `text-to-speech` pipeline is based on competitor pricing. However, 
-we strongly encourage orchestrators to set their own pricing based on their costs and 
-requirements. Setting a competitive price will help attract more jobs, as Gateways can 
-set their maximum price for a job. The current recommended pricing for this pipeline 
-is `1.5e-6 USD` per **character**.
+<Note>
+  We are planning to simplify the pricing in the future so orchestrators can set
+  one AI price per compute unit and have the system automatically scale based on
+  the model's compute requirements.
+</Note>
+
+The pricing for the `text-to-speech` pipeline is based on competitor pricing.
+However, we strongly encourage orchestrators to set their own pricing based on
+their costs and requirements. Setting a competitive price will help attract more
+jobs, as Gateways can set their maximum price for a job. The current recommended
+pricing for this pipeline is `1.5e-6 USD` per **character**.
 
 ### Pipeline-Specific Image
 

diff --git a/ai/pipelines/upscale.mdx b/ai/pipelines/upscale.mdx
@@ -123,15 +123,18 @@ The following system requirements are recommended for optimal performance:
 
 ## Recommended Pipeline Pricing
 
-<Note>We are planning to simplify the pricing in the future so orchestrators can set 
-one AI price per compute unit and have the system automatically scale based on the 
-model's compute requirements.</Note>
-
-The pricing for the `upscale` pipeline is based on competitor pricing. However, 
-we strongly encourage orchestrators to set their own pricing based on their costs and 
-requirements. Setting a competitive price will help attract more jobs, as Gateways can 
-set their maximum price for a job. The current recommended pricing for this pipeline 
-is `1.9073484e-08 USD` per **input pixel** (`height * width`).
+<Note>
+  We are planning to simplify the pricing in the future so orchestrators can set
+  one AI price per compute unit and have the system automatically scale based on
+  the model's compute requirements.
+</Note>
+
+The pricing for the `upscale` pipeline is based on competitor pricing. However,
+we strongly encourage orchestrators to set their own pricing based on their
+costs and requirements. Setting a competitive price will help attract more jobs,
+as Gateways can set their maximum price for a job. The current recommended
+pricing for this pipeline is `1.9073484e-08 USD` per **input pixel**
+(`height * width`).
 
 ## API Reference