Skip to main content

Command Overview

The prokodo CLI exposes five top-level commands. Each is documented on its own page.

prokodo <command> [sub-command] [options]

Commands at a glance

CommandSub-commandsWhat it does
authlogin ยท logout ยท whoamiManage API key credentials
initโ€”Scaffold .prokodo/config.json
verifyโ€”Run a cloud verification
creditsโ€”Show credit balance
doctorโ€”Environment health-check

Global help command

Commander ships a built-in help sub-command:

prokodo help              # same as --help
prokodo help auth # auth sub-command help
prokodo help verify # verify options

Exit codes

Every command follows this contract:

CodeMeaning
0Success
1Known / expected failure (e.g. verification failed, doctor check failed)
2Usage error, missing config, or fatal setup problem

This makes it safe to use in scripts:

prokodo verify && echo "Passed" || echo "Failed"

JSON output

Append

--json
to any command for machine-readable output on stdout. Human-readable logs still go to stderr, so you can redirect them independently:

prokodo verify --json 2>/dev/null | jq .passed
prokodo doctor --json 2>/dev/null | jq '[.checks[] | select(.passed == false)]'

Environment variables

VariableDescription
PROKODO_API_KEYAPI key โ€” used when no
--api-key
flag or credentials file
PROKODO_API_BASE_URLOverride the marketplace API base URL
NO_COLORDisable all ANSI colour output