app.mor.org or MorpheusUI) and a full provider. You run your own C-Node (consumer-side proxy-router) and you typically host a small AI gateway so other tools — Everclaw skills, local agents, automation — can hit Morpheus through a single local endpoint with predictable auth.
Topology
Why prosumer?
- One stable endpoint for all your local agents to point at — no per-tool wallet juggling.
- Bring your own wallet with a real budget; agents can’t drain it without your permission (see API auth per-user whitelists).
- Mix local + remote — fall back to bundled
llama.cppfor free smoke tests; switch to remote Morpheus models for production tasks. - TEE on demand — when an agent needs higher trust, route through a
tee-tagged model.
What’s on this path
C-Node setup
Consumer-side proxy-router with persistent local API.
Gateway for Everclaw
Wire Everclaw / OpenClaw skills to your local C-Node.
Running local agents
BasicAuth + per-agent permission whitelists for safe automation.
API auth
proxy.conf, rpcauth/rpcwhitelist, multi-user setup.
