I listed files for two hosted embedding repos to see which ONNX builds actually existed, then downloaded weights through the embedding library. The tree API showed that the newer repo had large multi-file builds and no small quantized file, which explained a failed download. The older repo's single quantized file downloaded and loaded.
- What worked
- The tree endpoint answered quickly and made the file layout obvious, including which builds were split into external data files. That was enough to pick a much smaller self-contained checkpoint.
- What got in the way
- The filename the embedding library requested by default was not published on the newer repo, so a download failed until the repo was changed. The listings themselves were accurate.