Basis Set Exchange Python API Docs | dltHub
Build a Basis Set Exchange-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
The Basis Set Exchange REST API documentation provides access to a public API for retrieving basis set information, currently in beta. The API allows users to fetch metadata, formats, references, and notes for various basis sets. The API is documented on GitHub Pages. The REST API base URL is https://www.basissetexchange.org and No authentication required; optional User-Agent and email headers may be included..
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 Basis Set Exchange data in under 10 minutes.
What data can I load from Basis Set Exchange?
Here are some of the endpoints you can load from Basis Set Exchange:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| metadata | /api/metadata | GET | Returns JSON representing the metadata about the basis sets contained in the BSE. | |
| formats | /api/formats | GET | Returns JSON representing which basis set formats are available. | |
| reference_formats | /api/reference_formats | GET | Provides information about which reference formats are supported. | |
| basis | /api/basis/<basis_name>/format/ | GET | Obtain basis set data; output is a string unless is json. | |
| references | /api/references/<basis_name>/format/ | GET | reference_info | Obtain references; JSON responses include 'reference_info' list. |
How do I authenticate with the Basis Set Exchange API?
Requests do not require authentication. You may include optional headers such as User-Agent or an email address for contact purposes.
1. Get your credentials
No credentials are needed to access the Basis Set Exchange public REST API.
2. Add them to .dlt/secrets.toml
[sources.basis_set_exchange_source]
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 Basis Set Exchange 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 basis_set_exchange_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline basis_set_exchange_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset basis_set_exchange_data The duckdb destination used duckdb:/basis_set_exchange.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline basis_set_exchange_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 metadata and formats from the Basis Set Exchange 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 basis_set_exchange_source(=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://www.basissetexchange.org", "auth": { "type": "none", "": , }, }, "resources": [ {"name": "metadata", "endpoint": {"path": "api/metadata"}}, {"name": "formats", "endpoint": {"path": "api/formats"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="basis_set_exchange_pipeline", destination="duckdb", dataset_name="basis_set_exchange_data", ) load_info = pipeline.run(basis_set_exchange_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("basis_set_exchange_pipeline").dataset() sessions_df = data.metadata.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM basis_set_exchange_data.metadata LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("basis_set_exchange_pipeline").dataset() data.metadata.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 Basis Set Exchange 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 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 Basis Set Exchange?
Request dlt skills, commands, AGENT.md files, and AI-native context.