Verify the install

Four checks, in the order worth running them.

The command exists

bash

wasit --version

Prints the installed version, read from the package's own manifest at runtime rather than a hardcoded string, so it cannot disagree with what npm actually published.

If your shell reports "command not found" after a global install, npm's global bin directory is not on your PATH. npm prefix -g prints where it went.

It can list its own checks

bash

wasit checks

Contacts nothing and needs no keys. If this prints thirteen checks, the install is sound and the problem in any later failure is configuration or the target, not Wasit.

It reads your configuration

bash

wasit wallet status

Prints each configured role's address and balances. A role you have not set up reports which variable is missing rather than failing.

Note — a key that is set but malformed — a truncated paste, or a G... public key where a secret belongs — is reported by name against that one role, and the other roles are still checked.

It exits the way CI expects

bash

wasit test --target https://your-service.example/paid --read-only
echo $?

On Windows PowerShell:

text

0 means everything that ran conformed, 1 a conformance failure, and 2 that a check produced no verdict at all — an unreachable target or a misconfigured run. A CI job that treats 2 as a test failure will blame your service for what is really a broken pipeline.