Zetrix Agentic Wallet for Openclaw

Openclaw Skills turns an AI agent into a Zetrix wallet that can prove identity, pay for gated resources, and issue verifiable credentials.

zetrix
v1.0.1
Jul 31, 2026
0
72
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install zetrix-agentic-wallet

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install zetrix-agentic-wallet using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Zetrix Agentic Wallet?

Openclaw Skills for the Zetrix Agentic Wallet gives an AI coding agent a secure, HSM-backed holder identity for on-chain interaction without exposing private keys. It supports x401 proof flows, x402 pay-per-use access, and verifiable credential issuance through a single-holder wallet model.

This skill is designed for conversations where the agent must act on behalf of a user: checking wallet status, answering proof challenges, paying for protected resources, or onboarding a new holder account. Openclaw Skills keeps the workflow explicit, auditable, and safe by requiring confirmation before spend actions and by retaining issued credentials for later reuse in the session.

Zetrix Agentic Wallet Use Cases

  • Check the active Zetrix wallet identity, address, and network before taking action.
  • Respond to x401 PROOF-REQUEST challenges and return a replayable proof header.
  • Fetch x402-protected URLs and automatically pay when the endpoint requires access fees.
  • Issue verifiable credentials such as an agent-identity credential through a paid subscription flow.
  • Set up or create a new holder wallet account when no active identity exists yet.
  • Verify whether a required VC is already available before attempting authentication or issuance.
  • Support on-chain pay-per-use interactions where the agent needs to transact real value safely.

How Zetrix Agentic Wallet Works

  1. The agent first checks wallet status to learn the holder DID, Zetrix address, network, and any credentials already held.
  2. If no wallet account exists, onboarding can create a new HSM-backed holder account, but only as a deliberate setup step.
  3. When a service sends an x401 challenge, the agent uses the appropriate VC to generate a proof response header.
  4. When a resource returns x402 payment requirements, the agent confirms intent, then fetches the URL and auto-pays within the configured cap.
  5. When a user requests a credential, the agent gathers the required attributes, confirms spend intent, and issues the VC in one paid call.
  6. The session tracks issued VCs and the latest proof header so they can be reused without losing identity continuity.

Zetrix Agentic Wallet Setup

  1. Ensure the agentic-wallet MCP server is already provisioned and connected to the runtime.
  2. Provide the required secret and configuration values through your secure environment, not through chat.
  3. Set the mandatory HSM password and, if applicable, the holder address and network.
  4. Configure a non-zero payment cap before any pay or issue operation can succeed.
  5. Restart or redeploy the wallet only after the administrator has saved the holder configuration.
npm install -g agentic-wallet-mcp

Required environment variables:

export HSM_PASSWORD="<secure-secret-from-your-secret-store>"
export ZETRIX_ADDRESS="<optional-holder-address>"
export ZETRIX_NETWORK="zetrix:mainnet"
export MAX_PAYMENT_AMOUNT='{"*":"5"}'

Notes:

  • HSM_PASSWORD is required and must never be pasted into chat.
  • ZETRIX_ADDRESS may be omitted for first-run auto-creation, depending on deployment.
  • ZETRIX_NETWORK defaults to zetrix:mainnet; use testnet for non-real value testing.
  • MAX_PAYMENT_AMOUNT ships fail-closed as {"*":"0"}, so payment is blocked until intentionally configured.

Zetrix Agentic Wallet Data Schema & Taxonomy

Openclaw Skills structures this wallet skill around a small set of session and wallet artifacts.

Artifact Purpose Source
holderDid The active Zetrix DID for the single holder identity wallet_status or create_holder_account
zetrixAddress The holder’s on-chain address wallet_status or create_holder_account
network Active network, either zetrix:mainnet or zetrix:testnet wallet_status
heldVCs Credentials already available for proofs in the current session User-supplied or returned from subscribe_and_issue
lastProofHeader Most recent x401 proof response to replay to the origin service prove_identity
paidThisSession Transparency log of paid resources and amounts pay_and_fetch

Generated or returned payloads:

  • proofResponseHeader: replay token for the original x401 resource server.
  • vc: the issued verifiable credential returned by issuance.
  • vcId: credential identifier for recordkeeping.
  • txHash: on-chain transaction hash for paid issuance.
  • amountPaidHuman and asset: payment summary for x402 operations.

Taxonomy and operational rules:

  • Single-holder wallet only: one running instance maps to one identity.
  • Credentials are not stored by the wallet backend; the session must retain any issued vc.
  • Real value actions are bounded by MAX_PAYMENT_AMOUNT.
  • Sensitive secrets are excluded from all data structures and never passed through tool outputs.

Zetrix Agentic Wallet Advanced Features

  • HSM-backed signing that keeps private keys out of the tool process entirely.
  • x401 identity proof support for services that require challenge/response authentication.
  • x402 pay-per-use automation that fetches protected resources and pays only when needed.
  • Credential issuance workflow for agent identity and other verifiable credential templates.
  • Session-level credential retention so issued VCs can be reused for later proofs.
  • Fail-closed spend control via server-enforced per-asset payment caps.
  • Single-holder deployment model that simplifies identity binding and auditability.
  • Clear network awareness so operators can distinguish mainnet value from testnet value.
  • Safe onboarding path for creating a new holder account only when none exists.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*