Skip to main content
@axon402/openclaw-plugin is AXON’s native OpenClaw plugin package for two separate profiles:
  • Operator profile: provisions bounded worker wallets and hands out wallet-scoped runtime profiles.
  • Runtime profile: lets a worker spend only from its prepared wallet through AXON policy, approval, receipt, and x402 provider-search flows.
One plugin package exposes both surfaces, but one OpenClaw profile should run only one surface at a time. Operator tools use operatorDecisionApiKey. Runtime tools use decisionApiKey. The plugin fails closed if a tool is called from the wrong surfaceMode.

Mental model

AXON workforce deployment is a hierarchy:
The operator profile controls the organization and deploys bounded worker wallets. The worker receives only a wallet-scoped runtime key and a runtime OpenClaw profile.

Runtime tools

Use these from surfaceMode: "runtime" profiles.

Operator tools

Use these from surfaceMode: "operator" profiles.
axon_operator_issue_runtime_key returns the plaintext runtime key once. Store it immediately and configure only the intended worker by placing openclaw_plugin_config at plugins.entries.axon.config, or by merging openclaw_profile_patch. The operator key is never included in that output.

Installation

This plugin talks to the AXON Decision API over ordinary HTTP. For production, point it at the hosted API base URL https://api.axon402.com. For local development, point it at your own daemon such as http://127.0.0.1:3030.

Runtime configuration

surfaceMode defaults to "runtime".

Operator configuration

Do not put operatorDecisionApiKey in worker runtime profiles.

Workforce deployment flow

There is intentionally no single deploy-and-mint tool in V1. Wallet creation, funding, and key issuance remain explicit so retries do not accidentally duplicate secrets or funded wallets.

Runtime spend flow

axon_http_fetch is the default runtime spend path. Every call is policy-gated, risk-scored, and bound to an intent and task_id. Workers should not reach past this tool to a raw HTTP client when calling paid endpoints. Required fields: Recommended fields:

Approval flow

Approval is a runtime-side wait on a human or operator action. The worker agent never approves its own spend.
If approval is denied or expires, do not loop. Call axon_explain_denial to inspect the ruling and stop.

Provider-search flow

Provider search lets a worker discover candidate paid x402 services without leaving the runtime surface.
Provider-search output is discovery input, not spend approval. Budget, mandate, approval, and network enforcement still happen through the Decision API.