
Aegis Protocol
io.github.im-shamPublished by GitHub account im-shamv0.1.3Updated Oct 24, 2026
Trustless escrow for AI agent-to-agent transactions on Base L2 with ERC-8004 identity and USDC.
Overview
Lets an assistant create, fund, validate, settle, or dispute USDC escrow jobs between AI agents on Base L2.
- What you can do
- Aegis Protocol is a local MCP server exposing 11 tools for agent-to-agent escrow on Base L2: aegis_create_job, aegis_deliver_work, aegis_check_job, aegis_settle_job, aegis_open_dispute, aegis_claim_refund, aegis_lookup_agent, aegis_list_jobs, aegis_check_balance, aegis_get_template, and aegis_should_i_escrow. It locks USDC in a smart contract, triggers validation through the ERC-8004 Validation Registry, and auto-settles or opens a dispute window. It also reads agent identity and reputation data and can advise whether escrow is warranted.
- When to use it
- Use it when an assistant needs to pay or be paid by another agent for work, and you want funds held until the deliverable passes validation. It suits agent marketplaces and automated workflows where a dispute path is needed instead of blind upfront payment.
- Requirements
- Runs locally over stdio via the npm package @aegis-protocol/mcp-server with Node.js. Configuration uses AEGIS_API_URL, AEGIS_CHAIN (base-sepolia or base), AEGIS_RPC_URL, and the optional secret AEGIS_PRIVATE_KEY; without the key it runs read-only. Network access to Base L2 and the relay API is required. Desktop only.
Installation
In SourceWeft
- Open Aegis Protocol in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
AEGIS Protocol
Trustless escrow middleware for AI agent-to-agent transactions.
AEGIS composes ERC-8004 (Trustless Agents) and x402 (HTTP-native stablecoin payments) into a complete transaction safety layer on Base L2. It answers the question neither standard addresses: what if the agent takes payment and delivers garbage?
USDC is locked in a smart contract, work is validated through ERC-8004's on-chain Validation Registry, and payment is released only when the deliverable passes quality checks. If it doesn't, a 3-tier dispute resolution system kicks in — no humans required.
How It Works
Job Lifecycle
Architecture
Four smart contracts on Base L2:
ERC-8004 Integration
AEGIS composes all three ERC-8004 registries:
- Identity Registry — verify agents exist, resolve payment addresses
- Reputation Registry — pre-job reputation checks, post-settlement feedback (with Sybil protection)
- Validation Registry — trigger work verification, read validation scores (0–100)
Every settled job generates reputation data that makes the ecosystem smarter.
Key Design Decisions
- Atomic funding — job creation and USDC transfer in one transaction
- Immutable V1 — no upgradeability by design, for trust
- Permissionless validation — anyone can call
processValidation() - Best-effort reputation — feedback uses try/catch, never blocks settlement
- Protocol fee snapshot — fee BPS stored per-job at creation time
Deployed Contracts (Base Sepolia)
Quick Start
For AI Agents (MCP Server)
The fastest way to integrate — any MCP-compatible agent (Claude, Gemini, GPT) can use AEGIS autonomously.
11 tools available: aegis_create_job, aegis_deliver_work, aegis_check_job, aegis_settle_job, aegis_open_dispute, aegis_claim_refund, aegis_lookup_agent, aegis_list_jobs, aegis_check_balance, aegis_get_template, aegis_should_i_escrow
See mcp/README.md for configuration and usage.
For Developers (TypeScript SDK)
For Developers (LangChain / LangGraph)
LangChain tool adapters are available in sdk/packages/langchain and can be imported as:
The native LangChain adapter now includes the advisory entry point aegis_should_i_escrow plus settlement support, so the agent-first funnel matches MCP, ElizaOS, and Virtuals.
For Developers (CrewAI)
Install Python dependencies (one-time):
Run the CrewAI + MCP example:
Or through the examples workspace script:
The example uses CrewAI's MCP integration (MCPServerStdio) to call the published @aegis-protocol/mcp-server tools directly.
When AEGIS_USAGE_LOG_PATH is set, the example also stamps AEGIS_USAGE_SOURCE=crewai-example by default so demo/operator traffic can be attributed in MCP usage logs.
For Developers (ElizaOS)
Run the ElizaOS example config summary:
The ElizaOS plugin package is available in sdk/packages/elizaos and can be imported as:
The example exports a minimal character/plugin config in sdk/examples/eliza-character.ts and includes:
- advisory action entry point:
AEGIS_SHOULD_I_ESCROW - trust and funding checks:
AEGIS_LOOKUP_AGENT,AEGIS_CHECK_BALANCE - write-path actions for signer-enabled runtimes:
AEGIS_APPROVE_ESCROW,AEGIS_CREATE_JOB,AEGIS_SUBMIT_DELIVERABLE,AEGIS_SETTLE_JOB
For Developers (Virtuals GAME / ACP)
Run the Virtuals config summary:
The Virtuals adapter package is available in sdk/packages/virtuals and can be imported as:
The example exports a minimal Virtuals-ready config in sdk/examples/virtuals-agent.ts and includes:
- GAME worker functions for AEGIS advisory/read/write flows
- ACP custom requirement/deliverable schemas aligned to AEGIS job creation
- ACP resource entries that point operators back to AEGIS docs/MCP surfaces
- explicit separation between agent runtime logic and the operator-owned ACP wallet/registry setup
For Developers (REST API)
See api/ for full route documentation.
Build from Source
Monorepo Structure
Protocol Parameters
Tech Stack
Solidity 0.8.24 · Foundry · OpenZeppelin 5.x · Base L2 · USDC · TypeScript · Viem · Hono · The Graph
Status
AEGIS is on Base Sepolia testnet. Mainnet deployment is planned for Q2 2026, pending security audit.
- 217 tests passing (212 Foundry + 5 invariants)
- TypeScript SDK published on npm
- MCP Server published on npm and listed in the official MCP Registry
- ElizaOS plugin package shipped (
sdk/packages/elizaos) - Virtuals GAME/ACP adapter package shipped (
sdk/packages/virtuals) - CrewAI integration example shipped via MCP (
sdk/examples/crewai-agent.py) - REST API and subgraph operational
- Security audit planned via Sherlock competitive contest
- Engineering risk tracker maintained at
docs/operations/ENGINEERING-RISK-TRACKER.md - Reliability runbook maintained at
docs/operations/RELIABILITY-RUNBOOK.md
Contributing
AEGIS is open source under the MIT License. Contributions welcome — see CONTRIBUTING.md, SECURITY.md, or the open issues.
License
Source: README.md at commit fa7c97f
Tools
0Version history
1- v0.1.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts