Introduction

AGENSAI gives every AI agent an ENS name, a smart account, and onchain permissions.

Instead of 0x7a3b9c…, your agent is my-agent.agensai.eth. Resolvable, revocable, and readable in every block explorer, every wallet, every audit log.

import { createAgent } from "@agensai/sdk";
 
const agent = await createAgent({
  name: "my-agent",
  policies: [
    { type: "spend", token: "USDC", amount: 50, period: "weekly" },
    { type: "contract", whitelist: ["uniswap.eth"] },
  ],
});
 
// → my-agent.agensai.eth ready to act.

What AGENSAI gives you

• Named agents. Every agent is born as an ENS subname under agensai.eth (or your own namespace on Pro). Onchain. Gasless. Resolvable from anywhere.
• Onchain policies. Spend limits, contract whitelists, time bounds, rate caps. Enforced by the smart account itself, not by your code.
• Headless by design. No passkey prompts, no browser dependencies. Run agents from any server, any function, any cron job.
• MCP native. A built-in MCP server exposes every operation to Claude, Cursor, Codex, Gemini, and Warp. Your agent in your IDE speaks ENS names, not hex.
• Multi chain. Base, Ethereum, Optimism at launch. One ENS identity across every EVM chain.

What AGENSAI is not

• Not a wallet you log into. Agents are server side. Owners authenticate once to provision. Agents act autonomously after.
• Not an LLM. AGENSAI is the wallet your LLM uses. Bring your own model.
• Not a payment processor. AGENSAI executes onchain calls. Fiat on/off ramps are out of scope.

How it's built

AGENSAI stands on production infrastructure shipped by JAW.id:

You don't reimplement any of these. AGENSAI gives you one ergonomic API on top.

Get started

• Quickstart (CLI) — Five minutes from install to a working agent.
• Quickstart (SDK) — Programmatic agent creation in TypeScript.
• Concepts — How AGENSAI thinks about identity, policies, and execution.

Get an API key

Every AGENSAI account starts with an API key. Sign up at app.agensai.xyz.

One key drives the entire stack. You don't manage separate credentials for the smart account and the ENS layer.