Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · AI
Everclaw — Inference You Own
AI inference you own, forever powering your OpenClaw agents via the Morpheus decentralized network. Stake MOR tokens, access Kimi K2.5 and 30+ models, and ma...
skill openclawclawhub Free
AI inference you own, forever powering your OpenClaw agents via the Morpheus decentralized network. Stake MOR tokens, access Kimi K2.5 and 30+ models, and ma...
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Item is unstable.
This item is timing out or returning errors right now. Review the source page and try again later.
Quick setup
- Wait for the source to recover or retry later.
- Review SKILL.md only after the source returns a real package.
- Do not rely on this source for automated install yet.
Package facts
- Download mode
- Manual review
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- CHANGELOG.md, README.md, SKILL.md, templates/openclaw-config-mac.json, templates/openclaw-config-gateway-only.json, templates/openclaw-config-linux.json
Validation
- Wait for the source to recover or retry later.
- Review SKILL.md only after the download returns a real package.
- Treat this source as transient until the upstream errors clear.
Install with your agent
Agent handoff
Use the source page and any available docs to guide the install because the item is currently unstable or timing out.
- Open the source page via Review source status.
- If you can obtain the package, extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the source page and extracted files.
New install
I tried to install a skill package from Yavira, but the item is currently unstable or timing out. Inspect the source page and any extracted docs, then tell me what you can confirm and any manual steps still required. Then review README.md for any prerequisites, environment setup, or post-install checks.
Upgrade existing
I tried to upgrade a skill package from Yavira, but the item is currently unstable or timing out. Compare the source page and any extracted docs with my current installation, then summarize what changed and what manual follow-up I still need. Then review README.md for any prerequisites, environment setup, or post-install checks.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.10.0
Provenance
- Publisher
- DavidAJohnston
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
🤖 Agent Setup Instructions
If your human asks you to set up Everclaw / Morpheus inference, follow these steps exactly.
Quick Setup (Gateway Only — easiest)
node ~/.openclaw/workspace/skills/everclaw/scripts/setup.mjs --template gateway-only --key <API_KEY> --apply --test --restart
Full Setup (Local P2P + Gateway)
node ~/.openclaw/workspace/skills/everclaw/scripts/setup.mjs --key <API_KEY> --apply --test --restart
What setup.mjs does:
Detects OS → picks the right config template (mac/linux/gateway-only) Deep-merges Morpheus providers into existing openclaw.json (preserves all other config) Substitutes the API key into the mor-gateway provider Updates auth-profiles.json with the new provider credentials Tests gateway connectivity (with --test) Restarts OpenClaw gateway (with --restart)
Flags:
FlagWhat it does--template <name>Override OS auto-detection (mac, linux, gateway-only)--key <key>Morpheus API Gateway key (free from app.mor.org)--applyWrite changes (default is dry-run)--testPing gateway after setup--restartRestart OpenClaw gateway after apply
⚠️ Critical Guardrails
NEVER use everclaw/ as a model prefix. Everclaw is a skill, not a provider. Use morpheus/ or mor-gateway/. Always dry-run first (omit --apply) to preview changes before writing. Don't edit openclaw.json by hand when setup.mjs can do it — the merge logic handles edge cases. API keys: Get a free key at https://app.mor.org — don't use the community bootstrap key for production.
Getting an API key:
Go to https://app.mor.org Create an account and sign in Click "Create API Key" and enable automation Pass the key to setup.mjs with --key
♾️ Everclaw — AI Inference You Own, Forever Powering Your OpenClaw Agents
Powered by Morpheus AI Open-source first. GLM-5 handles everything — Claude is the escape hatch, not the default. Access GLM-5, GLM-4.7 Flash, Kimi K2.5, and 30+ models with inference you own. Everclaw connects your OpenClaw agent to the Morpheus P2P network — stake MOR tokens, open sessions, and recycle your stake for persistent, self-sovereign access to AI. 📦 ClawHub: clawhub install everclaw-inference — clawhub.ai/EverClaw/everclaw-inference ⚠️ Name Collision Warning: A different product ("Everclaw Vault") uses the bare everclaw slug on ClawHub. Always use everclaw-inference — never clawhub install everclaw or clawhub update everclaw. See CLAWHUB_WARNING.md for details.
Prerequisites
Before installing EverClaw, ensure you have the following: DependencyHow to InstallRequired ForHomebrew (macOS)/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"Package managerNode.js (v18+)brew install nodeBootstrap scripts, proxyGitbrew install gitSkill installationOpenClawcurl -fsSL https://get.openclaw.ai | bashAgent runtime
Quick Check
Run this to verify your environment: curl -fsSL https://raw.githubusercontent.com/profbernardoj/everclaw/main/scripts/install-with-deps.sh | bash -s -- --check-only
One-Line Install
curl -fsSL https://raw.githubusercontent.com/profbernardoj/everclaw/main/scripts/install-with-deps.sh | bash This will: Check for all required dependencies Prompt to install any missing ones Clone EverClaw to ~/.openclaw/workspace/skills/everclaw Bootstrap a free GLM-5 starter key (1,000 requests/day) Optionally install the Morpheus proxy-router for P2P inference
New to OpenClaw?
If you don't have OpenClaw installed yet: # Install OpenClaw first curl -fsSL https://get.openclaw.ai | bash # Then install EverClaw curl -fsSL https://raw.githubusercontent.com/profbernardoj/everclaw/main/scripts/install-with-deps.sh | bash
How It Works
Get MOR tokens on Base — swap from ETH/USDC via Uniswap or Aerodrome (see below) You run a proxy-router (Morpheus Lumerin Node) locally as a consumer The router connects to Base mainnet and discovers model providers You stake MOR tokens to open a session with a provider (MOR is locked, not spent) You send inference requests to http://localhost:8082/v1/chat/completions When the session ends, your MOR is returned (minus tiny usage fees) Re-stake the returned MOR into new sessions → persistent inference you own
Agent Integration (Recommended Path)
If you are an AI agent (OpenClaw, Claude, etc.), use the OpenAI-compatible proxy for all Morpheus inference. Do NOT use the bash scripts (session.sh, chat.sh) -- the proxy handles sessions, auth, and model routing automatically.
Send Inference
curl http://127.0.0.1:8083/v1/chat/completions \ -H "Content-Type: application/json" \ -H "Authorization: Bearer morpheus-local" \ -d '{"model": "kimi-k2.5", "messages": [{"role": "user", "content": "Hello"}], "stream": false}'
List Available Models
curl http://127.0.0.1:8083/v1/models
Health Check
curl http://127.0.0.1:8083/health The proxy (port 8083) auto-opens blockchain sessions, auto-renews before expiry, and injects all required auth headers. The bash scripts (session.sh, chat.sh) are available for manual debugging but should not be used for agent integration. See Section 12 for full proxy documentation.
Getting MOR Tokens
You need MOR on Base to stake for inference. If you already have ETH, USDC, or USDT on Base: # Swap ETH for MOR bash skills/everclaw/scripts/swap.sh eth 0.01 # Swap USDC for MOR bash skills/everclaw/scripts/swap.sh usdc 50 Or swap manually on a DEX: Uniswap: MOR/ETH on Base Aerodrome: MOR swap on Base Don't have anything on Base yet? Buy ETH on Coinbase, withdraw to Base, then swap to MOR. See references/acquiring-mor.md for the full guide. How much do you need? MOR is staked, not spent — you get it back. 50-100 MOR is enough for daily use. 0.005 ETH covers months of Base gas fees.
Architecture
Agent → proxy-router (localhost:8082) → Morpheus P2P Network → Provider → Model ↓ Base Mainnet (MOR staking, session management)
Option A: ClawHub (Easiest)
clawhub install everclaw-inference To update: clawhub update everclaw-inference ⚠️ Use everclaw-inference — not everclaw. The bare everclaw slug belongs to a different, unrelated product on ClawHub.
Option B: One-Command Installer
The safe installer handles fresh installs, updates, and ClawHub collision detection: # Fresh install curl -fsSL https://raw.githubusercontent.com/profbernardoj/everclaw/main/scripts/install-everclaw.sh | bash # Or if you already have the skill: bash skills/everclaw/scripts/install-everclaw.sh # Check for updates bash skills/everclaw/scripts/install-everclaw.sh --check
Option C: Manual Git Clone
git clone https://github.com/profbernardoj/everclaw.git ~/.openclaw/workspace/skills/everclaw To update: cd ~/.openclaw/workspace/skills/everclaw && git pull
Install the Morpheus Router
After cloning, install the proxy-router: bash skills/everclaw/scripts/install.sh This downloads the latest proxy-router release for your OS/arch, extracts it to ~/morpheus/, and creates initial config files.
Manual Installation
Go to Morpheus-Lumerin-Node releases Download the release for your platform (e.g., mor-launch-darwin-arm64.zip) Extract to ~/morpheus/ On macOS: xattr -cr ~/morpheus/
Required Files
After installation, ~/morpheus/ should contain: FilePurposeproxy-routerThe main binary.envConfiguration (RPC, contracts, ports)models-config.jsonMaps blockchain model IDs to API types.cookieAuto-generated auth credentials
.env File
The .env file configures the proxy-router for consumer mode on Base mainnet. Critical variables: # RPC endpoint — MUST be set or router silently fails ETH_NODE_ADDRESS=https://base-mainnet.public.blastapi.io ETH_NODE_CHAIN_ID=8453 # Contract addresses (Base mainnet) DIAMOND_CONTRACT_ADDRESS=0x6aBE1d282f72B474E54527D93b979A4f64d3030a MOR_TOKEN_ADDRESS=0x7431aDa8a591C955a994a21710752EF9b882b8e3 # Wallet key — leave blank, inject at runtime via 1Password WALLET_PRIVATE_KEY= # Proxy settings PROXY_ADDRESS=0.0.0.0:3333 PROXY_STORAGE_PATH=./data/badger/ PROXY_STORE_CHAT_CONTEXT=true PROXY_FORWARD_CHAT_CONTEXT=true MODELS_CONFIG_PATH=./models-config.json # Web API WEB_ADDRESS=0.0.0.0:8082 WEB_PUBLIC_URL=http://localhost:8082 # Auth AUTH_CONFIG_FILE_PATH=./proxy.conf COOKIE_FILE_PATH=./.cookie # Logging LOG_COLOR=true LOG_LEVEL_APP=info LOG_FOLDER_PATH=./data/logs ENVIRONMENT=production ⚠️ ETH_NODE_ADDRESS MUST be set. The router silently connects to an empty string without it and all blockchain operations fail. Also MODELS_CONFIG_PATH must point to your models-config.json.
models-config.json
⚠️ This file is required. Without it, chat completions fail with "api adapter not found". { "$schema": "./internal/config/models-config-schema.json", "models": [ { "modelId": "0xb487ee62516981f533d9164a0a3dcca836b06144506ad47a5c024a7a2a33fc58", "modelName": "kimi-k2.5:web", "apiType": "openai", "apiUrl": "" }, { "modelId": "0xbb9e920d94ad3fa2861e1e209d0a969dbe9e1af1cf1ad95c49f76d7b63d32d93", "modelName": "kimi-k2.5", "apiType": "openai", "apiUrl": "" } ] } ⚠️ Note the format: The JSON uses a "models" array with "modelId" / "modelName" / "apiType" / "apiUrl" fields. The apiUrl is left empty — the router resolves provider endpoints from the blockchain. Add entries for every model you want to use. See references/models.md for the full list.
Secure Launch (1Password)
The proxy-router needs your wallet private key. Never store it on disk. Inject it at runtime from 1Password: bash skills/everclaw/scripts/start.sh Or manually: cd ~/morpheus source .env # Retrieve private key from 1Password (never touches disk) export WALLET_PRIVATE_KEY=$( OP_SERVICE_ACCOUNT_TOKEN=$(security find-generic-password -a "YOUR_KEYCHAIN_ACCOUNT" -s "op-service-account-token" -w) \ op item get "YOUR_ITEM_NAME" --vault "YOUR_VAULT_NAME" --fields "Private Key" --reveal ) export ETH_NODE_ADDRESS nohup ./proxy-router > ./data/logs/router-stdout.log 2>&1 &
Health Check
Wait a few seconds, then verify: COOKIE_PASS=$(cat ~/morpheus/.cookie | cut -d: -f2) curl -s -u "admin:$COOKIE_PASS" http://localhost:8082/healthcheck Expected: HTTP 200.
Stopping
bash skills/everclaw/scripts/stop.sh Or: pkill -f proxy-router
4. MOR Allowance
Before opening sessions, approve the Diamond contract to transfer MOR on your behalf: COOKIE_PASS=$(cat ~/morpheus/.cookie | cut -d: -f2) curl -s -u "admin:$COOKIE_PASS" -X POST \ "http://localhost:8082/blockchain/approve?spender=0x6aBE1d282f72B474E54527D93b979A4f64d3030a&amount=1000000000000000000000" ⚠️ The /blockchain/approve endpoint uses query parameters, not a JSON body. The amount is in wei (1000000000000000000 = 1 MOR). Approve a large amount so you don't need to re-approve frequently.
5. Opening Sessions
Open a session by model ID (not bid ID): MODEL_ID="0xb487ee62516981f533d9164a0a3dcca836b06144506ad47a5c024a7a2a33fc58" curl -s -u "admin:$COOKIE_PASS" -X POST \ "http://localhost:8082/blockchain/models/${MODEL_ID}/session" \ -H "Content-Type: application/json" \ -d '{"sessionDuration": 3600}' ⚠️ Always use the model ID endpoint, not the bid ID. Using a bid ID results in "dial tcp: missing address".
Session Duration
Duration is in seconds: 3600 = 1 hour, 86400 = 1 day Two blockchain transactions occur: approve transfer + open session MOR is staked (locked) for the session duration When the session closes, MOR is returned to your wallet
Response
The response includes a sessionId (hex string). Save this — you need it for inference.
Using the Script
# Open a 1-hour session for kimi-k2.5:web bash skills/everclaw/scripts/session.sh open kimi-k2.5:web 3600 # List active sessions bash skills/everclaw/scripts/session.sh list # Close a session bash skills/everclaw/scripts/session.sh close 0xSESSION_ID_HERE
⚠️ THE #1 GOTCHA: Headers, Not Body
session_id and model_id are HTTP headers, not JSON body fields. This is the single most common mistake. CORRECT: curl -s -u "admin:$COOKIE_PASS" "http://localhost:8082/v1/chat/completions" \ -H "Content-Type: application/json" \ -H "session_id: 0xYOUR_SESSION_ID" \ -H "model_id: 0xYOUR_MODEL_ID" \ -d '{ "model": "kimi-k2.5:web", "messages": [{"role": "user", "content": "Hello, world!"}], "stream": false }' WRONG (will fail with "session not found"): # DON'T DO THIS curl -s ... -d '{ "model": "kimi-k2.5:web", "session_id": "0x...", # WRONG — not a body field "model_id": "0x...", # WRONG — not a body field "messages": [...] }'
Using the Chat Script
bash skills/everclaw/scripts/chat.sh kimi-k2.5:web "What is the meaning of life?"
Streaming
Set "stream": true in the request body. The response will be Server-Sent Events (SSE).
7. Closing Sessions
Close a session to reclaim your staked MOR: curl -s -u "admin:$COOKIE_PASS" -X POST \ "http://localhost:8082/blockchain/sessions/0xSESSION_ID/close" Or use the script: bash skills/everclaw/scripts/session.sh close 0xSESSION_ID ⚠️ MOR staked in a session is returned when the session closes. Close sessions you're not using to free up MOR for new sessions.
Sessions Are Ephemeral
⚠️ Sessions are NOT persisted across router restarts. If you restart the proxy-router, you must re-open sessions. The blockchain still has the session, but the router's in-memory state is lost.
Monitoring
# Check balance (MOR + ETH) bash skills/everclaw/scripts/balance.sh # List sessions bash skills/everclaw/scripts/session.sh list
Session Lifecycle
Open → MOR is staked, session is active Active → Send inference requests using session_id header Expired → Session duration elapsed; MOR returned automatically Closed → Manually closed; MOR returned immediately
Re-opening After Restart
After restarting the router: # Wait for health check sleep 5 # Re-open sessions for models you need bash skills/everclaw/scripts/session.sh open kimi-k2.5:web 3600
9. Checking Balances
COOKIE_PASS=$(cat ~/morpheus/.cookie | cut -d: -f2) # MOR and ETH balance curl -s -u "admin:$COOKIE_PASS" http://localhost:8082/blockchain/balance | jq . # Active sessions curl -s -u "admin:$COOKIE_PASS" http://localhost:8082/blockchain/sessions | jq . # Available models curl -s -u "admin:$COOKIE_PASS" http://localhost:8082/blockchain/models | jq .
10. Troubleshooting
See references/troubleshooting.md for a complete guide. Quick hits: ErrorFixsession not foundUse session_id/model_id as HTTP headers, not body fieldsdial tcp: missing addressOpen session by model ID, not bid IDapi adapter not foundAdd the model to models-config.jsonERC20: transfer amount exceeds balanceClose old sessions to free staked MORSessions gone after restartNormal — re-open sessions after restartMorpheusUI conflictsDon't run MorpheusUI and headless router simultaneously
Key Contract Addresses (Base Mainnet)
ContractAddressDiamond0x6aBE1d282f72B474E54527D93b979A4f64d3030aMOR Token0x7431aDa8a591C955a994a21710752EF9b882b8e3
Quick Reference
ActionCommandInstallbash skills/everclaw/scripts/install.shStartbash skills/everclaw/scripts/start.shStopbash skills/everclaw/scripts/stop.shSwap ETH→MORbash skills/everclaw/scripts/swap.sh eth 0.01Swap USDC→MORbash skills/everclaw/scripts/swap.sh usdc 50Open sessionbash skills/everclaw/scripts/session.sh open <model> [duration]Close sessionbash skills/everclaw/scripts/session.sh close <session_id>List sessionsbash skills/everclaw/scripts/session.sh listSend promptbash skills/everclaw/scripts/chat.sh <model> "prompt"Check balancebash skills/everclaw/scripts/balance.shDiagnosebash skills/everclaw/scripts/diagnose.shDiagnose (config only)bash skills/everclaw/scripts/diagnose.sh --configDiagnose (quick)bash skills/everclaw/scripts/diagnose.sh --quick
11. Wallet Management (v0.4)
Everclaw v0.4 includes a self-contained wallet manager that eliminates all external account dependencies. No 1Password, no Foundry, no Safe Wallet — just macOS Keychain and Node.js (already bundled with OpenClaw).
Setup (One Command)
node skills/everclaw/scripts/everclaw-wallet.mjs setup This generates a new Ethereum wallet and stores the private key in your macOS Keychain (encrypted at rest, protected by your login password / Touch ID).
Import Existing Key
node skills/everclaw/scripts/everclaw-wallet.mjs import-key 0xYOUR_PRIVATE_KEY
Check Balances
node skills/everclaw/scripts/everclaw-wallet.mjs balance Shows ETH, MOR, USDC balances and MOR allowance for the Diamond contract.
Swap ETH/USDC for MOR
# Swap 0.05 ETH for MOR node skills/everclaw/scripts/everclaw-wallet.mjs swap eth 0.05 # Swap 50 USDC for MOR node skills/everclaw/scripts/everclaw-wallet.mjs swap usdc 50 Executes onchain swaps via Uniswap V3 on Base. No external tools required — uses viem (bundled with OpenClaw).
Approve MOR for Staking
node skills/everclaw/scripts/everclaw-wallet.mjs approve Approves the Morpheus Diamond contract to use your MOR for session staking.
Security Model
Private key stored in macOS Keychain (encrypted at rest) Protected by your login password / Touch ID Key is injected at runtime and immediately unset from environment Key is never written to disk as a plaintext file For advanced users: 1Password is supported as a fallback (backward compatible)
Full Command Reference
CommandDescriptionsetupGenerate wallet, store in KeychainaddressShow wallet addressbalanceShow ETH, MOR, USDC balancesswap eth <amount>Swap ETH → MOR via Uniswap V3swap usdc <amount>Swap USDC → MOR via Uniswap V3approve [amount]Approve MOR for Morpheus stakingexport-keyPrint private key (use with caution)import-key <0xkey>Import existing private key
12. OpenAI-Compatible Proxy (v0.2)
The Morpheus proxy-router requires custom auth (Basic auth via .cookie) and custom HTTP headers (session_id, model_id) that standard OpenAI clients don't support. Everclaw includes a lightweight proxy that bridges this gap.
What It Does
OpenClaw/any client → morpheus-proxy (port 8083) → proxy-router (port 8082) → Morpheus P2P → Provider Accepts standard OpenAI /v1/chat/completions requests Auto-opens blockchain sessions on demand (no manual session management) Auto-renews sessions before expiry (default: 1 hour before) Injects Basic auth + session_id/model_id headers automatically Exposes /health, /v1/models, /v1/chat/completions
Installation
bash skills/everclaw/scripts/install-proxy.sh This installs: morpheus-proxy.mjs → ~/morpheus/proxy/ gateway-guardian.sh → ~/.openclaw/workspace/scripts/ launchd plists for both (macOS, auto-start on boot)
Configuration
Environment variables (all optional, sane defaults): VariableDefaultDescriptionMORPHEUS_PROXY_PORT8083Port the proxy listens onMORPHEUS_ROUTER_URLhttp://localhost:8082Proxy-router URLMORPHEUS_COOKIE_PATH~/morpheus/.cookiePath to auth cookieMORPHEUS_SESSION_DURATION604800 (7 days)Session duration in secondsMORPHEUS_RENEW_BEFORE3600 (1 hour)Renew session this many seconds before expiryMORPHEUS_PROXY_API_KEYmorpheus-localBearer token for proxy auth
Session Duration
Sessions stake MOR tokens for their duration. Longer sessions = more MOR locked but fewer blockchain transactions: DurationMOR Staked (approx)Transactions1 hour~0.011 MOREvery hour1 day~0.274 MORDaily7 days~1.9 MORWeekly MOR is returned when the session closes or expires. The proxy auto-renews before expiry, so you get continuous inference with minimal staking overhead.
Health Check
curl http://127.0.0.1:8083/health
Available Models
curl http://127.0.0.1:8083/v1/models
Direct Usage (without OpenClaw)
curl http://127.0.0.1:8083/v1/chat/completions \ -H "Content-Type: application/json" \ -H "Authorization: Bearer morpheus-local" \ -d '{ "model": "kimi-k2.5", "messages": [{"role": "user", "content": "Hello!"}], "stream": false }'
Reliability Notes
kimi-k2.5 (non-web) is the most reliable model — recommended as primary fallback kimi-k2.5:web (web search variant) tends to timeout on P2P routing — avoid for fallback use Provider connection resets are transient — retries usually succeed The proxy itself runs as a KeepAlive launchd service — auto-restarts if it crashes
Proxy Resilience (v0.5)
v0.5 adds three critical improvements to the proxy that prevent prolonged outages caused by cooldown cascades — where both primary and fallback providers become unavailable simultaneously. Problem: Cooldown Cascades When a primary provider (e.g., Venice) returns a billing error, OpenClaw's failover engine marks that provider as "in cooldown." If the Morpheus proxy also returns errors that OpenClaw misclassifies as billing errors, both providers enter cooldown and the agent goes completely offline — sometimes for 6+ hours. Fix 1: OpenAI-Compatible Error Classification The proxy now returns errors in the exact format OpenAI uses, with proper type and code fields: { "error": { "message": "Morpheus session unavailable: ...", "type": "server_error", "code": "morpheus_session_error", "param": null } } Key distinction: All Morpheus infrastructure errors are typed as "server_error" — never "billing" or "rate_limit_error". This ensures OpenClaw treats them as transient failures and retries appropriately, instead of putting the provider into extended cooldown. Error codes returned by the proxy: CodeMeaningmorpheus_session_errorFailed to open or refresh a blockchain sessionmorpheus_inference_errorProvider returned an error during inferencemorpheus_upstream_errorConnection error to the proxy-routertimeoutInference request exceeded the time limitmodel_not_foundRequested model not in MODEL_MAP Fix 2: Automatic Session Retry When the proxy-router returns a session-related error (expired, invalid, not found, closed), the proxy now: Invalidates the cached session Opens a fresh blockchain session Retries the inference request once This handles the common case where the proxy-router restarts and loses its in-memory session state, or when a long-running session expires mid-request. Fix 3: Multi-Tier Fallback Chain Configure OpenClaw with multiple fallback models across providers: { "agents": { "defaults": { "model": { "primary": "venice/claude-opus-4-6", "fallbacks": [ "venice/claude-opus-45", // Try different Venice model first "venice/kimi-k2-5", // Try yet another Venice model "morpheus/kimi-k2.5" // Last resort: decentralized inference ] } } } } This way, if the primary model has billing issues, OpenClaw tries other models on the same provider (which may have separate rate limits) before falling back to Morpheus. The cascade is: venice/claude-opus-4-6 (primary) → billing error venice/claude-opus-45 (fallback 1) → tries a different model on Venice venice/kimi-k2-5 (fallback 2) → tries open-source model on Venice morpheus/kimi-k2.5 (fallback 3) → decentralized inference, always available if MOR is staked
13. OpenClaw Integration (v0.2)
Configure OpenClaw to use Morpheus as a fallback provider so your agent keeps running when primary API credits run out.
Step 1: Add Morpheus Provider
Add to your openclaw.json via config patch or manual edit: { "models": { "providers": { "morpheus": { "baseUrl": "http://127.0.0.1:8083/v1", "apiKey": "morpheus-local", "api": "openai-completions", "models": [ { "id": "kimi-k2.5", "name": "Kimi K2.5 (via Morpheus)", "reasoning": true, "input": ["text"], "cost": { "input": 0, "output": 0, "cacheRead": 0, "cacheWrite": 0 }, "contextWindow": 131072, "maxTokens": 8192 }, { "id": "kimi-k2-thinking", "name": "Kimi K2 Thinking (via Morpheus)", "reasoning": true, "input": ["text"], "cost": { "input": 0, "output": 0, "cacheRead": 0, "cacheWrite": 0 }, "contextWindow": 131072, "maxTokens": 8192 }, { "id": "glm-4.7-flash", "name": "GLM 4.7 Flash (via Morpheus)", "reasoning": false, "input": ["text"], "cost": { "input": 0, "output": 0, "cacheRead": 0, "cacheWrite": 0 }, "contextWindow": 131072, "maxTokens": 8192 } ] } } } }
Step 2: Set as Fallback
Configure a multi-tier fallback chain (recommended since v0.5): { "agents": { "defaults": { "model": { "primary": "venice/claude-opus-4-6", "fallbacks": [ "venice/claude-opus-45", // Different model, same provider "venice/kimi-k2-5", // Open-source model, same provider "morpheus/kimi-k2.5" // Decentralized fallback ] }, "models": { "venice/claude-opus-45": { "alias": "Claude Opus 4.5" }, "venice/kimi-k2-5": { "alias": "Kimi K2.5" }, "morpheus/kimi-k2.5": { "alias": "Kimi K2.5 (Morpheus)" }, "morpheus/kimi-k2-thinking": { "alias": "Kimi K2 Thinking (Morpheus)" }, "morpheus/glm-4.7-flash": { "alias": "GLM 4.7 Flash (Morpheus)" } } } } } ⚠️ Why multi-tier? A single fallback creates a single point of failure. If both the primary provider and the single fallback enter cooldown simultaneously (e.g., billing error triggers cooldown on both), your agent goes offline. Multiple fallback tiers across different models and providers ensure at least one path remains available.
Step 3: Add Auth Profiles
OpenClaw supports multiple API keys per provider with automatic rotation. When one key's credits run out (billing error), OpenClaw disables that key only and rotates to the next one — same model, fresh credits. This is the single most effective way to prevent downtime. Single Key (Minimum Setup) Add to ~/.openclaw/agents/main/agent/auth-profiles.json: { "venice:default": { "type": "api_key", "provider": "venice", "key": "VENICE-INFERENCE-KEY-YOUR_KEY_HERE" }, "morpheus:default": { "type": "api_key", "provider": "morpheus", "key": "morpheus-local" } } Multiple Keys (Recommended — v0.9.1) If you have multiple Venice API keys (e.g., from different accounts or plans), add them all as separate profiles. Order them from most credits to least: auth-profiles.json: { "version": 1, "profiles": { "venice:key1": { "type": "api_key", "provider": "venice", "key": "VENICE-INFERENCE-KEY-YOUR_PRIMARY_KEY" }, "venice:key2": { "type": "api_key", "provider": "venice", "key": "VENICE-INFERENCE-KEY-YOUR_SECOND_KEY" }, "venice:key3": { "type": "api_key", "provider": "venice", "key": "VENICE-INFERENCE-KEY-YOUR_THIRD_KEY" }, "morpheus:default": { "type": "api_key", "provider": "morpheus", "key": "morpheus-local" } } } openclaw.json — register the profiles and set explicit rotation order: { "auth": { "profiles": { "venice:key1": { "provider": "venice", "mode": "api_key" }, "venice:key2": { "provider": "venice", "mode": "api_key" }, "venice:key3": { "provider": "venice", "mode": "api_key" }, "morpheus:default": { "provider": "morpheus", "mode": "api_key" } }, "order": { "venice": ["venice:key1", "venice:key2", "venice:key3"] } } } ⚠️ auth.order is critical. Without it, OpenClaw uses round-robin (oldest-used first), which may not match your credit balances. With an explicit order, keys are tried in the exact sequence you specify — highest credits first. How Multi-Key Rotation Works OpenClaw's auth engine handles rotation automatically: Session stickiness: A key is pinned per session to keep provider caches warm. It won't flip-flop mid-conversation. Billing disable: When a key returns a billing/credit error, that profile is disabled with exponential backoff (starts at 5 hours). Other profiles for the same provider remain active. Rotation on failure: After disabling a profile, OpenClaw immediately tries the next key in auth.order. Same model, same provider — just fresh credits. Model fallback: Only after ALL profiles for Venice are disabled does OpenClaw move to the next model in the fallback chain (e.g., Morpheus). Auto-recovery: Disabled profiles auto-recover after backoff expires. If credits refill (e.g., daily reset), the profile becomes available again. Venice DIEM Credits Venice uses "DIEM" as its internal credit unit (1 DIEM ≈ $1 USD). Each API key has its own DIEM balance. Credits appear to reset daily. Expensive models drain credits faster: ModelInput CostOutput Cost~Messages per 10 DIEMClaude Opus 4.66 DIEM/M tokens30 DIEM/M tokens~5-10Claude Opus 4.56 DIEM/M tokens30 DIEM/M tokens~5-10Kimi K2.50.75 DIEM/M tokens3.75 DIEM/M tokens~50-100GLM 4.7 Flash0.125 DIEM/M tokens0.5 DIEM/M tokens~500+ Tip: With multiple keys, the agent can stay on Claude Opus across key rotations. Without multi-key, it would fall to cheaper models or Morpheus after one key's credits run out.
Failover Behavior (v0.9.1)
The complete failover chain with multi-key rotation: Key rotation within Venice — Key 1 credits exhausted → billing disable on that profile only → immediately rotates to Key 2 → Key 3 → etc. Same model, fresh credits. Model fallback — Only after ALL Venice keys are disabled → tries venice/claude-opus-45 (all keys again) → venice/kimi-k2-5 (all keys) → morpheus/kimi-k2.5 Morpheus fallback — The proxy auto-opens a 7-day Morpheus session (if none exists). Inference routes through the Morpheus P2P network. Gateway Guardian v4 — If all providers enter cooldown despite multi-key rotation → classifies error (billing vs transient) → billing: backs off + notifies owner (restart is useless for empty credits) → transient: restarts gateway (clears cooldowns) → nuclear reinstall if needed. Proactively monitors Venice DIEM balance. Auto-recovery — When credits refill (daily reset) or backoff expires, OpenClaw switches back to Venice automatically. Example with 6 keys (246 DIEM total): venice:key1 (98 DIEM) → venice:key2 (50 DIEM) → venice:key3 (40 DIEM) → venice:key4 (26 DIEM) → venice:key5 (20 DIEM) → venice:key6 (12 DIEM) → morpheus/kimi-k2.5 (owned, staked MOR) → mor-gateway/kimi-k2.5 (community gateway) v0.5 improvement: The Morpheus proxy returns "server_error" type errors (not billing errors), so OpenClaw won't put the Morpheus provider into extended cooldown due to transient infrastructure issues. If a Morpheus session expires mid-request, the proxy automatically opens a fresh session and retries once.
Venice Key Health Monitor (v2.0)
OpenClaw's billing error detection has pattern gaps with Venice-specific error messages. Two known gaps: Balance depletion: Venice returns "Insufficient USD or Diem balance to complete request" but OpenClaw checks for "insufficient balance" (adjacent words). Since "USD or Diem" separates "insufficient" from "balance", the pattern fails. Per-key spend limit: Venice returns "API key DIEM spend limit exceeded. Your account may still have DIEM balance, but this API key has reached its configured DIEM spending limit." — OpenClaw has no pattern for "spend limit" at all. Both get classified as "unknown" instead of "billing", the key gets a 60-second cooldown instead of a billing disable, and the same exhausted key gets retried in a loop. Two scripts fix this at the skill level: 1. Proactive Key Health Monitor (venice-key-monitor.sh) Periodically probes every Venice API key's DIEM/USD balance via a cheap GLM-4.7-Flash inference call (costs ~0.0001 DIEM). Reads the x-venice-balance-diem or x-venice-balance-usd response header and disables depleted keys by writing disabledUntil + disabledReason: "billing" directly to auth-profiles.json. # Check all keys and disable depleted ones bash skills/everclaw/scripts/venice-key-monitor.sh # Report balances without making changes bash skills/everclaw/scripts/venice-key-monitor.sh --status # Custom depletion threshold (default: 1 DIEM) bash skills/everclaw/scripts/venice-key-monitor.sh --threshold 5 Cron: Runs every 2 hours. Pre-empts the problem before the agent ever tries an empty key. 2. Reactive 402 Watchdog (venice-402-watchdog.sh) Monitors auth-profiles.json for Venice keys with rapid failures that aren't properly billing-disabled (the telltale sign of OpenClaw's pattern gap). When detected, immediately disables the offending key and identifies the next healthy key. # One-shot scan (check recent failures) bash skills/everclaw/scripts/venice-402-watchdog.sh # Run as daemon (continuous monitoring every 30s) bash skills/everclaw/scripts/venice-402-watchdog.sh --daemon Cron: Runs every 5 minutes. Catches billing errors in near-real-time that the proactive monitor might miss between its 2-hour checks. Detection Patterns (what OpenClaw misses) Venice ErrorOpenClaw PatternMatch?Insufficient USD or Diem balance to complete request"insufficient balance"❌ No — words not adjacentAPI key DIEM spend limit exceeded(none)❌ No pattern exists402 Payment Required/status.*402/✅ Only if status code preservedInsufficient credits"insufficient credits"✅ The watchdog catches the first two patterns (the most common Venice billing errors) that OpenClaw's text matching misses. State Files FilePurpose~/.openclaw/logs/venice-key-balances.jsonLast balance check results per key~/.openclaw/logs/venice-402-state.jsonLast watchdog action and rotation state~/.openclaw/logs/venice-key-monitor.logMonitor activity log~/.openclaw/logs/venice-402-watchdog.logWatchdog activity log
14. Gateway Guardian v5 (v2026.2.21)
A self-healing, billing-aware watchdog that monitors the OpenClaw gateway and its ability to run inference. Runs every 2 minutes via launchd.
Evolution
VersionWhat it checkedFatal flawv1HTTP dashboard aliveProviders in cooldown = brain-dead but HTTP 200v2Raw provider URLsProvider APIs always return 200 regardless of internal statev3Through-OpenClaw inference probeBilling exhaustion → restart → instant re-disable = dead loop. Also: set -e + pkill self-kill = silent no-op restartsv4Through-OpenClaw + billing classification + credit monitoringopenclaw agent injected 71K workspace prompt into every probev5Direct curl inference probes + billing classification + credit monitoringCurrent version
What v5 Fixes Over v4
Root cause: openclaw agent injected the full 71K workspace system prompt into every health probe. This caused mor-gateway/glm-5 to timeout at 60s (takes ~37s just for the prompt). Worse, failures were delivered to Signal as normal agent replies — spamming the user with error messages. Fix: Direct curl to gateway's LiteLLM proxy with a tiny prompt (~50 chars). Uses glm-4.7-flash (fast, lightweight) instead of glm-5. No agent session = no Signal delivery on failure. Errors stay in logs only.
What v4 Fixed Over v3
Billing-aware escalation — Classifies inference errors as billing vs transient vs timeout. Billing errors trigger backoff + notification instead of useless restarts. Silent restart bug — Replaced set -euo pipefail with set -uo pipefail + explicit ERR trap. Restart failures are now logged instead of silently exiting. pkill self-kill — Hard restart now iterates PIDs and excludes the Guardian's own PID. No more accidentally killing the watchdog. Proactive credit monitoring — Checks Venice DIEM balance via x-venice-balance-diem response header every 10 min. Warns when balance drops below threshold. DIEM reset awareness — Calculates hours to midnight UTC (when Venice DIEM resets daily). When billing-dead, enters 30-min backoff instead of hammering every 2 min. Auto-clears when UTC day rolls over. Signal notifications — Notifies owner on: billing exhaustion (with ETA to reset), billing recovery, nuclear restart, and total failure.
How It Works
Billing backoff gate — If in billing-dead state, check if midnight UTC has passed. If yes, re-probe. If no, skip this run (30-min intervals). Credit monitoring — Every 10 min, makes a cheap Kimi K2.5 call to Venice and reads the x-venice-balance-diem response header. Warns below 15 DIEM. Circuit breaker — Kills sub-agents stuck >30 min with repeated timeouts. HTTP probe — Is the gateway process running? Inference probe — Can the agent run inference through the full stack? Error classification — Parses probe output: billing → 402, Insufficient DIEM/USD/balance → don't restart, enter billing backoff, notify owner transient → auth cooldown without billing keywords → restart (clears cooldown) timeout → probe timed out → restart unknown → restart (safe default) Four-stage restart escalation (for non-billing errors only): openclaw gateway restart (graceful — resets cooldown state) Hard kill (excludes own PID) → launchd KeepAlive launchctl kickstart -k 🔴 NUCLEAR: curl -fsSL https://clawd.bot/install.sh | bash
Recommended Config
Pair with reduced billing backoff in openclaw.json to minimize downtime: { "auth": { "cooldowns": { "billingBackoffHoursByProvider": { "venice": 1 }, "billingMaxHours": 6, "failureWindowHours": 12 } } }
Installation
Included in install-proxy.sh, or manually: cp skills/everclaw/scripts/gateway-guardian.sh ~/.openclaw/workspace/scripts/ chmod +x ~/.openclaw/workspace/scripts/gateway-guardian.sh # Install launchd plist (macOS) # See templates/ai.openclaw.guardian.plist ⚠️ Important: The launchd plist should include OPENCLAW_GATEWAY_TOKEN in its environment variables.
Manual Test
bash ~/.openclaw/workspace/scripts/gateway-guardian.sh --verbose
Logs
tail -f ~/.openclaw/logs/guardian.log
Configuration
VariableDefaultDescriptionGATEWAY_PORT18789Gateway port to probePROBE_TIMEOUT8HTTP timeout in secondsINFERENCE_TIMEOUT45Agent probe timeoutFAIL_THRESHOLD2HTTP failures before restartINFERENCE_FAIL_THRESHOLD3Inference failures before escalation (~6 min)BILLING_BACKOFF_INTERVAL1800Seconds between probes when billing-dead (30 min)CREDIT_CHECK_INTERVAL600Seconds between Venice DIEM balance checks (10 min)CREDIT_WARN_THRESHOLD15DIEM balance warning thresholdMAX_STUCK_DURATION_SEC1800Circuit breaker: kill sub-agents stuck >30 minSTUCK_CHECK_INTERVAL300Circuit breaker check interval (5 min)OWNER_SIGNAL+1XXXXXXXXXXSignal number for notificationsSIGNAL_ACCOUNT+1XXXXXXXXXXSignal sender account
State Files
FilePurpose~/.openclaw/logs/guardian.stateHTTP failure counter~/.openclaw/logs/guardian-inference.stateInference failure counter~/.openclaw/logs/guardian-circuit-breaker.stateCircuit breaker timestamp~/.openclaw/logs/guardian-billing.stateBilling exhaustion start timestamp (0 = healthy)~/.openclaw/logs/guardian-billing-notified.stateWhether owner was notified (0/1)~/.openclaw/logs/guardian-credit-check.stateLast credit check timestamp~/.openclaw/logs/guardian.logGuardian activity log
15. Smart Session Archiver (v0.9.4)
OpenClaw stores every conversation as a .jsonl file in ~/.openclaw/agents/main/sessions/. Over time, these accumulate — and when the dashboard loads, it parses all session history into the DOM. At ~17MB (134+ sessions), browsers hit "Page Unresponsive" because the renderer chokes on thousands of chat message elements.
The Problem
The bottleneck isn't raw memory — Chrome gives each tab 1.4-4GB of V8 heap. The real limit is DOM rendering performance. Chrome Lighthouse warns at 800 DOM nodes and errors at 1,400. A hundred sessions with tool calls, code blocks, and long conversations easily generate 5,000+ DOM elements. The browser's layout engine can't keep up. Sessions Dir SizeDashboard Behavior< 5 MB✅ Loads instantly5-10 MB⚡ Slight delay, usable10-15 MB⚠️ Sluggish, noticeable lag15-20 MB🔴 "Page Unresponsive" likely20+ MB💀 Dashboard won't load
Solution: Size-Triggered Archiving
Instead of archiving on a fixed schedule (which may fire too early or too late depending on usage), the session archiver monitors the actual size of the sessions directory and only moves files when they exceed a threshold. Default threshold: 10MB — provides good headroom before hitting the ~15MB danger zone, without firing unnecessarily on light usage days.
Usage
# Archive if over threshold (default 10MB) bash skills/everclaw/scripts/session-archive.sh # Check size without archiving bash skills/everclaw/scripts/session-archive.sh --check # Force archive regardless of size bash skills/everclaw/scripts/session-archive.sh --force # Detailed output bash skills/everclaw/scripts/session-archive.sh --verbose
What It Protects
The archiver never moves: Active sessions — referenced in sessions.json (the index file) Guardian health probe — guardian-health-probe.jsonl Recent sessions — keeps the 5 most recent by modification time (configurable via KEEP_RECENT) Everything else gets moved to sessions/archive/ — not deleted. You can always move files back if needed.
Configuration
VariableDefaultDescriptionARCHIVE_THRESHOLD_MB10Trigger threshold in MBSESSIONS_DIR~/.openclaw/agents/main/sessionsSessions directory pathKEEP_RECENT5Number of recent sessions to always keep
Cron Integration
Set up a cron job that runs the archiver periodically. The script is a no-op when under threshold, so it's safe to run frequently: { "name": "Smart session archiver", "schedule": { "kind": "cron", "expr": "0 */6 * * *", "tz": "America/Chicago" }, "sessionTarget": "isolated", "payload": { "kind": "agentTurn", "model": "morpheus/kimi-k2.5", "message": "Run the smart session archiver: bash skills/everclaw/scripts/session-archive.sh --verbose. Report the results. If sessions were archived, mention the before/after size.", "timeoutSeconds": 60 } } Recommended: every 6 hours. Frequent enough to catch growth spurts, cheap enough to run on the LIGHT tier since it's a no-op most of the time.
Output
The script outputs a JSON summary for programmatic consumption: {"archived":42,"freedMB":8.2,"beforeMB":12.4,"afterMB":4.2,"threshold":10}
Why 10MB?
Based on real-world testing: 134 sessions totaling 17MB caused "Page Unresponsive" in Chrome, Safari, and Brave on macOS. The dashboard uses a standard web renderer that parses all session JSONL into DOM elements — there's no virtualization or lazy loading. 10MB gives ~50% headroom before the ~15-20MB danger zone where most browsers start struggling.
17. x402 Payment Client (v0.7)
Everclaw v0.7 includes an x402 payment client that lets your agent make USDC payments to any x402-enabled endpoint. The x402 protocol is an HTTP-native payment standard: when a server returns HTTP 402, your agent automatically signs a USDC payment and retries.
How x402 Works
Agent → request → Server returns 402 + PAYMENT-REQUIRED header Agent → parse requirements → sign EIP-712 payment → retry with PAYMENT-SIGNATURE header Server → verify signature via facilitator → settle USDC → return resource
CLI Usage
# Make a request to an x402-protected endpoint node scripts/x402-client.mjs GET https://api.example.com/data # Dry-run: see what would be paid without signing node scripts/x402-client.mjs --dry-run GET https://api.example.com/data # Set max payment per request node scripts/x402-client.mjs --max-amount 0.50 GET https://api.example.com/data # POST with body node scripts/x402-client.mjs POST https://api.example.com/task '{"prompt":"hello"}' # Check daily spending node scripts/x402-client.mjs --budget
Programmatic Usage
import { makePayableRequest, createX402Client } from './scripts/x402-client.mjs'; // One-shot request const result = await makePayableRequest("https://api.example.com/data"); // result.paid → true if 402 was handled // result.amount → "$0.010000" (USDC) // result.body → response content // Reusable client with budget limits const client = createX402Client({ maxPerRequest: 0.50, // $0.50 USDC max per request dailyLimit: 5.00, // $5.00 USDC per day dryRun: false, }); const res = await client.get("https://agent-api.example.com/query?q=weather"); const data = await client.post("https://agent-api.example.com/task", { prompt: "hello" }); // Check spending console.log(client.budget()); // { date: "2026-02-11", spent: "$0.520000", remaining: "$4.480000", limit: "$5.000000", transactions: 3 }
Payment Flow Details
Request — Standard HTTP request to any URL 402 Detection — Server returns HTTP 402 with PAYMENT-REQUIRED header containing JSON payment requirements Budget Check — Verifies amount against per-request max ($1.00 default) and daily limit ($10.00 default) EIP-712 Signing — Signs a TransferWithAuthorization (EIP-3009) for USDC on Base using the agent's wallet Retry — Resends the request with PAYMENT-SIGNATURE header containing the signed payment payload Settlement — The Coinbase facilitator verifies the signature and settles the USDC transfer Response — Server returns the requested resource
Security
Private key from 1Password at runtime (never on disk) — follows Bagman patterns Budget controls prevent runaway spending: $1/request max, $10/day by default Dry-run mode for testing without signing or spending USDC on Base only — no other chains or tokens (EIP-3009 TransferWithAuthorization) Daily budget tracking persisted to .x402-budget.json (amounts only, no keys)
Key Addresses
ItemAddressUSDC (Base)0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913Coinbase Facilitatorhttps://api.cdp.coinbase.com/platform/v2/x402Base Chain ID8453 (CAIP-2: eip155:8453)
18. ERC-8004 Agent Registry (v0.7)
The ERC-8004 protocol provides on-chain registries for agent discovery and trust. Everclaw v0.7 includes a reader that queries the Identity and Reputation registries on Base mainnet.
What Is ERC-8004?
ERC-8004 defines three registries: Identity Registry (ERC-721): Each agent is an NFT with a tokenURI pointing to a registration file containing name, description, services/endpoints, x402 support, and trust signals Reputation Registry: Clients give structured feedback (value + tags) to agents. Summary scores aggregate across all clients Validation Registry: Stake-secured re-execution and zkML verification (read-only in Everclaw) Agents are discoverable, portable (transferable NFTs), and verifiable across organizational boundaries.
CLI Usage
# Look up an agent by ID node scripts/agent-registry.mjs lookup 1 # Get reputation data node scripts/agent-registry.mjs reputation 1 # Full discovery (identity + registration file + reputation) node scripts/agent-registry.mjs discover 1 # List agents in a range node scripts/agent-registry.mjs list 1 10 # Get total registered agents node scripts/agent-registry.mjs total
Programmatic Usage
import { lookupAgent, getReputation, discoverAgent, totalAgents, listAgents } from './scripts/agent-registry.mjs'; // Look up identity const agent = await lookupAgent(1); // { // agentId: 1, // owner: "0x89E9...", // uri: "data:application/json;base64,...", // wallet: "0x89E9...", // registration: { // name: "ClawNews", // description: "Hacker News for AI agents...", // services: [{ name: "web", endpoint: "https://clawnews.io" }, ...], // x402Support: false, // active: true, // supportedTrust: ["reputation"] // } // } // Get reputation const rep = await getReputation(1); // { // agentId: 1, // clients: ["0x3975...", "0x718B..."], // feedbackCount: 2, // summary: { count: 2, value: "100", decimals: 0 }, // feedback: [{ client: "0x3975...", value: "100", tag1: "tip", tag2: "agent" }, ...] // } // Full discovery const full = await discoverAgent(1); // Combines identity, registration file, services, and reputation into one object
Registration File Format
Agent registration files (resolved from tokenURI) follow the ERC-8004 standard: { "type": "https://eips.ethereum.org/EIPS/eip-8004#registration-v1", "name": "MyAgent", "description": "What the agent does", "image": "https://example.com/logo.png", "services": [ { "name": "web", "endpoint": "https://myagent.com" }, { "name": "A2A", "endpoint": "https://agent.example/.well-known/agent-card.json", "version": "0.3.0" }, { "name": "MCP", "endpoint": "https://mcp.agent.eth/", "version": "2025-06-18" } ], "x402Support": true, "active": true, "supportedTrust": ["reputation", "crypto-economic"] } The reader handles all URI types: data: URIs (base64-encoded JSON stored on-chain), ipfs:// URIs (via public IPFS gateway), and https:// URIs.
Contract Addresses (Base Mainnet)
RegistryAddressIdentity0x8004A169FB4a3325136EB29fA0ceB6D2e539a432Reputation0x8004BAa17C55a88189AE136b182e5fdA19dE9b63 ⚠️ Same addresses on all EVM chains — Ethereum, Base, Arbitrum, Polygon, Optimism, Linea, Avalanche, etc. The Identity Registry does NOT implement totalSupply(), so totalAgents() uses a binary search via ownerOf().
Combining x402 + Agent Registry
The x402 client and agent registry work together for agent-to-agent payments: import { discoverAgent } from './scripts/agent-registry.mjs'; import { makePayableRequest } from './scripts/x402-client.mjs'; // 1. Discover an agent and find its x402-enabled endpoint const agent = await discoverAgent(42); const apiEndpoint = agent.services.find(s => s.name === "A2A")?.endpoint; // 2. Make a paid request — x402 handling is automatic if (agent.x402Support && apiEndpoint) { const result = await makePayableRequest(apiEndpoint, { method: "POST", headers: { "Content-Type": "application/json" }, body: JSON.stringify({ task: "Analyze this data..." }), maxAmount: 500000n, // $0.50 USDC }); console.log(result.body); // Agent's response }
Quick Reference (v2026.2.23)
ActionCommandInstall Everclawbash skills/everclaw/scripts/install-everclaw.shCheck for updatesbash skills/everclaw/scripts/install-everclaw.sh --checkUpdate (git pull)cd skills/everclaw && git pullInstall routerbash skills/everclaw/scripts/install.shInstall proxy + guardianbash skills/everclaw/scripts/install-proxy.shStart routerbash skills/everclaw/scripts/start.shStop routerbash skills/everclaw/scripts/stop.shSwap ETH→MORbash skills/everclaw/scripts/swap.sh eth 0.01Swap USDC→MORbash skills/everclaw/scripts/swap.sh usdc 50Open sessionbash skills/everclaw/scripts/session.sh open <model> [duration]Close sessionbash skills/everclaw/scripts/session.sh close <session_id>List sessionsbash skills/everclaw/scripts/session.sh listSend promptbash skills/everclaw/scripts/chat.sh <model> "prompt"Check balancebash skills/everclaw/scripts/balance.shProxy healthcurl http://127.0.0.1:8083/healthGuardian testbash scripts/gateway-guardian.sh --verboseGuardian logstail -f ~/.openclaw/logs/guardian.logVenice key healthbash skills/everclaw/scripts/venice-key-monitor.sh --statusVenice key balancesbash skills/everclaw/scripts/venice-key-monitor.sh --verboseVenice 402 watchdogbash skills/everclaw/scripts/venice-402-watchdog.sh --verboseArchive sessionsbash skills/everclaw/scripts/session-archive.shCheck session sizebash skills/everclaw/scripts/session-archive.sh --checkForce archivebash skills/everclaw/scripts/session-archive.sh --forcex402 requestnode scripts/x402-client.mjs GET <url>x402 dry-runnode scripts/x402-client.mjs --dry-run GET <url>x402 budgetnode scripts/x402-client.mjs --budgetLookup agentnode scripts/agent-registry.mjs lookup <id>Agent reputationnode scripts/agent-registry.mjs reputation <id>Discover agentnode scripts/agent-registry.mjs discover <id>List agentsnode scripts/agent-registry.mjs list <start> [count]Total agentsnode scripts/agent-registry.mjs totalScan a skillnode security/skillguard/src/cli.js scan <path>Batch scannode security/skillguard/src/cli.js batch <dir>Security auditbash security/clawdstrike/scripts/collect_verified.shDetect injectionpython3 security/prompt-guard/scripts/detect.py "text"
15. Security Skills (v0.3)
Everclaw agents handle MOR tokens and private keys — making them high-value targets. v0.3 bundles four security skills to defend against supply chain attacks, prompt injection, credential theft, and configuration exposure.
🔍 SkillGuard — Pre-Install Skill Scanner
Scans AgentSkill packages for malicious patterns before you install them. Detects credential theft, code injection, prompt manipulation, data exfiltration, and evasion techniques. # Scan a skill directory node security/skillguard/src/cli.js scan <path> # Batch scan all installed skills node security/skillguard/src/cli.js batch <directory> # Scan a ClawHub skill by slug node security/skillguard/src/cli.js scan-hub <slug> Score interpretation: 80-100 ✅ LOW risk — safe to install 50-79 ⚠️ MEDIUM — review before installing 20-49 🟠 HIGH — significant concerns 0-19 🔴 CRITICAL — do NOT install When to use: Before installing any skill from ClawHub or untrusted sources. Run batch scans periodically to audit all installed skills. Full docs: security/skillguard/SKILL.md
🔒 ClawdStrike — Config & Exposure Audits
Security audit and threat model for OpenClaw gateway hosts. Verifies configuration, network exposure, installed skills/plugins, and filesystem hygiene. Produces an OK/VULNERABLE report with evidence and remediation steps. # Run a full audit cd security/clawdstrike && \ OPENCLAW_WORKSPACE_DIR=$HOME/.openclaw/workspace \ bash scripts/collect_verified.sh What it checks: Gateway bind address and auth configuration Channel exposure (Signal, Telegram, Discord, etc.) Installed skills and plugins for known vulnerabilities Filesystem permissions and sensitive file access Network exposure and firewall rules OpenClaw version and known CVEs When to use: After initial setup, after installing new skills, and periodically (weekly recommended). Full docs: security/clawdstrike/SKILL.md
🧱 PromptGuard — Prompt Injection Defense
Advanced prompt injection defense system with multi-language detection (EN/KO/JA/ZH), severity scoring, automatic logging, and configurable security policies. Connects to the HiveFence distributed threat intelligence network. # Analyze a message for injection attempts python3 security/prompt-guard/scripts/detect.py "suspicious message here" # Run audit on prompt injection logs python3 security/prompt-guard/scripts/audit.py # Analyze historical logs python3 security/prompt-guard/scripts/analyze_log.py Detection categories: Direct injection (instruction overrides, role manipulation) Indirect injection (data exfiltration, hidden instructions) Jailbreak attempts (DAN mode, filter bypasses) Multi-language attacks (cross-language injection) When to use: In group chats, when processing untrusted input, when agents interact with external data sources. Full docs: security/prompt-guard/SKILL.md
💰 Bagman — Secure Key Management
Secure key management for AI agents handling private keys, API secrets, and wallet credentials. Covers secure storage patterns, session keys, leak prevention, prompt injection defense specific to financial operations, and MetaMask Delegation Framework (EIP-7710) integration. Key principles: Never store keys on disk — use 1Password op run for runtime injection Session keys — generate ephemeral keys with limited permissions Delegation Framework — grant agents scoped authority without exposing master keys Leak prevention — patterns to detect and block secret exposure Reference docs: security/bagman/references/secure-storage.md — Storage patterns security/bagman/references/session-keys.md — Session key architecture security/bagman/references/delegation-framework.md — EIP-7710 integration security/bagman/references/leak-prevention.md — Leak detection rules security/bagman/references/prompt-injection-defense.md — Financial-specific injection defense When to use: Whenever an agent handles private keys, wallet credentials, or API secrets — which Everclaw agents always do. Full docs: security/bagman/SKILL.md
Security Recommendations
For Everclaw agents handling MOR tokens: Before installing any new skill: Run SkillGuard scan After setup and periodically: Run ClawdStrike audit In group chats or with untrusted input: Enable PromptGuard detection Always: Follow Bagman patterns for key management (1Password, session keys, no keys on disk)
16. Model Router (v0.6)
A lightweight, local prompt classifier that routes requests to the cheapest capable model. Runs in <1ms with zero external API calls.
Tiers
TierPrimary ModelFallbackUse CaseLIGHTmorpheus/glm-4.7-flashmorpheus/kimi-k2.5Cron jobs, heartbeats, simple Q&A, status checksSTANDARDmorpheus/kimi-k2.5venice/kimi-k2-5Research, drafting, summaries, most sub-agent tasksHEAVYvenice/claude-opus-4-6venice/claude-opus-45Complex reasoning, architecture, formal proofs, strategy All LIGHT and STANDARD tier models run through Morpheus (inference you own via staked MOR). Only HEAVY tier uses Venice (premium).
How Scoring Works
The router scores prompts across 13 weighted dimensions: DimensionWeightWhat It DetectsreasoningMarkers0.20"prove", "theorem", "step by step", "chain of thought"codePresence0.14function, class, import, backticks, "refactor"synthesis0.11"summarize", "compare", "draft", "analyze", "review"technicalTerms0.10"algorithm", "architecture", "smart contract", "consensus"multiStepPatterns0.10"first...then", "step 1", numbered listssimpleIndicators0.08"what is", "hello", "weather" (negative score → pushes toward LIGHT)agenticTask0.06"edit", "deploy", "install", "debug", "fix"creativeMarkers0.04"story", "poem", "brainstorm"questionComplexity0.04Multiple question markstokenCount0.04Short prompts skew LIGHT, long prompts skew HEAVYconstraintCount0.04"at most", "at least", "maximum", "budget"domainSpecificity0.04"quantum", "zero-knowledge", "genomics"outputFormat0.03"json", "yaml", "table", "csv" Special override: 2+ reasoning keywords in the user prompt → force HEAVY at 88%+ confidence. This prevents accidental cheap routing of genuinely hard problems. Ambiguous prompts (low confidence) default to STANDARD — the safe middle ground.
CLI Usage
# Test routing for a prompt node scripts/router.mjs "What is 2+2?" # → LIGHT (morpheus/glm-4.7-flash) node scripts/router.mjs "Summarize the meeting notes and draft a follow-up" # → STANDARD (morpheus/kimi-k2.5) node scripts/router.mjs "Design a distributed consensus algorithm and prove its correctness" # → HEAVY (venice/claude-opus-4-6) # JSON output for programmatic use node scripts/router.mjs --json "Build a React component" # Pipe from stdin echo '{"prompt":"hello","system":"You are helpful"}' | node scripts/router.mjs --stdin
Programmatic Usage
import { route, classify } from './scripts/router.mjs'; const decision = route("Check the weather in Austin"); // { // tier: "LIGHT", // model: "morpheus/glm-4.7-flash", // fallback: "morpheus/kimi-k2.5", // confidence: 0.87, // score: -0.10, // signals: ["short (7 tok)", "simple (weather)"], // reasoning: "score=-0.100 → LIGHT" // }
Applying to Cron Jobs
Set the model field on cron job payloads to route to cheaper models: { "payload": { "kind": "agentTurn", "model": "morpheus/kimi-k2.5", // STANDARD tier — owned via Morpheus "message": "Compile a morning briefing...", "timeoutSeconds": 300 } } For truly simple cron jobs (health checks, pings, status queries): { "payload": { "kind": "agentTurn", "model": "morpheus/glm-4.7-flash", // LIGHT tier — fastest, owned "message": "Check proxy health and report any issues", "timeoutSeconds": 60 } }
Applying to Sub-Agent Spawns
// Simple research task → STANDARD sessions_spawn({ task: "Search for X news", model: "morpheus/kimi-k2.5" }); // Quick lookup → LIGHT sessions_spawn({ task: "What's the weather?", model: "morpheus/glm-4.7-flash" }); // Complex analysis → let it use the default (HEAVY / Claude 4.6) sessions_spawn({ task: "Design the x402 payment integration..." });
Cost Impact
With the router in place, only complex reasoning tasks in the main session use premium models. All background work (cron jobs, sub-agents, heartbeats) runs on Morpheus inference you own: BeforeAfterAll cron jobs → Claude 4.6 (premium)Cron jobs → Kimi K2.5 / GLM Flash (owned)All sub-agents → Claude 4.6 (premium)Sub-agents → Kimi K2.5 (owned) unless complexMain session → Claude 4.6Main session → Claude 4.6 (unchanged)
19. Morpheus API Gateway Bootstrap (v0.8)
The Morpheus API Gateway (api.mor.org) provides community-powered, OpenAI-compatible inference — no node, no staking, no wallet required. Everclaw v0.8 includes a bootstrap script that configures this as an OpenClaw provider, giving new users instant access to AI from the first launch.
Why This Matters
New OpenClaw users face a cold-start problem: they need an API key (Claude, OpenAI, etc.) before their agent can do anything. Everclaw v0.8 solves this by bundling a community API key for the Morpheus inference marketplace, which is currently in open beta. The bootstrap flow: New user installs OpenClaw + Everclaw Run node scripts/bootstrap-gateway.mjs — agent gets inference immediately Agent's first task: guide user to get their own key at app.mor.org User upgrades to their own key → can then progress to full Morpheus node + MOR staking
Quick Start
# One command — tests the gateway and patches OpenClaw config node skills/everclaw/scripts/bootstrap-gateway.mjs # Or with your own API key from app.mor.org node skills/everclaw/scripts/bootstrap-gateway.mjs --key sk-YOUR_KEY_HERE # Test the gateway connection node skills/everclaw/scripts/bootstrap-gateway.mjs --test # Check current gateway status node skills/everclaw/scripts/bootstrap-gateway.mjs --status
What It Does
The bootstrap script: Tests the Morpheus API Gateway connection with a live inference call Patches openclaw.json to add mor-gateway as a new provider Adds mor-gateway/kimi-k2.5 to the fallback chain Reports available models and next steps
API Gateway Details
SettingValueBase URLhttps://api.mor.org/api/v1API formatOpenAI-compatibleAuthBearer token (sk-...)Open betaUntil March 1, 2026Models34 (LLMs, TTS, STT, embeddings)Provider namemor-gateway
Available Models (via Gateway)
The gateway exposes all models on the Morpheus inference marketplace: ModelTypeNoteskimi-k2.5LLMPrimary bootstrap model — strong coding + reasoningglm-4.7-flashLLMFast, good for simple tasksllama-3.3-70bLLMGeneral purposeqwen3-235bLLMLarge, strong reasoninggpt-oss-120bLLMOpenAI-compatible OSS modelhermes-4-14bLLMLightweighttts-kokoroTTSText-to-speechwhisper-v3-large-turboSTTSpeech-to-texttext-embedding-bge-m3EmbeddingText embeddings All models also have :web variants with web search capability.
OpenClaw Config (generated by bootstrap)
{ "models": { "providers": { "mor-gateway": { "baseUrl": "https://api.mor.org/api/v1", "apiKey": "sk-...", "api": "openai-completions", "models": [ { "id": "kimi-k2.5", "name": "Kimi K2.5 (via Morpheus Gateway)", "reasoning": false }, { "id": "glm-4.7-flash", "name": "GLM 4.7 Flash (via Morpheus Gateway)", "reasoning": false }, { "id": "llama-3.3-70b", "name": "Llama 3.3 70B (via Morpheus Gateway)", "reasoning": false } ] } } } } Important: All gateway models must have "reasoning": false — the upstream litellm rejects the reasoning_effort parameter.
Community Bootstrap Key
The bootstrap script includes a community API key (base64-obfuscated) for the SmartAgentProtocol account. This provides open access during the beta period. Getting your own key (recommended): Go to app.mor.org Create an account and sign in Click "Create API Key" Enable "session automation" in account settings (required for API access) Run: node scripts/bootstrap-gateway.mjs --key YOUR_KEY
Gateway vs Local Proxy vs P2P Node
FeatureAPI Gateway (v0.8)Local Proxy (v0.2)P2P Node (v0.1)SetupOne commandInstall proxy + configFull node installCostOpen (beta)Own (MOR staking)Own (MOR staking)Requires MORNoYesYesRequires walletNoYesYesDecentralizedGateway → providersDirect P2PDirect P2PBest forNew users, quick startDaily use, reliabilityFull sovereignty The recommended progression: Gateway → Local Proxy → P2P Node as users gain confidence with the Morpheus ecosystem.
Fallback Chain with Gateway
With the gateway added, the recommended fallback chain becomes: venice/claude-opus-4-6 # Primary (premium) → venice/claude-opus-45 # Venice fallback → venice/kimi-k2-5 # Venice open tier → morpheus/kimi-k2.5 # Local proxy (MOR staking) → mor-gateway/kimi-k2.5 # API Gateway (open beta) For new users without Venice or a local proxy, the gateway is the first and only provider — making it the critical bootstrap path.
20. Always-On Setup for 24/7 Operation (v0.9.9)
Your agent needs your Mac to stay awake. macOS defaults to sleep after inactivity, which interrupts cron jobs, heartbeats, and long-running tasks. Everclaw includes an always-on setup script that configures power management for continuous operation.
Quick Setup
# Configure macOS to never sleep (requires sudo) sudo bash skills/everclaw/scripts/always-on.sh # Restore default power settings sudo bash skills/everclaw/scripts/always-on.sh --restore
What It Does
The script configures macOS power management for 24/7 operation: SettingValuePurposedisablesleep1System never sleepsstandby0No hibernationautopoweroff0No deep sleeppowernap1Network activity while display offwomp1Wake on LAN enabled (remote access)autorestart1Auto-restart after power failuretcpkeepalive1Keep network connections alivedisksleep0Never spin down disks
LaunchAgent for Caffeinate
The script also installs a LaunchAgent (com.everclaw.alwayson) that runs caffeinate -i -d -s in the background, providing an additional layer of protection against system sleep: -i — Prevent system from idling to sleep -d — Prevent display from sleeping -s — Prevent system from sleeping when on AC power
Verify It's Working
# Check current power settings pmset -g # Should show: # SleepDisabled 1 # standby 0 # autorestart 1
Why This Matters for Agents
Without always-on configuration: Cron jobs don't fire while sleeping Heartbeats miss their schedule Long-running tasks (file transfers, backups) fail Your agent appears "offline" to other agents/users With always-on: Cron jobs fire on schedule Heartbeats run every 30 minutes like clockwork Long tasks complete uninterrupted Your agent is reachable 24/7
Power Consumption
A Mac Mini M4 at idle with sleep disabled draws ~6-10W. That's roughly: $0.50-1.00/month at $0.12/kWh Negligible compared to AI inference costs
Alternatives for Other Platforms
Linux: sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target Headless Raspberry Pi: No sleep by default. Ensure systemd services are enabled for OpenClaw and Morpheus.
Troubleshooting
Mac still sleeps: Check pmset -g assertions for any processes preventing sleep Verify LaunchAgent is loaded: launchctl list | grep everclaw Check Energy Saver settings in System Settings aren't overriding pmset Display still sleeps: This is fine — the system stays awake even with display off thanks to Power Nap. To disable display sleep entirely: sudo pmset -a displaysleep 0
21. Three-Shift Task Planning (v2026.2.21)
A structured task planning system that proposes prioritized work plans at the start of each 8-hour shift. Nothing executes without user approval.
Shifts
ShiftDefault TimeWindowCharacter☀️ Morning6:00 AM6 AM – 2 PMRamp-up: meetings, comms, decisions🌤️ Afternoon2:00 PM2 PM – 10 PMDeep work: coding, writing, building🌙 Night10:00 PM10 PM – 6 AMAutonomous: research, maintenance
How It Works
Gather context — Reads memory files, calendar, email, git status, previous shift handoff Generate plan — Prioritized tasks (P1 must-do, P2 should-do, P3 could-do), active project status, blocked items Present for approval — User approves, modifies, or skips before anything executes Execute — Works through approved tasks in priority order, logs progress Handoff — Writes shift summary for the next shift to pick up
Setup
# Create three cron jobs (adjust times to your timezone) openclaw cron add --name three-shifts-morning --schedule "0 6 * * *" \ --message "Generate morning shift plan. Read the three-shifts skill, gather context, and propose tasks for the 6 AM – 2 PM window." openclaw cron add --name three-shifts-afternoon --schedule "0 14 * * *" \ --message "Generate afternoon shift plan. Read the three-shifts skill, gather context, and propose tasks for the 2 PM – 10 PM window." openclaw cron add --name three-shifts-night --schedule "0 22 * * *" \ --message "Generate night shift plan. Read the three-shifts skill, gather context, and propose tasks for the 10 PM – 6 AM window."
Shift-Specific Rules
Morning/Afternoon: External actions (emails, PRs, messages) allowed with approval Night: Autonomous only — no external comms, no financial transactions, no destructive ops Night cancellation: If user doesn't approve by 10:30 PM, night shift is cancelled See three-shifts/SKILL.md for full documentation including approval workflows, configuration options, weekend behavior, and quiet hours.
2026.2.21
Three-Shift Task Planning — Morning/Afternoon/Night shift system with prioritized task proposals and approval workflow Gateway Guardian v5 — Direct curl inference probes replace openclaw agent probes. Eliminates 71K workspace prompt injection into health checks, prevents Signal spam from failed probes, uses glm-4.7-flash for fast lightweight probing Version scheme change — Moved from semver (0.9.x) to date-based versioning (YYYY.M.DD)
0.9.9
Always-on 24/7 power configuration for macOS GLM-5 as default model (replaces Kimi K2.5)
0.9.8.3
Community contributions (dynamic model discovery, install.sh fixes, bash 3.2 compat, agent integration docs)
References
references/acquiring-mor.md — How to get MOR tokens (exchanges, bridges, swaps) references/models.md — Available models and their blockchain IDs references/api.md — Complete proxy-router API reference references/economics.md — How MOR staking economics work references/troubleshooting.md — Common errors and solutions security/skillguard/SKILL.md — SkillGuard full documentation security/clawdstrike/SKILL.md — ClawdStrike full documentation security/prompt-guard/SKILL.md — PromptGuard full documentation security/bagman/SKILL.md — Bagman full documentation x402 Protocol — HTTP-native payment protocol specification ERC-8004 — Trustless Agents EIP specification 8004scan — Agent registry explorer
Category context
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Docs3 Config
- SKILL.md
- CHANGELOG.md
- README.md
- templates/openclaw-config-gateway-only.json
- templates/openclaw-config-linux.json
- templates/openclaw-config-mac.json