@corven/agentix
agentix
Local-first AI agent execution engine on Base Sepolia.
Quick Start
npx agentix setup
The setup wizard verifies your environment, creates local storage, configures an RPC endpoint (public by default — no key needed, optional provider key for higher limits), and auto-detects your AI harnesses (Claude Code, Cursor, Copilot, ...), wiring the AgentIX MCP server into each so tools work immediately.
What You Get
- ERC-4337 Smart Wallet — deterministic, session-key controlled
- Lightweight Sessions — daily spend limits, daily tx limits, expiry
- Credentials — Merkle-tree based, org-issued, ZK-provable
- Risk-Bound Execution — every action validated, simulated, risk-scored, explained
- Owner Policy — set spending limits once, agent operates freely within bounds
- MCP Integration — 69 tools for Claude Code, Cursor, Copilot, MimoCode, OpenCode
Commands
agentix setup # Interactive wizard (RPC + MCP auto-wiring)
agentix connect # Detect harnesses & wire in AgentIX MCP tools
agentix init # Initialize local runtime (non-interactive)
agentix doctor # Full system diagnostics (12 points)
agentix health # Quick health check
agentix wallet create # Create agent wallet
agentix session create # Create lightweight session
agentix cred issue # Issue credential
agentix fund --amount 10 # Get fiat on-ramp options
agentix protocol # Protocol documentation
MCP (for AI Agents)
agentix setup and agentix connect auto-wire the MCP server into every
detected harness. To start it manually:
npx agentix-mcp
Architecture
Local-first. No cloud. SQLite at ~/.agentix/db/. Config at ~/.agentix/config/. Every action goes through: Parse -> Validate -> Resolve -> Policy -> Simulate -> Risk Score -> Explain -> Execute.
Set AGENTIX_HOME to relocate the data directory (defaults to ~/.agentix).
Security
The optional API server (used by the dashboard) binds to 127.0.0.1 only and has
no authentication — it trusts every local caller. Do not expose port 3001 to
a network. Any local process or browser page can reach it and trigger writes.
Private keys, when configured, are read from the AGENTIX_PRIVATE_KEY / PRIVATE_KEY
environment variables — never commit them.
Known advisories
snarkjs (ZK proving) pulls transitive dev-tooling deps (bfj/jsonpath/underscore,
ws, @ethersproject v5) with published DoS-class advisories. These are not reachable
from the proving path used at runtime (groth16.fullProve); the top-level ethers is v6.
They resolve once upstream snarkjs updates its dependency tree.