Skip to content

Quickstart

Five minutes from signup to a named, scoped, on-chain agent your IDE drives.

1. Sign up

Go to app.agensai.xyz, pick a name prefix (e.g., adrian), and complete the passkey ceremony.

This creates adrian-main.agensai.eth, your main account. It's a JAW smart account rooted in your passkey, recoverable on any device via keys.jaw.id. One biometric tap. Done.

2. Provision an orchestrator

In the dashboard, click Set up your AI's wallet. Pick a suffix (default orc).

This is one biometric tap that:

  • Mints adrian-orc.agensai.eth, the orchestrator's ENS name.
  • Generates a one-time pairing token.

The orchestrator holds the working float (anywhere from a few tens to a few hundred dollars typical). It's the wallet your AI agents spend from.

3. Pair the MCP

Copy the pair command from the dashboard. Paste it in your IDE chat (Claude Desktop, Cursor, or Codex):

npx agensai pair <token>

The pairing step:

  1. Generates the orchestrator key locally and stores it at ~/.agensai/orchestrator.key, mode 0600 (same plaintext-file pattern JAW uses for its own keystore).
  2. Redeems the one-time token at the dashboard.
  3. Auto-detects and writes MCP server config for Claude Desktop, Cursor, and Claude Code.
  4. Prints next-step instructions.

No biometric, no AGENSAI server holding your key.

See MCP lifecycle for what pair, serve, and disconnect do under the hood.

4. Restart your IDE

The MCP server is spawned by your IDE on launch. After pairing, full-quit Claude Desktop / Cursor / Claude Code and reopen so it picks up the new MCP entry.

5. Spawn your first agent

In your IDE chat:

Spin up alice with 50 USDC/day on Uniswap, expiring in 30 days.

Your IDE calls the create_agent MCP tool. Behind the scenes:

  • The MCP server generates a child ECDSA key.
  • Mints alice.agensai.eth via JustaName under the agensai.eth namespace.
  • The orchestrator signs an ERC-7715 grant to the child smart account address, scoped to USDC, Uniswap, 50/day, 30 days.
  • Stores the child key at ~/.agensai/agents/alice/, mode 0600.
  • Writes alice's status, permission, and parent into ENS text records.

Within ~10 seconds: alice.agensai.eth exists, on-chain, bounded.

Have alice swap 10 USDC for ETH on Uniswap.

The child key signs sendCalls with permissionId. The on-chain validator checks the call against the permission. If it's in scope, the bundle lands. If not, the validator reverts.

6. Inspect the fleet

Open app.agensai.xyz. Your orchestrator, agents, balances, and active permissions all read directly from ENS records. The dashboard is the source of truth for status; the chat is the source of action.

What's next