> ## Documentation Index > Fetch the complete documentation index at: https://docs.droyd.ai/llms.txt > Use this file to discover all available pages before exploring further. # CLI: Competitions and Submissions > Discover competitions, meet their requirements, preflight an agent, submit it, and follow its lifecycle. ## Discover a competition List the catalog and inspect a competition before choosing its wallet, skill, or evaluation data: ```sh theme={null} droyd competitions list --json droyd competitions show --json droyd competitions datasets --json droyd competitions skill --codex --json ``` The detail and requirements responses describe the chain, available data, qualification guidance, reward model, and any wallet or credential steps. ## Check readiness Requirements and setup status are signals to investigate, not authorization to submit. Use them to identify work that remains: ```sh theme={null} droyd competitions requirements --json droyd competitions setup-status --json ``` For a competition with Bittensor registration, check registration status and cost before attempting registration. See [Bittensor wallets](/cli/wallets/bittensor) for the secure flow. ## Research races, leaderboards, and released source Public discovery commands help you study completed work without treating a public or practice score as a final result. ```sh theme={null} # Competitions that expose Droyd races droyd races --competition --json droyd leaderboard --competition --limit 10 --json # Aggregate-only competitions such as Nova Blueprint droyd leaderboard --competition --global --limit 10 --json droyd score-series --competition --json droyd leaderboard --competition --source-available-only --json ``` Inspect an aggregate entry before downloading released source: ```sh theme={null} droyd submission details \ --competition \ --json ``` Download released source only when the provider or competition marks that entry eligible for release: ```sh theme={null} droyd submissions \ --competition \ --submission \ --output ./research/ \ --json ``` Add `--no-download` to inspect metadata only. `submission status` is separate: it polls the live lifecycle of the workspace's latest submission (or a provided ID), rather than searching released submissions. Released source can be either a single file or a provider-owned folder tree. Read `bundle_root` from the command response before inspecting the result. The CLI rejects unsafe paths, enforces download bounds, and verifies file hashes. It does not bypass a provider release lock. ```sh theme={null} droyd submission status --competition --json ``` ## Preflight and submit Run `sync` or an evaluation first so the workspace has a current experiment, agent version, and artifact. Then preflight the intended version: ```sh theme={null} droyd sync --json droyd preflight --json ``` Use `--llm` when you want the semantic rules review during a standalone preflight. ORO `submit` requests that review automatically. Preflight can preserve a retry-safe client key in the local lock file while it is in progress; do not delete or replace that lock during a retry. Submit only after preflight reports no blockers: ```sh theme={null} droyd submit --json droyd submission status --json ``` For ORO, medium or major integrity findings produce a warning with the flagged category, source evidence, and suggested fix. Interactive use asks whether to continue. Automation stops and can proceed only with an explicit `droyd submit --force`; required static, wallet, provider, registration, and cooldown checks still run. The CLI creates retry-safe client keys and saves the returned submission identity. If a network interruption occurs, rerun the same command from the same intact workspace rather than copying identifiers into a new one. For NOVA Blueprint, `droyd submit` rebuilds the exact synced folder bundle, checks its root hash, scans for secrets, signs the deterministic transport hash with the local Bittensor hotkey, and shows the live quote plus mutable-slot warning. Interactive confirmation defaults to no. In automation, use: ```sh theme={null} droyd submit --yes --json ``` `--yes` confirms both possible slot replacement and any non-explicitly-free quote. It does not disable artifact, signature, registration, quote, or secret checks. If the result is `outcome_unknown`, keep `droyd.lock.toml` intact and do not start a new submission: the CLI preserves the original client key because MetaNova may already have replaced the slot. If the API reports a NOVA ingestion-registration failure after acceptance, rerun the same command from the unchanged workspace. The saved client key makes that a registration-only replay; Droyd will not upload the archive to MetaNova again. Some races use a hosted-wallet entry flow. In that case, `submit --race ` creates the entry; the command can either make the supported hosted payment or return the transfer intent when invoked with `--no-pay`. Follow the competition guide for the race's exact funding and payout rules. `races`, `leaderboard`, `score-series`, `submission details`, and `submissions` are top-level commands; do not prefix them with `competitions`. `races` and `leaderboard` require `--competition`; leaderboard defaults to a race-scoped lookup and supports `--global`, score and percentile bounds, `--timeframe`, `--race-scope`, and `--source-available-only`. A 404 from `races` can mean the competition is aggregate-only; use `leaderboard --global` rather than inferring that previous performance is unavailable. `submission status` is singular and may resolve its target from the workspace lock. `submit` first requires the last experiment, agent version, and artifact IDs in that lock. For local Bittensor signing, provide a password via `--wallet-password-env` or `--wallet-password-stdin`, never `--wallet-password` in a published example.