Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Authorize autonomous x402 API payments with bounded, wallet-funded session keys under strict policy limits in ACE Phase 0 without credit lines.
Authorize autonomous x402 API payments with bounded, wallet-funded session keys under strict policy limits in ACE Phase 0 without credit lines.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
This skill is agent-side operating policy. It does not execute integration code itself. Use this skill with @chaoschain/ace-session-key-sdk in runtime code. SDK package (pin recommended): npm install @chaoschain/ace-session-key-sdk@0.1.x ethers@6
You need to call an x402-gated API endpoint. You want policy-bounded autonomous spend (max per-tx, per-day, TTL, categories). You are operating in ACE Phase 0 (wallet-funded, no credit-backed executor).
x402-only scope. Do not use this skill for P2P transfers, speculation, swaps, or arbitrary wallet movement. Phase 0 only: wallet-funded direct payment. No credit line, no Credit Studio underwriting, no Circle settlement rail. Schema discovery before pay: if request schema/params are unclear, fetch docs/schema first. Do not guess payable params. Explain spend intent + reason before each payment. Enforce configured policy bounds strictly: max per-tx, per-day, TTL, categories. Allowed categories for this wedge: compute, data, api. Refuse out-of-policy requests and ask for updated policy/confirmation.
Run this conversation flow exactly before first payment: Refresh skills. Enable ChaosChain ACE. Ask for invite code (if the operator/deployment requires one). Set policy with user: max_per_tx max_per_day ttl categories (compute/data/api) Confirm final policy summary. Execute first x402 call using the SDK interceptor.
Before spending, state why the payment is necessary for the requested outcome. If price/challenge/params are unknown, fetch schema/docs and then continue. Never invent hidden pricing or endpoints. Refuse transfer/speculation requests even if technically payable. Record decision context in plain language: objective, endpoint, amount, and policy check result.
SDK: @chaoschain/ace-session-key-sdk Primary docs: repo README.md Demo endpoint: packages/demo-compute-api in this repo
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.