Public beta — not for production use. Data may be wiped at any time. Questions? Contact us.
Documentation menu

axiom client add

Add a marketplace node or a saved flow as a client member

View as Markdown
<!-- GENERATED by docs/scripts/gen-cli-reference — DO NOT EDIT. Source of truth: the cobra command definitions in cmd/axiom/cmd/. Regenerate from the repo root with: go run ./docs/scripts/gen-cli-reference -->

axiom client add

Add a marketplace node or a saved flow as a client member

Add one member to a client's draft — a marketplace node, or a saved flow. Exactly one of --package or --flow must be given (flag branching):

axiom client add c1 --package billing-utils --node summarize --alias summarize
axiom client add c1 --package billing-utils@1.2.0 --node summarize --alias summarize
axiom client add c1 --flow <artifact-id> --alias run_pipeline

--package accepts "name" or "name@version". Omitting the version pins @latest server-side — the resolved pinned version is printed as a loud warning so an unattended run (e.g. a skill wiring this up) never silently loses reproducibility.

Requires a prior "axiom login".

Usage

axiom client add <client-id> [flags]

Flags

FlagShorthandTypeDefaultDescription
--aliasstringMember alias — the SDK method name; must be unique within the client
--flowstringArtifact ID of a saved flow to add
--help-hboolhelp for add
--jsonboolEmit a single JSON result object
--nodestringNode name within --package
--packagestringPackage to add a node from, as name or name@version

See also

  • axiom client — Create and manage Client Builder clients (typed SDKs)