OpenClaw integration

The AgenticFI OpenClaw extension 0.1.0 is a public MIT alpha with an immutable GitHub release. It is directly installable through OpenClaw's native Git plugin path. It is not yet a ClawHub listing or a production-qualified funded integration.

What it adds

• a native onchain-router provider with live policy-filtered chat models;
• read-only tools for models, pricing, and voices;
• bounded paid tools for images, MP3 speech, and MP3 transcription;
• an authenticated /onchain-router command for redacted status, diagnostics, and recovery guidance;
• one deterministic Buyer Runtime idempotency key across host retries of the same transport turn;
• optional lifecycle management for the exact installed @agenticfi/onchain-router-proxy@0.1.2 dependency.

It does not create, import, inspect, unlock, fund, or back up a wallet. It does not implement x402, choose a paid fallback, download packages at runtime, or connect OpenClaw directly to the public payment service.

Requirements and install

• Node.js >=24.15.0 <25;
• OpenClaw 2026.8.1;
• macOS or Linux;
• a Buyer Runtime profile created and unlocked by a human;
• the exact proxy version declared by the extension.

openclaw plugins install git:github.com/AgenticFI/onchain-router-openclaw@v0.1.0 --force
openclaw plugins enable onchain-router --accept-capabilities
openclaw plugins inspect onchain-router --runtime --json

--force acknowledges the external GitHub source; it does not bypass host policy or capability consent. The version tag prevents a later branch update from silently replacing the reviewed release. Review the declared local-file and process capabilities, then choose an onchain-router/<model-id> returned by the live picker.

Local trust boundary

The extension connects only to the authenticated proxy on exact loopback http://127.0.0.1:8402. Its bearer must be a regular owner-only file at mode 0600. Never expose the proxy through a tunnel, reverse proxy, LAN bind, or container host port.

Native chat retries preserve the same financial identity for one transport turn. Do not configure model fallbacks for this provider: an ambiguous paid result requires receipt inspection and deliberate same-key recovery, not a new request or model.

The release workflow builds and tests the adapter, runs OpenClaw archive and native-Git lifecycle qualification, and publishes the packed artifact. The complete setup, build, tool, configuration, and troubleshooting instructions are in the public repository. A funded OpenClaw request remains an explicit operator acceptance step because it spends from the operator's Buyer Runtime wallet.