Wallets and names for every agent^*autonomous.

Name: AGENSAI
Author: AGENSAI

Your chat is the UI. One MCP connects Claude, Cursor, or ChatGPT to JAW, and suddenly you're launching fleets of onchain agents by talking. Each agent gets an ENS identity, a wallet, and permissions you set through a conversation. I didn't wrap a third-party SDK. It runs straight on JAW.

Open the dashboard Read the docs

Free · ~30 seconds to your first agent

youpay hannibal 1 usdc/day → ✓ hannibal-coffee.agensai.eth live

base sepoliaby default·any chain JAW supports

You above. A fleet of agents below.

Your AI chat becomes the command deck for a fleet of agents. Describe one, pay hannibal 1 USDC every day for a week, and you get back a real wallet, a real ENS name, and an onchain permission no one can exceed. Spawn one. Spawn ten. Anyone who can describe what they want can run a fleet. No SDK. No contracts. No developer mode. One way to wire JAW into a chat. Fork it and ship yours.

$npx agensai pair <token>

Names instead of hex strings means safer prompts, reviewable diffs, and tool calls a teammate can actually read in a PR.

Cursor · MCP · agensaiconnected

you

Pay hannibal.eth 1 USDC every day for a week.

tool · agensai.create_agent + grant_allowance

{ agent:        "hannibal-coffee",
  funded:       "7 USDC",
  allowance_to: "hannibal.eth",
  cap:          "1 USDC / day",
  expires:      "7 days" }

Live as hannibal-coffee.agensai.eth.

smart account · base sepolia · 1 USDC/day to hannibal.eth · 7d

CClaude Desktop

CCursor

WWindsurf

ZZed

CClaude Code

AAny MCP host

Three layers.
That's the whole stack.

Three tags, three responsibilities. You describe what you want. The AGENSAI MCP wires it into JAW. JAW holds the wallet, keys, permissions. That's where security lives, signed by JustaLab.

Every JAW upgrade ships to your agents the day it lands.

Your chatClaude Desktop · Cursor · Windsurf · any MCP host

You

AGENSAI MCPone npm package · pair, spawn, transfer, revoke

vibecoded

JAWsmart accounts · ENS names · scoped permissions · USDC gas

JustaLab

JAW.id@jaw.id/core@jaw.id/wagmi@jaw.id/uiERC-4337ERC-7715ERC-1271EIP-7702EntryPoint v0.8ENSBaseEthereumOptimismJAW.id@jaw.id/core@jaw.id/wagmi@jaw.id/uiERC-4337ERC-7715ERC-1271EIP-7702EntryPoint v0.8ENSBaseEthereumOptimism

A platform for every user. Not just power users.

If you can type a sentence into Claude Desktop or Cursor, you can spawn an agent with a real wallet and onchain spending limits. No SDK, no contracts to wire up, no developer mode.

ENS isn't a feature.
It's the database.

Your fleet lives on ENS, not in a private database. Main, orchestrators, agents, each is a name with records you sign. Resolvable in any wallet. Recoverable on the day I vanish.

01Identity

Identity is the wallet.

An agent is its name. hannibal-coffee.agensai.eth resolves to the smart account itself. One primitive, not two.

02Sovereignty

The directory has no owner.

Your fleet is a public record on Ethereum. Resolvable from any wallet, verifiable from any explorer, hosted by no one.

03Reach

One name, every chain.

Same name, same address on Base, Optimism, Ethereum. Every tool that reads ENS already reads your agents.

walkFleet("hannibal.agensai.eth")

read · onchain · ccip-read

Main

hannibal.agensai.eth

agensai.orch.0hannibal-orc.agensai.eth

agensai.orch.1hannibal-orc-q3.agensai.eth

Orchestrator

hannibal-orc.agensai.eth

ownerhannibal.agensai.eth

children[0]hannibal-coffee.agensai.eth

children[1]rent-payer.agensai.eth

statusactive

Agent

hannibal-coffee.agensai.eth

parenthannibal-orc.agensai.eth

allowance1 USDC / day to hannibal.eth · 7d

statusactive

same address on every chain · same name in every walletwritten by → on-device keys, never by me

A database isn't trust. A backend isn't recovery. The chain stores the wallet. ENS stores everything else. Both belong to you, not to me, even after I'm gone.

Use mine. Or build your own.

AGENSAI is one opinionated POC on top of JAW. A thousand others are worth shipping. JAW gives you every primitive natively, smart accounts, ENS, permissions, gas. A thin MCP wires it into your chat, and when JAW ships an upgrade your fleet inherits it by default. You don't need to rent a third-party SDK and bolt a CLI on top to do this. Vote to open mine, or build your own on JAW.

01Path

Use mine.

Open the dashboard

02Path

Build your own.

The monorepo isn't public yet. Sign in with JAW, vote yes on-chain, and if enough builders want it I open the whole thing. Fork it, rebrand it, change every opinion.

03Path

Ship anywhere.

Default base sepolia. Any chain JAW supports works. Same MCP, same ENS, different chain id. The architecture doesn't care which L2 you pick.

Read the docs

Either path lands you in the same place: real ENS names, on a public chain, on a stack anyone can run. I just happen to run one version of it.

Smart wallets are how an agent acts. ENS is who it is.

Two primitives. Both belong to the agent, not the platform. Names aren't the surface. They're half the product.

Owned stack. Public names. No backend.

Most agent-wallet products wrap a third-party account vendor and keep fleet state in a hosted backend. AGENSAI is a starter POC on JAW (fork it, ship yours), with the chain itself as the database. Five rows on what that trade-off changes.

Dimension

Wrapper SaaS on a third-party stack

AGENSAI on JAW

Stack

Their SDK wraps a third-party account vendor's SDK. The deepest layer is owned by a third party. upstream changes ripple up.

JAW underneath, signed by JustaLab. AGENSAI MCP is a thin POC layer on top of it. Your chat is the surface.

Identity

0x addresses. Names are kept in a hosted directory you query through their API.

Every agent is born an ENS name. The chain is the directory. hannibal-coffee.agensai.eth resolves on Etherscan, in MetaMask, and in any wallet that speaks ENS.

Setup

Install one MCP server in your IDE. Pair once. 30 seconds. The chat is the UI.

Who spawns

Developers building an agent app on their platform.

Anyone with Claude Desktop or Cursor. No code required. Just type spawn a bot that pays my freelancer Fridays.

If I vanish

The hosted backend is in the request path, and fleet state lives in their database. Continuity depends on the company staying around.

Agents are ENS names + onchain accounts. No AGENSAI server in the agent execution path. Your fleet keeps running on the public chain whether I'm around or not.

Different choices, different trade-offs. Mine is built so the chain holds what matters, and the rest is replaceable.

Wallets and names for every agent*autonomous.

Three layers.That's the whole stack.

ENS isn't a feature.It's the database.