Exit codes and output contract¶
Use this page when scripting aeat invocations: it documents the process exit codes and the TTY/JSON output behavior shared by every command.
Exit codes¶
Code |
Meaning |
|---|---|
|
Success. |
|
General error or refused operation. |
|
Invalid CLI usage (bad flag, missing argument). |
|
Authentication required or credentials expired. |
|
Resource not found. |
|
Conflict or precondition failure. |
|
Validation error in user-supplied data. |
|
External service unavailable. |
|
Operation not permitted by policy. |
|
Unexpected internal error. |
|
Partial success (some items succeeded, some failed). |
TTY and JSON output contract¶
When output is to a TTY the CLI emits human-readable rich text. When --format json is passed (or when output is redirected) the CLI emits a single JSON document per invocation. Commands that have adopted the SchemaEnvelope wrap their result as {schema_version, command, result, warnings}. Commands not yet migrated emit their payload directly.