GPUStack Python API Docs | dltHub

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

Last updated:

GPUStack is a platform that offers GPU resource management together with OpenAI‑compatible REST APIs for AI workloads. The REST API base URL is http://your_gpustack_server_url and All requests require a Bearer token containing the GPUStack API key..

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 GPUStack data in under 10 minutes.


What data can I load from GPUStack?

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

ResourceEndpointMethodData selectorDescription
models/v1/modelsGETdataList all available models (OpenAI‑compatible)
model_detail/v1/models/{model_id}GETRetrieve details of a specific model
deployments/v1/deploymentsGETdataList deployment objects managed by GPUStack
pods/v1/podsGETdataList GPU pod resources
usage/v1/usageGETdataRetrieve usage and token metrics for the account

How do I authenticate with the GPUStack API?

Authentication is performed by sending the API key as a Bearer token in the Authorization header of each request.

1. Get your credentials

  1. Open the GPUStack web dashboard and sign in with administrative credentials.
  2. In the navigation menu choose User & API Key Management.
  3. Click Create API Key (or select an existing key) and give it a descriptive name.
  4. Copy the generated key; it will be shown only once.
  5. Store the key securely and use it as the Bearer token in your requests.

2. Add them to .dlt/secrets.toml

[sources.gpu_stack_source] api_key = "your_api_key_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 GPUStack 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 gpu_stack_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline gpu_stack_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 models and deployments from the GPUStack 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 gpu_stack_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://your_gpustack_server_url", "auth": { "type": "bearer", "token": api_key, }, }, "resources": [ {"name": "models", "endpoint": {"path": "v1/models", "data_selector": "data"}}, {"name": "deployments", "endpoint": {"path": "v1/deployments", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="gpu_stack_pipeline", destination="duckdb", dataset_name="gpu_stack_data", ) load_info = pipeline.run(gpu_stack_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("gpu_stack_pipeline").dataset() sessions_df = data.models.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM gpu_stack_data.models LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("gpu_stack_pipeline").dataset() data.models.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 GPUStack 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.


Troubleshooting

Authentication errors

  • 401 Unauthorized – occurs when the Authorization header is missing, malformed, or contains an invalid API key.

Rate limiting

  • 429 Too Many Requests – the API enforces per‑minute request quotas; back‑off and retry after the Retry-After header.

Pagination

  • List endpoints paginate results using limit and offset (or page and page_size) query parameters; include these parameters to retrieve subsequent pages.

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.


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 GPUStack?

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