JsDelivr Python API Docs | dltHub
Build a JsDelivr-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
jsDelivr is a public API providing information on npm packages, files, versions, and CDN usage statistics. The REST API base URL is https://data.jsdelivr.com/v1 and no authentication required.
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 JsDelivr data in under 10 minutes.
What data can I load from JsDelivr?
Here are some of the endpoints you can load from JsDelivr:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| packages | /v1/packages | GET | List packages | |
| package_npm | /v1/package/npm/{package} | GET | versions | Package metadata for npm |
| package_gh | /v1/package/gh/{user}/{repo} | GET | versions | Package metadata for GitHub |
| files | /v1/files/npm/{package}/{version} | GET | files | File tree for package version |
| stats_periods | /v1/stats/periods | GET | List available stats periods |
How do I authenticate with the JsDelivr API?
The jsDelivr API is a public service that does not require any authentication, API keys, or tokens.
No credentials required. The JsDelivr API is public, so there is nothing to obtain and nothing to add to .dlt/secrets.toml — the pipeline above runs as written.
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 JsDelivr 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 jsdelivr_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline jsdelivr_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset jsdelivr_data The duckdb destination used duckdb:/jsdelivr.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 /v1/package/npm/{package} and /v1/files/npm/{package}/{version} from the JsDelivr 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 jsdelivr_source(): config: RESTAPIConfig = { "client": { "base_url": "https://data.jsdelivr.com/v1", }, "resources": [ {"name": "package_npm", "endpoint": {"path": "package/npm/{package}", "data_selector": "versions"}}, {"name": "files", "endpoint": {"path": "files/npm/{package}/{version}", "data_selector": "files"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="jsdelivr_pipeline", destination="duckdb", dataset_name="jsdelivr_data", ) load_info = pipeline.run(jsdelivr_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("jsdelivr_pipeline").dataset() sessions_df = data.package_npm.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM jsdelivr_data.package_npm LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("jsdelivr_pipeline").dataset() data.package_npm.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 JsDelivr data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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 JsDelivr?
Request dlt skills, commands, AGENT.md files, and AI-native context.