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

axiom app-key

Manage invoke-scoped app keys (public browser credentials)

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 app-key

Manage invoke-scoped app keys (public browser credentials)

Manage invoke-scoped app keys: PUBLIC, long-lived credentials a browser app ships in its bundle, restricted to a fixed set of flows (graph IDs) with an origin allowlist and per-key rate caps.

An app key can ONLY invoke its listed flows (and follow the runs it starts) — it cannot read or write anything else on the platform. The origin allowlist is an anti-abuse measure, not a security boundary: real authorization belongs inside your flows (e.g. jwt-tools verification against your app's own users).

Usage

axiom app-key [flags]
axiom app-key [command]

Flags

FlagShorthandTypeDefaultDescription
--help-hboolhelp for app-key

Subcommands

CommandDescription
axiom app-key createMint an app key restricted to the given flows
axiom app-key lsList the tenant's API keys (app keys and PATs)
axiom app-key revokeRevoke a key by id (see "axiom app-key ls")
axiom app-key updateRe-point an app key at new flows and/or browser origins (the key value is unchanged)

See also