This page is a mirror summary, last verified for v7.0.0. For canonical Everclaw guidance, see everclaw.xyz.
Pattern
The skill thinks it’s calling a local OpenAI-compatible API. The C-Node handles wallets, sessions, and routing on the back end.Setup steps
Run a C-Node
Follow C-Node setup. Bind
:8082 to loopback only.Approve some MOR allowance once
See “Approve once” in C-Node setup.
Pre-open a session (optional)
Some agent skills want a stable session for the run. Open one and pass the
sessionId to the skill via env var.Configure the skill
Set the skill’s OpenAI-base-URL to
http://127.0.0.1:8082 and inject Authorization: Basic <base64(user:pass)> and session_id: <sessionId> headers per request. See your skill’s docs for the exact env names.Permissions
Run agents under a separateproxy.conf user with a method whitelist. For an Everclaw skill that only needs chat completions plus session lifecycle:
Failure modes to plan for
- Provider unreachable — agent should retry, then the C-Node closes the stuck session and returns the unused MOR.
- Session expired mid-task — agent should detect 401/403/429 from the C-Node and re-open a session.
- Allowance exhausted —
approvemore MOR (see C-Node setup) or set up a top-up cron.
Related
- Everclaw ecosystem mirror — broader context, links.
- Running local agents — generalized agent patterns.

