One stable contract over an evolving builder
Dataset API separates customer integrations from the Python dataset_builder implementation. Consumers use a versioned HTTPS contract while collectors, normalizers, and validation logic can evolve behind the adapter.
The public workflow is intentionally small: discover a dataset, inspect or create a build, select an immutable release, then query bounded rows or download the release artifact.
Resource map
| Resource | Purpose | Mutability |
|---|---|---|
| Dataset | Catalog definition, fields, identity, and latest release | Definition may gain compatible fields |
| Build | Asynchronous builder job | Status changes until terminal |
| Release | Quality-checked published snapshot | Immutable |
| Query response | Bounded projection from one release | Read-only |
| Download | Full release artifact | Read-only |
The release is the unit of trust
A release identifies its dataset and schema versions, quality status, counts, optional parent release, artifacts, and immutable flag. Persist the release ID with every downstream import so results remain reproducible.
First managed catalog
The preview catalog contains Finnish vehicle market listings. The narrow starting point makes schema evolution, source coverage, carried-forward rows, and release lineage concrete before additional catalogs are introduced.