Livepeer Python API Docs | dltHub

Build a Livepeer-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

Livepeer's Text To Image API generates images from text prompts. The Image To Video API creates videos from images. Both use POST requests to respective endpoints. The REST API base URL is https://dream-gateway.livepeer.cloud (public playground gateway, not production), and Livepeer Studio production gateway: https://livepeer.studio/api/beta/generate and all requests require a Bearer token in the Authorization header..

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Livepeer data in under 10 minutes.


What data can I load from Livepeer?

Here are some of the endpoints you can load from Livepeer:

ResourceEndpointMethodData selectorDescription
text_to_image/text-to-imagePOSTimagesGenerate images from text prompts
image_to_image/image-to-imagePOSTimagesTransform a provided image
image_to_video/image-to-videoPOST(response returns video URL or job object)Generate a video from an image (gateway-dependent)
image_to_text/image-to-textPOST(response fields per model)Extract text from image (AI API)
audio_to_text/audio-to-textPOST(response fields)Transcribe audio
llm/llmPOST(response fields)Language model endpoint
upscale/upscalePOSTimagesUpscale images

How do I authenticate with the Livepeer API?

Use an HTTP Bearer token in the Authorization header: Authorization: Bearer . For the public dream gateway, no token is required for playground use but production Livepeer Studio gateway requires an API token.

1. Get your credentials

  1. Sign in or sign up at Livepeer Studio (https://livepeer.studio/) 2) In the dashboard navigate to API keys / Tokens (or Project settings → API Keys) 3) Create a new API token with appropriate scopes for AI/generate and copy the token. 4) Store token in secrets.toml and pass to dlt source via parameter token.

2. Add them to .dlt/secrets.toml

[sources.livepeer_source] token = "your_livepeer_token_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Livepeer API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

python livepeer_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline livepeer_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset livepeer_data The duckdb destination used duckdb:/livepeer.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline livepeer_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads text_to_image and image_to_video from the Livepeer API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def livepeer_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://dream-gateway.livepeer.cloud (public playground gateway, not production), and Livepeer Studio production gateway: https://livepeer.studio/api/beta/generate", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "text_to_image", "endpoint": {"path": "text-to-image", "data_selector": "images"}}, {"name": "image_to_video", "endpoint": {"path": "image-to-video", "data_selector": "(response contains video URL or job object; no top-level array)"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="livepeer_pipeline", destination="duckdb", dataset_name="livepeer_data", ) load_info = pipeline.run(livepeer_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("livepeer_pipeline").dataset() sessions_df = data.text_to_image.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM livepeer_data.text_to_image LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("livepeer_pipeline").dataset() data.text_to_image.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Livepeer data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for Livepeer?

Request dlt skills, commands, AGENT.md files, and AI-native context.