NVIDIA cuOpt Python API Docs | dltHub

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

Last updated:

NVIDIA cuOpt is an accelerated optimization service for complex, real-time fleet routing workflows. The REST API base URL is https://api.nvcf.nvidia.com/v2/nvcf 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 add "dlt[hub]" and start loading NVIDIA cuOpt data in under 10 minutes.


What data can I load from NVIDIA cuOpt?

Here are some of the endpoints you can load from NVIDIA cuOpt:

ResourceEndpointMethodData selectorDescription
cuopt_health/cuopt/healthGETCheck health status of cuOpt server
cuopt_request/cuopt/request/{id}GETCheck status of a specific request
cuopt_solution/cuopt/solution/{id}GETRetrieve result for a specific request ID
cuopt_incumbents/cuopt/solution/{id}/incumbentsGETGet incumbent solutions for MIP
cuopt_log/cuopt/log/{id}GETQuery solver logs by request ID

How do I authenticate with the NVIDIA cuOpt API?

Authentication requires a JWT (Bearer token) passed in the 'Authorization' header. The token is obtained by authenticating with NVIDIA Identity Federation using Client ID and Secret or SAK credentials.

1. Get your credentials

To obtain credentials for the NVIDIA cuOpt managed service: 1. Log in to the NVIDIA NGC portal. 2. Navigate to the NGC Catalog dropdown and select Cloud Functions. 3. Within the interface (specifically under the Cloud Function tab/menu), locate the section for API Keys. 4. Generate a Personal API Key (often referred to as an NVIDIA Identity Federation API Key or SAK). 5. Save the key securely, as it is used to authenticate requests to the service. Note that legacy methods involving Client ID and Client Secret are now deprecated in favor of this API Key (SAK).

2. Add them to .dlt/secrets.toml

[sources.nvidia_cuopt_source] CUOPT_CLIENT_SAK = "your_personal_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 init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub 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:

uv run dlthub ai toolkit install rest-api-pipeline

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 NVIDIA cuOpt 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:

uv run python nvidia_cuopt_pipeline.py

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

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

Inspect your pipeline and data:

uv run dlthub 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 /v2/nvcf/functions and /v2/nvcf/assets from the NVIDIA cuOpt 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 nvidia_cuopt_source(client_secret=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.nvcf.nvidia.com/v2/nvcf", "auth": {"type": "bearer", "token": client_secret}, }, "resources": [ {"name": "cuopt_request", "endpoint": {"path": "cuopt/request/{id}"}}, {"name": "cuopt_solution", "endpoint": {"path": "cuopt/solution/{id}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="nvidia_cuopt_pipeline", destination="duckdb", dataset_name="nvidia_cuopt_data", ) load_info = pipeline.run(nvidia_cuopt_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("nvidia_cuopt_pipeline").dataset() sessions_df = data.cuopt_request.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM nvidia_cuopt_data.cuopt_request LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("nvidia_cuopt_pipeline").dataset() data.cuopt_request.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 NVIDIA cuOpt 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 harness:

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

Was this page helpful?

Community Hub

Need more dlt context for NVIDIA cuOpt?

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

Available Pipelines