LaunchKit · 2026
Back to Skills

valiron-trust-layer

Intercept and authorize outgoing machine-to-machine payments (x402 or similar) using @valiron/sdk trust decisions.

1
278 downloads
by @vatsashah45

Setup & Installation

openclaw skills install @vatsashah45/valiron-trust-layer

Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:

npx clawhub install valiron-trust-layer

Version History

v1.0.2Feb 25, 2026 - Version note by skill developer:

- Added a metadata field specifying the skill key and primary environment variable required (`VALIRON_API_KEY`). - Clarified that `VALIRON_API_KEY` is now optional by default, but reserved/required for authenticated deployments. - Updated runtime requirements and configuration instructions to reflect optional and conditional use of `VALIRON_API_KEY`. - Improved guidance on failure behavior: fail closed only if required policy/config inputs are missing, and clarified SDK authentication handling. - No code or file changes; documentation/refinement update only.

What This Skill Does

Adds a trust gate in front of outgoing machine-to-machine payments. Before payment execution, it checks the counterparty agent's identity via @valiron/sdk, applies a configurable policy (allow, throttle, sandbox, or deny), and records the decision for audit.

Applies deterministic policy checks and spend controls before any payment commitment rather than relying on free-form model output, reducing the risk of unauthorized or runaway agent spending.

When to use it

  • Blocking payments to untrusted agents automatically
  • Throttling spend when counterparty trust score is low
  • Sandboxing test payments to unverified agents
  • Auditing every outgoing payment decision with structured logs
  • Enforcing per-route spend limits on autonomous agent wallets

Example Workflow

Here's how your AI assistant might use this skill in practice.

INPUT

User asks: Process a payment to agent 0xABC for API access

AGENT
  1. 1Extract counterpartyAgentId from the incoming payment request
  2. 2Call checkAgent(agentId) to retrieve a trust decision from Valiron
  3. 3Map the trust result to a route using the decision policy (prod, sandbox_only, etc.)
  4. 4Evaluate spend controls and per-route caps against the payment amount
  5. 5Allow payment and log the authorization, or return an explicit denial reason
OUTPUT

Payment is authorized under the prod policy and proceeds to x402 execution, or is denied with a structured rejection reason returned to the caller

Requirements

Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.

VALIRON_API_KEY environment variable (required for authenticated deployments)