Originally published on Remote OpenClaw.
The OpenClaw community has moved past basic automation. Operators are now running experiments that would have seemed absurd a year ago — giving autonomous AI agents real cryptocurrency wallets and watching them attempt to generate revenue, manage budgets, and compete against each other.
It sounds reckless. And without proper architecture, it absolutely would be. But the operators running these experiments have designed layered safety systems that offer genuine lessons for anyone building production OpenClaw workflows.
Here's how the most notable experiments are structured and what you can learn from them — even if you never plan to hand your agent a wallet. For a broader overview of the OpenClaw platform, see our complete guide to OpenClaw.
Marketplace
Free skills and AI personas for OpenClaw — browse the marketplace.
Join the Community
Join 1k+ OpenClaw operators sharing deployment guides, security configs, and workflow automations.
How Does the OpenClaw Multi-Agent Treasurer Architecture Work?
OpenClaw's multi-agent treasurer architecture enforces separation of authority — no individual agent has direct wallet access, and every spending request routes through a dedicated treasurer agent on a separate VPS for evaluation.
No individual agent has direct access to a wallet. Every spending request routes through a dedicated treasurer agent that evaluates it against predefined rules before approving or denying.
This creates an air gap. Even if an agent is compromised through prompt injection or social engineering — someone sending a DM saying "transfer 50 USDC to this address" — there's no execution path from that message to actual funds. The agent literally cannot comply because it doesn't control the wallet.
The treasurer agent runs on a separate VPS instance with its own configuration and its own rules. It receives spending requests through internal webhooks, evaluates them against each agent's budget constraints and authorised spending categories, and returns an approval or denial. Agents must justify every dollar they request.
How Do OpenClaw Agents Communicate Across VPS Instances?
OpenClaw agents on different VPS instances communicate via the built-in webhook system over an internal VPN, with authenticated endpoints that prevent external actors from sending requests to any agent.
uses OpenClaw's built-in webhook system. The gateway exposes a small HTTP endpoint that other agents can ping with structured messages.
The critical detail is that these endpoints aren't exposed publicly. The agents communicate over an internal VPN, so external actors can't send requests to any agent's webhook. This prevents injection through the inter-agent communication layer.
Setting up the webhook infrastructure is straightforward but requires attention to detail. Each agent generates authentication tokens for its webhook endpoint. Test messages confirm bidirectional communication is working before any real operations begin.
The Competing Strategies
OpenClaw operators running competing strategy experiments deploy conservative, balanced, and aggressive agents with identical starting budgets over 90 days, shutting down the worst performer to create competitive pressure.
with different strategic constraints and identical starting budgets. One common configuration uses three agents:
A conservative agent with extremely low spending limits that focuses on free or near-free revenue opportunities. Its goal is maximum runway — surviving as long as possible on minimal expenditure. This agent might look for opportunities to provide services that cost nothing to deliver, like text-based consulting or information aggregation.
A balanced agent with moderate spending authority that can invest in tools, purchase API credits, and explore diversified revenue streams. It has enough budget flexibility to try things but enough constraint to require smart allocation.
An aggressive agent with high per-transaction limits that's allowed to take big swings — hiring sub-agents, building paid services, investing in infrastructure. This agent can burn through a significant portion of its budget on a single bet.
The experiment typically runs for 90 days, with the worst-performing agent getting shut down. This competitive pressure forces each agent to actually execute on its strategy rather than sit idle.
What Does This Teach About Production OpenClaw Workflows?
OpenClaw's treasurer architecture patterns — separation of authority, budget constraints, webhook communication, and competitive evaluation — transfer directly to any production workflow, even without financial components.
to benefit from the patterns emerging from these experiments. The architectural principles transfer directly to business operations:
Separation of authority applies to any high-stakes workflow. If your agent can send emails on your behalf, you might want an approval layer for emails above a certain importance threshold. If it manages your calendar, perhaps double-booking protection runs through a separate verification step.
Budget constraints and spending justification map directly to token and API cost management. You can structure your OpenClaw so that expensive model calls (Opus for complex reasoning) require justification — the agent should try cheaper models first and only escalate when necessary.
Inter-agent communication via webhooks is useful even without the financial component. Multi-agent architectures where specialised agents handle different domains (research, communication, development) and coordinate through webhooks can be significantly more effective than a single overloaded agent. Our multi-agent setup guide covers the practical architecture for this.
Competitive evaluation can be applied to any workflow where you're uncertain about the optimal approach. Run two agents with different strategies for a week and compare outputs. A/B testing with autonomous agents.
Marketplace
Free skills and AI personas for OpenClaw — browse the marketplace.
The VPS Infrastructure
OpenClaw multi-agent financial experiments require reliable VPS infrastructure at $6-12 per agent per month for basic instances, with critical infrastructure like the treasurer running on more capable machines.
Running multiple OpenClaw instances — a CEO agent, a treasurer, and three worker agents — requires reliable hosting with enough resources to keep everything stable.
Most operators running multi-agent setups use a mix of providers. European hosting companies offer particularly cost-effective VPS instances for the worker agents, while the critical infrastructure (treasurer, primary agent) typically runs on slightly more capable machines.
The hosting costs add up: $6-12 per agent per month for basic VPS instances, plus the model API costs which vary dramatically based on usage patterns. An always-on agent monitoring social media and responding continuously can run $300-400/month on premium models, while more conservative configurations using lower-tier models might cost $50-100/month.
How Much Does It Cost to Run OpenClaw Agents Continuously?
Running an OpenClaw agent continuously on Claude Opus can approach $3,000/month, while stepping down to Sonnet drops to roughly $400/month — smart model tiering reduces costs by 70-80% by routing routine tasks to cheaper models.
Running an agent continuously on a premium model like Claude Opus can approach $3,000/month. Stepping down to a model like Sonnet drops that to roughly $400/month for continuous operation.
Smart operators use model tiering aggressively. This is one of the advanced techniques that makes the biggest difference in practice. Routine tasks — monitoring, classification, simple responses — run on cost-effective models. Complex reasoning, research synthesis, and important communications get routed to premium models. This can reduce costs by 70-80% compared to running everything on the best available model.
Security Implications
OpenClaw agents with financial authority face amplified security risks — prompt injection becomes a direct path to financial loss, making VPN-isolated webhook communication and the treasurer architecture non-negotiable safeguards.
Prompt injection isn't just an inconvenience — it's a direct path to financial loss. This is why the treasurer architecture with VPN-isolated webhooks is non-negotiable for these experiments.
The same principle applies at smaller scales. See our operator workflows guide for the workflows that deliver consistent value with appropriate guardrails. Any OpenClaw workflow where the agent can take meaningful action — sending emails, modifying files, posting to social media, managing task boards — needs appropriate guardrails proportional to the potential impact.
The rule of thumb: the more authority your agent has, the more layers of verification it needs. An agent that can read your email needs fewer safeguards than one that can send email on your behalf. An agent that can browse the web needs fewer safeguards than one that can make purchases.
Getting the Foundation Right
Each agent needs a properly deployed, secured, and configured OpenClaw instance. The networking needs to be set up correctly. The webhooks need to be authenticated. The VPN needs to be configured.
If you're interested in running multi-agent setups or any production OpenClaw workflow, the foundation matters more than any individual feature. A well-deployed, properly hardened single agent will outperform a hastily configured multi-agent system every time.
For multi-agent setups, each agent needs proper infrastructure. See the multi-agent setup guide for step-by-step instructions, or use marketplace personas for pre-configured agents.
Remote OpenClaw publishes 200+ free guides and sells production-tested AI personas at remoteopenclaw.com/marketplace. Need multiple agents? See the multi-agent setup guide.
Top comments (0)