Quick Start

Connect the owner wallet and create the agent account

Sign in at app.projectaegis.ai and choose Set up new agent. Give the agent a name and choose a signer. If Aegis generates the low-privilege bot signer in your browser, download its provisional backup immediately. Your owner wallet key is never part of the agent handoff.

Apply guardrails

Set small per-transaction and daily limits for the assets the agent may use. The default path creates a dedicated policy; advanced users can select a compatible policy from the reusable Policy Library. Apply guardrails activates the policy, creates the agent-to-policy permission, mints its on-chain constraints, and records that permission as this agent's primary permission. If an agent has several valid permissions, Aegis asks you to choose one instead of guessing.

Fund the account and choose its route

The guardrail step carries its primary setup asset forward, so fund only what the agent needs without choosing that asset again. Direct is normally fastest for DeFi and asks for a small native-token balance on the generated signer. Bundler mode keeps the signer empty and uses EntryPoint prefund or a paymaster, but adds another provider and queueing hop; a responsive bundler can still include the operation in the same block. The Aegis public RPC works without provider setup but may be rate-limited. Custom RPC stays optional; when a custom provider endpoint also supports ERC-4337 v0.6, it can be used for both RPC and bundling, with a separate bundler field available when needed. The exact signed dry run proves the selected route, funding, and gas estimate before broadcast.

Download one agent handoff package

The browser builds one ZIP containing a manifest, public runtime descriptor, separate runtime secrets, optional signer file, safe first-action probe, and a START-HERE.md runbook. The package never includes your owner key or wallet-wide aegissa_ management key. Aegis keeps secrets in separate files inside the package so the agent can install them with restrictive permissions without asking the human to assemble paths by hand.

python3 -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install "aegis-smart-accounts>=0.5.0"

aegis handoff install /path/to/my-agent-aegis-handoff.zip \
  --destination ~/.aegis/handoffs/my-agent
aegis handoff check ~/.aegis/handoffs/my-agent

Installation verifies every file hash, rejects unsafe archive paths and links, writes secret-bearing files with mode 0600, and reports the exact runtime descriptor path.

Let the agent run its first check

Give the agent the ZIP path or installed handoff directory plus the agent runbook. The agent checks the package, explains its permission and route, and estimates the included minimal policy-compatible action without broadcasting. Import the resulting first-action.readiness.json report in guided setup to bring independently verified runtime evidence back into the dashboard. An unsafe beta override can produce diagnostic evidence, but it never produces a Ready state. Review and approve the first real action before the agent broadcasts it.