olympicducks
Submit a MicroDuck policy to OlympicDucks straight
from a training run, and manage it from a terminal after — list, download or
retire it. retire is the one thing this CLI can do that the browser can't
(there's no delete button there yet); everything else mirrors the web app.
The CLI holds nothing but a token.
pipx run olympicducks submit output.onnx --name "shover"
or install it once with pipx:
pipx install olympicducks
olympicducks submit output.onnx --name "shover"
Usage
Get a personal token from olympicducks.com/settings (shown once — copy it before you leave), then either:
olympicducks login <token> # stored in ~/.config/olympicducks/config.json
or set OLYMPICDUCKS_TOKEN in the environment — handy for CI and training jobs.
olympicducks submit output.onnx --name "shover" --game sumo
olympicducks submit output.onnx --name "shover" --wait
--wait polls until validation finishes and prints why a policy was rejected,
if it was. Without it, submit returns as soon as the upload is queued.
--moves key=path is accepted but currently does nothing: the extra policies
are uploaded and the server keeps only the gait, so the entry runs without
them and reports success anyway. Don't rely on it until D69's open question —
what a move costs against an account's storage quota — is settled.
olympicducks list # your ducks, entries and their status
olympicducks download shover # saves shover.onnx
olympicducks download shover -o weights.onnx
olympicducks retire shover # off the ladder; weights and match history kept
download only works for a valid or retired version — one still
validating or rejected has nothing to fetch yet. retire is refused while
the duck has a climb in progress; wait for it to finish first.
Metadata
Release files for olympicducks 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| olympicducks-0.0.1.tar.gz | 5.6 kB | With provenance | Details for olympicducks-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| olympicducks-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for olympicducks-0.0.1-py3-none-any.whl |
Total release size: 11.4 kB
Release files / olympicducks-0.0.1.tar.gz
| Download URL | olympicducks-0.0.1.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
acb20b1d96a8b72d27a82984e9d67de00ab1a870ab3301f5fca7fb5789968159
|
|
BLAKE2b-256 checksum How to use checksums |
196af6da974a06ee057dfb589e88c40b7531b18259a614a91d57157bf7bfbfdc
|
| 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 Aug 31, 2026.
Transparency logRelease files / olympicducks-0.0.1-py3-none-any.whl
| Download URL | olympicducks-0.0.1-py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b849e470bca28a82edbdcb9d33fbc2637fca5475ed31ee0a08c200706ab090d2
|
|
BLAKE2b-256 checksum How to use checksums |
a2814b8c6bb28b50b171b807112cb98dfd172be6a02553b59e01ad262ed00298
|
| 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 Aug 31, 2026.
Transparency logSecurity for olympicducks 0.0.1
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for olympicducks-0.0.1.tar.gz
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 Aug 31, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.