CLI reference

Index of Builder CLI commands used in the AI Fabrix integration lifecycle. Authoritative syntax, flags, and permissions live in Builder CLI help (aifabrix <command> --help) and the CLI workflow guide.

Authentication

aifabrix auth status
aifabrix login

Generate and model

aifabrix create <systemKey> --type external
aifabrix wizard [systemKey]
aifabrix wizard --config <file>
aifabrix repair <systemKey> [--dry-run] [--auth apikey] [--rbac] [--expose]
aifabrix json <systemKey>
aifabrix download <systemKey>

Validate and test

aifabrix validate <systemKey|file> [--cert-sync]
aifabrix test <systemKey>
aifabrix test-integration <systemKey>
aifabrix test-e2e <systemKey>
aifabrix datasource test-e2e <datasourceKey> --app <systemKey> [--test-crud]

Publish

aifabrix upload <systemKey> [--probe] [--dry-run] [--verbose]
aifabrix deploy <systemKey> [--probe]
aifabrix show <systemKey> --online

Enterprise AI Certification

Run after upload, in order:

aifabrix verify-operations <systemKey>
aifabrix verify-trust <systemKey>
aifabrix verify-governance <systemKey> [--subject-email <email>]
aifabrix lifecycle <systemKey>

Command	Pillar
`verify-operations`	Operations — validate, test, integration, E2E
`verify-trust`	Agent metadata trust — business metadata for AI
`verify-governance`	Governance — ABAC visibility per subject
`lifecycle`	Combined certification report

See Certification for the full ladder and Validation and certification for business context.

Datasource commands

Use aifabrix datasource (shorthand aifabrix ds) when you iterate on one datasource without re-uploading the entire external system. Commands below match the installed Builder CLI — run aifabrix datasource --help if a flag differs in your version.

Validate, list, and compare

aifabrix datasource validate <file-or-directory>
aifabrix datasource list [prefix]
aifabrix datasource diff <file1> <file2>

validate — offline schema and semantic checks on YAML/JSON (or a folder of datasource files)
list — datasources registered in the configured environment
diff — compare two datasource files before publish

Publish and test

aifabrix datasource upload <file-or-key>
aifabrix datasource test <datasourceKey>
aifabrix datasource test-integration <datasourceKey>
aifabrix datasource test-e2e <datasourceKey> --app <systemKey> [--test-crud]

upload — publish one datasource by file path or datasource key under integration/<systemKey>/
test — structural/policy validation on the dataplane
test-integration — integration validation on the dataplane
test-e2e — end-to-end validation against live or sandbox APIs

System-level equivalents remain aifabrix upload, aifabrix test-integration, and aifabrix test-e2e when you publish or test every datasource at once.

Logs and fixtures (optional)

aifabrix datasource log-test <datasourceKey>
aifabrix datasource log-integration <datasourceKey>
aifabrix datasource log-e2e <datasourceKey>
aifabrix datasource log-trust <datasourceKey>
aifabrix datasource load <datasourceKey> <fixture-file>
aifabrix datasource export <datasourceKey> [--output <path>]
aifabrix datasource clean-logs <systemKey>

Use log commands after failed test, test-integration, test-e2e, or verify-trust --debug runs. load and export move fixture or governed records for sandbox workflows — confirm environment before upload-style commands.

Lifecycle maintenance

aifabrix repair <systemKey> [--dry-run]
aifabrix delete <systemKey>

Narrative docs (prefer over this index)

For business context and phase order, use:

Limits

Command names and flags evolve with Builder releases. If a command fails, run aifabrix <command> --help and validate against your installed CLI version.

Documentation Index