baseten-bdn
Python SDK for working with BDN inside and outside Baseten.
This package is under initial development. It installs as baseten-bdn and
imports as baseten.bdn. The baseten package is a namespace shared with
other Baseten SDKs such as baseten and baseten-loops.
Installation
pip install baseten-bdn
Hot Load
Inside a model pod that is opted in to BDN Hot Load, baseten.bdn.hotload
attaches BDN volumes below /bdn/mounts at runtime. An attach returns once the
directory is readable.
from baseten.bdn.hotload import HotLoadClient
with HotLoadClient() as hotload:
adapter = hotload.attach("bdn:adapters/sql-lora@b3:2547…", target="sql-lora")
load_adapter(adapter.path) # /bdn/mounts/sql-lora
AsyncHotLoadClient offers the same methods as coroutines. Attachments belong
to the pod and stay mounted after the client is closed; call detach to free a
target name for reuse.
Volumes
From any machine with a Baseten API key, baseten.bdn.volumes reads a volume
version's manifest or pulls a version into a local directory. The client mints a short-lived token through the Baseten API,
resolves the ref, and reads the volume's objects directly from storage with
the credentials it is given, verifying every object against its recorded
digest.
from baseten.bdn.volumes import VolumeClient
with VolumeClient(api_key="...") as volumes:
result = volumes.pull("bdn:loops/sampler-abc123:step-100", "./checkpoint")
print(result.version_ref, result.file_count, result.bytes_written)
Refs are bdn:<namespace>/<volume> with an optional :<tag> or @<digest>
selector and an optional /path inside the version; VolumeRef parses and
renders them. A path on the ref, or include=[...], narrows a pull to those
entries without moving them. A pull is staged next to dest_dir and renamed
into place once complete, so a failed pull leaves nothing behind; pass
overwrite=True to write into an existing directory in place. Pulling is
supported on Linux and macOS.
Development
Requires uv.
uv sync
uv run poe lint
uv run poe typecheck
uv run poe test
Run uv run poe format to apply formatting and lint fixes.
License
MIT. See LICENSE.
Metadata
Release files for baseten-bdn 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| baseten_bdn-0.1.0.tar.gz | 82.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| baseten_bdn-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 119.5 kB
Release files / baseten_bdn-0.1.0.tar.gz
| Download URL | baseten_bdn-0.1.0.tar.gz |
|---|---|
| Size | 82.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d98a20bc5a74e118805a49d6e6574163493d3f52d449eefb12e1d70e2bb8144a
|
|
BLAKE2b-256 checksum How to use checksums |
f52a1a6d625445366065c6b9bce1be632f5f27aa72a23cd1b4f3c9001ca328de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / baseten_bdn-0.1.0-py3-none-any.whl
| Download URL | baseten_bdn-0.1.0-py3-none-any.whl |
|---|---|
| Size | 37.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ccd809f78ec82494ca7239a3086dde52ba70f3788e50592d9fe65ebb33a6f1d3
|
|
BLAKE2b-256 checksum How to use checksums |
0c5c616e5cdd7b7383c9affd93566a1c40533e9fb1805e1107d4d750a4e79c80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency log