Every command

There are 593 commands, each on its own row in the order nextmail --help lists them. 46 are written by hand for people: they ask for what is missing, format what they print and combine several API calls where that helps, so their row names no single endpoint. The other 547 are the resource commands, nextmail <namespace> <verb> across 53 namespaces, and each one calls the endpoint its row names.

The resource commands are not written one by one. The CLI reads the SDK's method manifest, which describes every method with its parameters, endpoint and scopes, and turns each method into a verb named after the namespace and the method in kebab case, so domains.createAddress is nextmail domains create-address. A list and the listAll and iterate that walk it become one list verb with --all and --max, which is why there are fewer commands than SDK methods.

The package's parity check proves it before every release. For every SDK method it builds the command line three ways, with the required values only, with them in a --data file, and with every flag set, runs the command against a recording fetch, and fails when a method has no command or when a command sends anything other than the method, path, query, body and credential the manifest names. It then runs the same command lines through the real parser and dispatcher, and fails on any request that differs from the direct call.

Each row shows the first usage line of its command. nextmail <command> --help shows the rest: every argument and flag with what it takes, and examples, and for a resource command its scopes, its endpoint, what it returns and the notes from the API reference. Add --json for the same page as one JSON document, and nextmail --help --json prints every command, argument and flag at once. Every command also takes the global flags, --json, --yes, --dry-run, --profile, --api-key, --base-url, --no-input, --no-color and --debug, so no row repeats them.