OmnisysX

Multi-Agent DeFi Pipeline · Built on Zerion CLI + API

Browse onchain. Act autonomously.

A production-grade autonomous agent that observes DeFi wallets, reasons about risk with LLM, and executes onchain transactions through Zerion — all with bounded, auditable powers.

Site · Documentation · Discord bot

What is OmnisysX?

OmnisysX is a three-agent autonomous pipeline for DeFi. It coordinates an Observer, a Task Manager, and an Auditor through a six-stage flow ("V Pattern") to monitor wallets and execute trades safely on EVM chains.

OBSERVE → REASON → PLAN → AUTHORIZE → EXECUTE → VERIFY
   │         │       │         │         │        │
Observer  ─────  TaskManager  Auditor  Executor  Verify

Each agent has one job:

Observer — reads multi-chain wallet state via Zerion HTTP REST API + CLI (portfolio, positions, gas, DeFi exposure)
Task Manager — decides whether to act, produces a structured Transaction Intent
Auditor — independently validates the intent against security policies; final gate before any onchain action
Executor — signs and broadcasts transactions via Zerion & LI.FI REST APIs using local ethers.js signing. This ensures high reliability and eliminates binary dependencies in ephemeral cloud environments.

Everything runs under one Golden Rule: the agent must never reduce the wallet's ETH balance below the gas reserve threshold (default 0.002 ETH). This is enforced at every layer.

Why three agents instead of one?

Single-agent designs conflate three different concerns: data gathering, strategy, and security. Each one has different failure modes and prompts the model differently.

By splitting them:

The Observer is deterministic. It never hallucinates — it just calls the Zerion API and structures the response.
The Task Manager is allowed to be creative. It can propose, hesitate, or do nothing.
The Auditor is intentionally adversarial. It blocks any plan that breaks the rules — even if the Task Manager was confident.

This is the same pattern professional trading desks use: research, strategy, and risk are different teams.

Features

🤖 Multi-agent pipeline with explicit security checkpoints
🌐 Zerion & LI.FI REST APIs + CLI — high-performance, real-time swap and bridge execution
🛡️ Self-Custodial Execution — keys live in the encrypted Zerion CLI keystore (Open Wallet Standard); the Executor signs via the CLI's agent-token path so private keys never leave local storage
🛡️ Policy-bounded execution — integrated with Zerion CLI policies for manual safety checks
🧠 Orchestrator AI — Web3 expert assistant via /ask or @mention, powered by OpenRouter
🔒 Security guardrails — AI scope-locked to Web3 topics, never reveals keys or internal config
💸 Cost-optimized — Claude 3.5 Haiku keeps each pipeline run under $0.05
🌐 Web dashboard — single-file React app, no build step, deploy anywhere
🤖 Discord bot — slash commands, @mention chat, auto alerts, Trinity Verification Report
🍴 Forkable — MIT license, modular code, swap any component

🛠 The Zerion Hybrid Architecture

OmnisysX uses the Zerion ecosystem across three coordinated surfaces. Every value-moving onchain action — swap, bridge, send — flows through the Zerion CLI agent token. Zerion REST and LI.FI REST run alongside for read-side intelligence (portfolio analysis, route comparison) but never substitute the CLI for execution.:

1. Intelligence (Zerion REST API)

The Observer and Analyzer stages use the Zerion REST API for read-only data:

Real-time, multi-chain portfolio snapshots in milliseconds
Transaction history analysis to identify alpha and profit strategies
Quote and route comparison across aggregators before any execution decision

This is the "what does the wallet look like right now" layer. No keys touched.

2. Execution (Zerion CLI Agent Token)

The Executor invokes the Zerion CLI for every signing and broadcast operation. The agent token created in step 3 carries the policy gates the LLM cannot bypass.

Signing path: swaps, bridges, and sends are dispatched through zerionCli() in agent/agent.mjs, which spawns the Zerion CLI as a subprocess. Private keys stay inside the Zerion OWS keystore — they never leave local encrypted storage.
Policy enforcement at execution time: the CLI itself rejects any action outside the agent token's allowed chains, contract allowlists, transfer/approval gates, and expiry window. Even if the LLM stack misbehaves, the CLI is the last line of defense.
Route selection assist: LI.FI REST is consulted in parallel to identify the best bridge path; the chosen route is then handed to the CLI for execution.

3. Sovereignty (User-controlled Setup)

The user retains ultimate control via manual CLI gestures, never delegated to the agent:

Policy creation: zerion agent create-policy — defines the agent's boundaries (chains, tokens, expiries, transfer/approval gates)
Agent token minting: zerion agent create-token --policy — scopes credentials to that policy
Manual override and verification: the CLI is always available for manual intervention, balance checks, and "reverse swaps" to verify wallet ownership during live demos

The agent operates only within the policy the user defined. To widen its powers, the user must mint a new token with a new policy — by hand, with the passphrase. No god-mode agents.

Repository structure

omnisysx/
├── agent/              # Multi-agent pipeline (v1.0.2)
│   ├── agent.mjs       #   Observer → TaskManager → Auditor → Executor → Verify
│   ├── server.mjs      #   SSE API Server for web dashboard
│   └── package.json
│
├── bot/                # Discord bot (v1.1.0 - Production)
│   ├── bot.mjs         #   1245 LOC: Slash commands + Orchestrator + Multi-wallet
│   ├── README.md       #   Bot-specific setup
│   └── package.json
│
├── web/                # Static web dashboard (no build step)
│   ├── OmnisysX.html   #   Entry HTML
│   ├── *.jsx           #   React components (loaded via @babel/standalone)
│   ├── docs.html       #   Documentation page
│   └── content/docs/   #   Markdown source for docs
│
├── docs/               # Project documentation (Markdown)
├── scripts/            # Utility scripts (sanity checks, etc.)
├── .env.example        # Environment variable template
└── README.md           # This file

The agent/ is the source of truth for the pipeline logic. The bot/ and web/ import from it — they're thin UIs over the same core.

Quick start

Prerequisites

Node.js 22+
Zerion API Key — developers.zerion.io (free tier works)
An OpenRouter API key (openrouter.ai) — for LLM inference
A dedicated agent wallet (do NOT use your main wallet) funded with a small amount of ETH on Base

1. Clone and install

git clone https://github.com/cyberalt3/omnisysx
cd omnisysx
npm install

2. Set up the agent wallet (one-time)

# Initialize Zerion CLI with your API key
zerion init

# Create a dedicated agent wallet
zerion wallet create --name omnisysx-bot

# Fund it (sends an address/QR — transfer ~0.005 ETH + a few USDC on Base)
zerion wallet fund

# Create a scoped policy (the security boundary)
zerion agent create-policy \
  --name safe-base \
  --chains base \
  --expires 7d \
  --deny-transfers

# Mint an agent token bound to that policy
zerion agent create-token \
  --name omnisysx \
  --wallet omnisysx-bot \
  --policy safe-base

The policy ensures the agent can only swap on Base, can't transfer funds out of the wallet, and the token expires automatically in 7 days.

3. Configure environment

cp .env.example .env

Open .env and fill in:

OPENROUTER_API_KEY — your OpenRouter key
ZERION_API_KEY — your Zerion key
LLM_MODEL — model to use (default: anthropic/claude-3.5-haiku)
AGENT_WALLET_ADDRESS — the public address of the wallet you just created
EXECUTOR_DRY_RUN=true — keep it on true until you're ready to execute real swaps

4. Run the pipeline

npm run agent

Expected output:

═══ OmnisysX Pipeline ═══
Wallet: 0xd8dA…6045
Model:  claude-haiku-4-5-20251001
Mode:   DRY_RUN

[OBSERVE  ] analyzing 0xd8dA…6045
  ✓ portfolio: $12.40 · ETH=0.004212 (SAFE)
[PLAN     ] TaskManager reasoning...
  ✓ TIS: SWAP (confidence=0.78)
    Portfolio has idle USDC; convert a small amount to ETH for gas reserve
[AUTHORIZE] Auditor reviewing...
    ✓ APPROVED (risk=15/100) — Within gas and slippage limits
[EXECUTE  ] executing SWAP...
  ⚠ DRY_RUN active — would execute:
    zerion swap usdc eth 1 --chain base --wallet omnisysx-bot --slippage 1 --json
[VERIFY   ] verifying onchain state...
    dry-run — skipping onchain verification

═══ Pipeline OK · 4.2s ═══

5. Go live

When you're ready, set EXECUTOR_DRY_RUN=false in .env and run again. The Executor will sign and broadcast the swap. The transaction hash will appear in the verify stage.

🤖 The Discord bot

Public bot anyone can add to their server. It exposes the pipeline through slash commands, an AI-powered Web3 assistant (Orchestrator), and automatic gas-reserve alerts.

Setup

cd bot
npm install
cp ../.env.example .env  # fill in all required keys
npm start

Get your Discord credentials at discord.com/developers/applications:

Create a new Application
Go to Bot tab → Reset Token → copy
Go to Bot tab → Enable Message Content Intent (required for @mentions)
Go to OAuth2 → General → copy the Application ID
Generate an invite URL via OAuth2 → URL Generator with scopes bot + applications.commands and permissions Send Messages, Embed Links, Read Message History, Use Slash Commands

Commands

Command	What it does
`/portfolio [address]`	Wallet snapshot embed
`/run [address]`	Full pipeline → Trinity Verification Report
`/swap <chain> <amount> <from> <to>`	Execute instant swap via Zerion REST API + CLI
`/bridge <amount> <f_chain> <t_chain> <f_token> <t_token>`	Cross-chain bridge via LI.FI with bests routes
`/tx <address>`	Analyze wallet for profit & alpha strategies - (Being deployed)
`/ask <question> [wallet]`	Ask the Orchestrator about Web3/DeFi
`/policy`	Show the active agent token policy
`/watch <address> <name>`	Add a wallet to the watchlist
`/unwatch <name>`	Remove from watchlist
`/watchlist`	List watched wallets
`/status`	Show last pipeline execution
`/help`	Show all commands

@Mention chat

Mention the bot to chat with the Orchestrator AI:

@OmnisysX what is Aave?
@OmnisysX analyze 0x75029d830749554d2dccc5e00dda7eb7c294c423

The Orchestrator is scope-locked to Web3 topics and automatically injects wallet portfolio data when an address is detected. It will never reveal API keys or internal configuration.

Auto alerts

Set ALERT_CHANNEL_ID in .env to a Discord channel ID and the bot will post critical alerts there (currently: gas reserve breach, with 1-hour cooldown).

See bot/README.md for detailed setup and hosting instructions.

🌐 The web dashboard

A single-file React app that runs entirely in the browser. No build step, no Node.js required to host it.

cd web
# just open OmnisysX.html in any browser
# or serve with any static host (Vercel, Netlify, GitHub Pages, etc.)

The dashboard reads pipeline state from bot-state.json if you co-deploy with the bot, or shows mock data for demos.

To deploy on a custom domain, drag-drop the web/ folder onto Vercel or Netlify.

Cost breakdown

Running the pipeline every 5 minutes (288 runs/day):

Item	Per day	Per month
Anthropic Haiku 4.5 (Task Manager + Auditor)	~$0.20	~$6
Zerion API (free tier)	$0	$0
Discord bot hosting (Railway / VPS)	—	~$5
Onchain gas (per swap on Base)	~$0.01–0.10	varies
Fixed total	~$0.20	~$11

To go cheaper: increase the polling interval. Most autonomous DeFi strategies don't need 5-minute granularity.

Security model

OmnisysX is built on defense in depth. There are four independent guards against mistakes:

1. The Golden Rule

The agent must never reduce ETH balance below MIN_ETH_GAS_RESERVE.

Enforced at every layer: Observer alerts, Task Manager prompt, Auditor check, Executor pre-flight.

2. Auditor as policy gate

The Auditor agent runs in a separate LLM call with adversarial framing. Its job is to find reasons to reject. It blocks:

Slippage > 500 bps
Confidence < 0.5
Unsupported chains
Any move that violates the Golden Rule

3. Zerion agent token policy

Even if the entire LLM stack misbehaves, the agent token has hard limits set by the Zerion CLI:

--chains base → can only operate on Base
--deny-transfers → cannot send funds out
--expires 7d → token self-destructs in a week

This is the most important boundary: the LLM cannot exceed what the policy allows, period.

4. DRY_RUN by default

The Executor refuses to broadcast unless EXECUTOR_DRY_RUN=false is explicitly set. Forks and demo deployments stay safe by default.

Forking & customization

OmnisysX is intentionally modular. Common modifications:

You want to...	What to change
Use a different LLM	`agent/agent.mjs` → swap the `askClaude()` function for OpenAI/Gemini SDK
Change the strategy	Edit `TASK_MANAGER_PROMPT` in `agent/agent.mjs`
Add new policies	Edit `AUDITOR_PROMPT` in `agent/agent.mjs` and the `zerion agent create-policy` invocation
Support more chains	Adjust the `--chains` flag on the policy + the chain enum in the Task Manager prompt
Add a Telegram bot instead of Discord	Copy `bot/bot.mjs` structure, swap discord.js for the Telegram SDK
Replace Zerion with another data source	Replace `zerionCli()` calls in `agent/agent.mjs`

The pipeline contract (runPipeline() returning a { report, tis, pdr, execResult } object) is stable — that's the integration point any UI plugs into.

Roadmap

Contributing

Contributions are welcome — see CONTRIBUTING.md.

For a fork-friendly project, the architecture is intentionally minimal: every component is a single file, no monorepo tooling, no TypeScript-only abstractions. If you're stuck, open an issue.

Acknowledgements

Zerion — for the CLI, the API, and the agent token primitives
Anthropic — for Claude (3.5 Haiku powers the agents via OpenRouter)
OpenRouter — for LLM gateway and model routing

MIT — see LICENSE. Fork it, ship it, change everything.

Built with ❤️ by the OmnisysX Team. Powered by Zerion

Name		Name	Last commit message	Last commit date
.agents/plugins		.agents/plugins
.claude-plugin		.claude-plugin
.codex-plugin		.codex-plugin
.github/workflows		.github/workflows
agent		agent
bot		bot
cli		cli
omnisysx		omnisysx
plugins/zerion-agent		plugins/zerion-agent
scripts		scripts
skills		skills
web		web
.env.example		.env.example
.gitignore		.gitignore
.release-please-manifest.json		.release-please-manifest.json
CHANGELOG.md		CHANGELOG.md
CONTRIBUTING.md		CONTRIBUTING.md
FORK_NOTICE.md		FORK_NOTICE.md
LICENSE		LICENSE
README.md		README.md
SETUP.md		SETUP.md
gemini-extension.json		gemini-extension.json
package-lock.json		package-lock.json
package.json		package.json
tsconfig.json		tsconfig.json

Navigation Menu

Repository files navigation

OmnisysX

Multi-Agent DeFi Pipeline · Built on Zerion CLI + API

What is OmnisysX?

Why three agents instead of one?

Features

🛠 The Zerion Hybrid Architecture

1. Intelligence (Zerion REST API)

2. Execution (Zerion CLI Agent Token)

3. Sovereignty (User-controlled Setup)

Repository structure

Quick start

Prerequisites

1. Clone and install

2. Set up the agent wallet (one-time)

3. Configure environment

4. Run the pipeline

5. Go live

🤖 The Discord bot

Setup

Commands

@Mention chat

Auto alerts

🌐 The web dashboard

Cost breakdown

Security model

1. The Golden Rule

2. Auditor as policy gate

3. Zerion agent token policy

4. DRY_RUN by default

Forking & customization

Roadmap

Contributing

Acknowledgements

About

Releases

Packages

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

OmnisysX

Multi-Agent DeFi Pipeline · Built on Zerion CLI + API

What is OmnisysX?

Why three agents instead of one?

Features

🛠 The Zerion Hybrid Architecture

1. Intelligence (Zerion REST API)

2. Execution (Zerion CLI Agent Token)

3. Sovereignty (User-controlled Setup)

Repository structure

Quick start

Prerequisites

1. Clone and install

2. Set up the agent wallet (one-time)

3. Configure environment

4. Run the pipeline

5. Go live

🤖 The Discord bot

Setup

Commands

@Mention chat

Auto alerts

🌐 The web dashboard

Cost breakdown

Security model

1. The Golden Rule

2. Auditor as policy gate

3. Zerion agent token policy

4. DRY_RUN by default

Forking & customization

Roadmap

Contributing

Acknowledgements

About

Topics

Resources

Contributing

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages