DOXA CLI
The DOXA CLI is the primary tool for uploading and submitting agents to DOXA: a powerful platform for hosting engaging artificial intelligence competitions.
🔗 Compete on DOXA
➡️ Join the DOXA Community on Discord
Installation
The DOXA CLI may be installed using pip in the following way:
pip install doxa-cli
Using the DOXA CLI
Assuming you have your Python Scripts folder on your PATH, you can use the DOXA CLI via the doxa command in your shell. Otherwise, you will have to use python -m doxa_cli (or python3 -m doxa_cli on some systems) to access DOXA CLI commands.
Logging into the CLI with your DOXA account
Before you can upload agents to DOXA using the CLI, you must first log in with your DOXA account by running the following command:
doxa login
If supported, this will open an authorisation prompt in your default browser. If you are not already logged in on doxaai.com, you will first be invited to do so. Thereafter, you wil be asked to authorise the DOXA CLI to have access to your DOXA account. Once you signify your approval, the DOXA CLI will automatically log you in within a few seconds.
By default, the DOXA CLI will store its configuration in a location that follows the norm for your operating system (e.g. within %APPDATA%\doxa\doxa on Windows, ~/Library/Application Support/doxa on macOS and ~/.config/doxa on Linux). You can find this location by running doxa config. If for whatever reason you would like to store the DOXA CLI configuration elsewhere (e.g. due to a permissions issue), you may use a different directory by setting the DOXA_CONFIG_DIRECTORY environment variable.
Logging out
You may log out by running the following command:
doxa logout
Retrieving user information
You can retrieve information on the user account with which you are currently logged in by performing the following command:
doxa user
Uploading agents to DOXA
You may upload and submit agents to DOXA using the following command:
doxa upload [AGENT DIRECTORY]
The agent directory must contain a doxa.yaml file informing DOXA how to process your submission.
The following is an example of the contents of one such doxa.yaml file:
competition: uttt
environment: cpu
language: python
entrypoint: evaluate.py
Metadata
Release files for doxa-cli 0.1.8
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 | |
|---|---|---|---|---|
| doxa_cli-0.1.8.tar.gz | 14.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| doxa_cli-0.1.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 31.0 kB
Release files / doxa_cli-0.1.8.tar.gz
| Download URL | doxa_cli-0.1.8.tar.gz |
|---|---|
| Size | 14.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
779594e63180d936e679a050e96171ddce9b00733d4b218fb01d211ebde4ab74
|
|
BLAKE2b-256 checksum How to use checksums |
ed91634e908b1da4ce44e9d0f89b18efd9b6709d9b5da1ac586bf6d5187e39db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.4
|
Release files / doxa_cli-0.1.8-py3-none-any.whl
| Download URL | doxa_cli-0.1.8-py3-none-any.whl |
|---|---|
| Size | 16.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a6d9ac16839637219596f7eea23e4f328d3b0ba4cd166881ca6d03d8790d291e
|
|
BLAKE2b-256 checksum How to use checksums |
39464a9ad8fb25b4844fc6195292c10eee948f57df3abb355da27a8f8c3d71f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.4
|
Security for doxa-cli 0.1.8
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.