Skip to main content
afauth status prints a local snapshot of the agent’s identity and readiness — the did:key, where the key lives, the trust-attestor binding (and whether it’s live), and a summary of known accounts. Where afauth whoami prints the bare did:key for scripts, status answers the operational question: who am I, where’s my key, and am I linked to a trust attestor?
It reads only local files (key.json, trust.json, accounts.json) and makes no network calls, so the link state is a local judgment — it flags expired and orphaned bindings, but cannot confirm a server-side revocation at the attestor.

Output

If no identity exists yet, status prints a hint to run afauth init and exits.

Flags

See also