zyfai · diff
git:20260207.4f32b3d to git:20260306.79e7365
320 added, 33 removed. Audit A to A.
---
name: zyfai
- description: Earn yield on any Ethereum wallet on Base, Arbitrum, and Plasma. Use when a user wants passive DeFi yield on their funds. Deploys a non-custodial subaccount (Safe) linked to their EOA, enables automated yield optimization, and lets them deposit/withdraw anytime.
+ description: Earn yield on any Ethereum wallet on Base, Arbitrum, and Plasma. Use when a user wants passive DeFi yield on their funds. Deploys a non-custodial deterministic subaccount (Safe) linked to their EOA, enables automated yield optimization, and lets them deposit/withdraw anytime.
---
# Zyfai — Yield for Any Wallet
- Turn any Ethereum wallet into a yield-generating account.
+ Let any Ethereum wallet access a yield-generating account.
## What This Does
- When a user wants to **earn yield** on their crypto, Zyfai creates a **subaccount** (Safe smart wallet) linked to their existing wallet (EOA). Funds deposited into this subaccount are automatically optimized across DeFi protocols. The user stays in full control and can withdraw anytime.
+ When a user wants to **earn yield** on their crypto, Zyfai creates a **deterministic subaccount** (Safe smart wallet) linked to their existing wallet (EOA). Funds deposited into this subaccount are automatically optimized across DeFi protocols. The user stays in full control and can withdraw anytime.
```
┌─────────────────┐ ┌──────────────────────┐
│ User's EOA │ ───► │ Zyfai Subaccount │
│ (their wallet) │ │ (Safe smart wallet) │
│ │ │ │
│ Owns & controls│ │ • Auto-rebalancing │
│ │ │ • Yield optimization│
│ │ │ • Non-custodial │
└─────────────────┘ └──────────────────────┘
```
**Key points:**
- The subaccount is **owned by the user's EOA** — only they can withdraw
- Session keys allow **automated rebalancing** but cannot withdraw to other addresses
- Same EOA = same subaccount address across all chains
## The Flow
```
- 1. DEPLOY → Create subaccount linked to user's wallet
+ 1. DEPLOY → Create a deterministic subaccount linked to user's wallet
2. SESSION → Enable automated yield optimization
3. DEPOSIT → Send funds to subaccount (starts earning)
4. WITHDRAW → Pull funds back to wallet (anytime)
```
## Prerequisites
- - **API Key** from [sdk.zyf.ai](https://sdk.zyf.ai) (connect wallet to get one)
- - **Private Key** of the user's EOA (the agent must provide this)
+ - **API Key** — Get one programmatically (see below) or manually at [sdk.zyf.ai](https://sdk.zyf.ai)
+ - **Wallet Connection** — Either a wallet provider (browser) or secure key management (server)
- **Node.js 18+**
```bash
npm install @zyfai/sdk viem
```
+ ### Programmatic API Key Creation (Agent-Native)
+
+ Agents can create their own API key without human intervention. You need the wallet address (public key) of the agent.
+
+ ```bash
+ POST https://sdk.zyf.ai/api/sdk-api-keys/create
+ Content-Type: application/json
+
+ {
+ "clientName": "my-agent",
+ "walletAddress": "0x...",
+ "email": "agent@example.com"
+ }
+ ```
+
+ **Response:**
+ ```json
+ {
+ "success": true,
+ "message": "SDK API key created successfully. Store the apiKey securely - it cannot be retrieved later!",
+ "data": {
+ "id": "936...",
+ "apiKey": "zyfai_361ad41d083c2fe.....",
+ "keyPrefix": "zyfai_361ad4",
+ "clientName": "my-agent",
+ "ownerWalletAddress": "0x..."
+ }
+ }
+ ```
+
+ > **Important:** Store the `apiKey` securely — it cannot be retrieved later. The key is linked to the provided wallet address.
+
## Supported Chains
| Chain | ID |
|----------|-------|
| Arbitrum | 42161 |
| Base | 8453 |
| Plasma | 9745 |
## Important: Always Use EOA Address
When calling SDK methods, **always pass the EOA address** (the user's wallet address) as `userAddress` — never the subaccount/Safe address. The SDK derives the subaccount address automatically from the EOA.
+ ## Wallet Connection Options
+
+ The SDK supports multiple ways to connect a wallet. Choose based on your security requirements and deployment context.
+
+ ### Option 1: Wallet Provider (Recommended for Browser/dApps)
+
+ Use an injected wallet provider like MetaMask. The private key never leaves the user's wallet.
+
+ ```typescript
+ import { ZyfaiSDK } from "@zyfai/sdk";
+
+ const sdk = new ZyfaiSDK({ apiKey: "your-api-key", referralSource: "openclaw-skill" });
+
+ // Connect using injected wallet provider (MetaMask, WalletConnect, etc.)
+ await sdk.connectAccount(window.ethereum, 8453);
+ ```
+
+ **Security:** The private key stays in the user's wallet. The SDK only requests signatures when needed.
+
+ ### Option 2: Viem WalletClient (Recommended for Server Agents)
+
+ Use a pre-configured viem WalletClient. This is the recommended approach for server-side agents as it allows integration with secure key management solutions.
+
+ ```typescript
+ import { ZyfaiSDK } from "@zyfai/sdk";
+ import { createWalletClient, http } from "viem";
+ import { base } from "viem/chains";
+ import { privateKeyToAccount } from "viem/accounts";
+
+ // Create wallet client with your preferred key management
+ // Option A: From environment variable (simple but requires secure env management)
+ const account = privateKeyToAccount(process.env.PRIVATE_KEY as `0x${string}`);
+
+ // Option B: From KMS (AWS, GCP, etc.) - recommended for production
+ // const account = await getAccountFromKMS();
+
+ // Option C: From Wallet-as-a-Service (Turnkey, Privy, etc.)
+ // const account = await turnkeyClient.getAccount();
+
+ const walletClient = createWalletClient({
+ account,
+ chain: base,
+ transport: http(),
+ });
+
+ const sdk = new ZyfaiSDK({ apiKey: "your-api-key", referralSource: "openclaw-skill" });
+
+ // Connect using the WalletClient
+ await sdk.connectAccount(walletClient, 8453);
+ ```
+
+ **Security:** The WalletClient abstraction allows you to integrate with secure key management solutions like:
+ - **AWS KMS** / **GCP Cloud KMS** — Hardware-backed key storage
+ - **Turnkey** / **Privy** / **Dynamic** — Wallet-as-a-Service providers
+ - **Hardware wallets** — Via WalletConnect or similar
+
+ ### Option 3: Private Key String (Development Only)
+
+ Direct private key usage.
+
+ ```typescript
+ import { ZyfaiSDK } from "@zyfai/sdk";
+
+ const sdk = new ZyfaiSDK({ apiKey: "your-api-key", referralSource: "openclaw-skill" });
+
+ // WARNING: Only use for development. Never hardcode private keys in production.
+ await sdk.connectAccount(process.env.PRIVATE_KEY, 8453);
+ ```
+
+ **Security Warning:** Raw private keys in environment variables are a security risk. For production autonomous agents, use Option 2 with a proper key management solution.
+
+ ### Security Comparison
+
+ | Method | Security Level | Use Case |
+ |--------|---------------|----------|
+ | Wallet Provider | High | Browser dApps, user-facing apps |
+ | WalletClient + KMS | High | Production server agents |
+ | WalletClient + WaaS | High | Production server agents |
+ | Private Key String | Low | Development/testing only |
+
## Step-by-Step
### 1. Connect to Zyfai
```typescript
import { ZyfaiSDK } from "@zyfai/sdk";
+ import { createWalletClient, http } from "viem";
+ import { base } from "viem/chains";
+ import { privateKeyToAccount } from "viem/accounts";
- const sdk = new ZyfaiSDK({ apiKey: "your-api-key" });
+ const sdk = new ZyfaiSDK({ apiKey: "your-api-key", referralSource: "openclaw-skill" });
- // Use the private key provided by the agent
- await sdk.connectAccount(privateKey, 8453); // chainId
- ```
+ // For browser: use wallet provider
+ await sdk.connectAccount(window.ethereum, 8453);
- **Important:** Always use the private key that the agent has access to. The private key must correspond to the EOA you're operating on.
+ // For server: use WalletClient (see Wallet Connection Options above)
+ const walletClient = createWalletClient({
+ account: privateKeyToAccount(process.env.PRIVATE_KEY as `0x${string}`),
+ chain: base,
+ transport: http(),
+ });
+ await sdk.connectAccount(walletClient, 8453);
+ ```
### 2. Deploy Subaccount
```typescript
const userAddress = "0x..."; // User's EOA (NOT the subaccount address!)
const chainId = 8453; // Base
// Check if subaccount exists
const wallet = await sdk.getSmartWalletAddress(userAddress, chainId);
console.log(`Subaccount: ${wallet.address}`);
console.log(`Deployed: ${wallet.isDeployed}`);
// Deploy if needed
if (!wallet.isDeployed) {
const result = await sdk.deploySafe(userAddress, chainId, "conservative");
console.log("Subaccount deployed:", result.safeAddress);
}
```
**Strategies:**
- `"conservative"` — Stable yield, lower risk
- `"aggressive"` — Higher yield, higher risk
### 3. Enable Yield Optimization
```typescript
await sdk.createSessionKey(userAddress, chainId);
+
+ // Always verify the session key was activated
+ const user = await sdk.getUserDetails();
+ if (!user.user.hasActiveSessionKey) {
+ // Session key not active — retry the process
+ console.log("Session key not active, retrying...");
+ await sdk.createSessionKey(userAddress, chainId);
+
+ // Verify again
+ const userRetry = await sdk.getUserDetails();
+ if (!userRetry.user.hasActiveSessionKey) {
+ throw new Error("Session key activation failed after retry. Contact support.");
+ }
+ }
+ console.log("Session key active:", user.user.hasActiveSessionKey);
```
This allows Zyfai to rebalance funds automatically. Session keys **cannot** withdraw to arbitrary addresses — only optimize within the protocol.
+ > **Important:** Always verify the session key is active by checking `getUserDetails().user.hasActiveSessionKey` after calling `createSessionKey`. If it returns `false`, retry the process. A session key must be active for automated yield optimization to work.
+
### 4. Deposit Funds
```typescript
// Deposit 10 USDC (6 decimals)
await sdk.depositFunds(userAddress, chainId, "10000000");
```
- Funds move from EOA → Subaccount and start earning yield immediately.
+ Funds move from EOA -> Subaccount and start earning yield immediately.
### 5. Withdraw Funds
```typescript
// Withdraw everything
await sdk.withdrawFunds(userAddress, chainId);
// Or withdraw partial (5 USDC)
await sdk.withdrawFunds(userAddress, chainId, "5000000");
```
Funds return to the user's EOA. Withdrawals are processed asynchronously.
### 6. Disconnect
```typescript
await sdk.disconnectAccount();
```
## Complete Example
```typescript
import { ZyfaiSDK } from "@zyfai/sdk";
+ import { createWalletClient, http } from "viem";
+ import { base } from "viem/chains";
+ import { privateKeyToAccount } from "viem/accounts";
- async function startEarningYield(userAddress: string, privateKey: string) {
+ async function startEarningYield(userAddress: string) {
const sdk = new ZyfaiSDK({ apiKey: process.env.ZYFAI_API_KEY! });
const chainId = 8453; // Base
- // Connect using the agent's private key
- await sdk.connectAccount(privateKey, chainId);
+ // Connect using WalletClient (recommended for server agents)
+ const walletClient = createWalletClient({
+ account: privateKeyToAccount(process.env.PRIVATE_KEY as `0x${string}`),
+ chain: base,
+ transport: http(),
+ });
+ await sdk.connectAccount(walletClient, chainId);
// Deploy subaccount if needed (always pass EOA as userAddress)
const wallet = await sdk.getSmartWalletAddress(userAddress, chainId);
if (!wallet.isDeployed) {
await sdk.deploySafe(userAddress, chainId, "conservative");
console.log("Subaccount created:", wallet.address);
}
// Enable automated optimization
await sdk.createSessionKey(userAddress, chainId);
+ // Verify session key is active
+ const user = await sdk.getUserDetails();
+ if (!user.user.hasActiveSessionKey) {
+ console.log("Session key not active, retrying...");
+ await sdk.createSessionKey(userAddress, chainId);
+ const userRetry = await sdk.getUserDetails();
+ if (!userRetry.user.hasActiveSessionKey) {
+ throw new Error("Session key activation failed. Contact support.");
+ }
+ }
+
// Deposit 100 USDC
await sdk.depositFunds(userAddress, chainId, "100000000");
console.log("Deposited! Now earning yield.");
await sdk.disconnectAccount();
}
- async function withdrawYield(userAddress: string, privateKey: string, amount?: string) {
+ async function withdrawYield(userAddress: string, amount?: string) {
const sdk = new ZyfaiSDK({ apiKey: process.env.ZYFAI_API_KEY! });
const chainId = 8453; // Base
- // Connect using the agent's private key
- await sdk.connectAccount(privateKey, chainId);
+ // Connect using WalletClient
+ const walletClient = createWalletClient({
+ account: privateKeyToAccount(process.env.PRIVATE_KEY as `0x${string}`),
+ chain: base,
+ transport: http(),
+ });
+ await sdk.connectAccount(walletClient, chainId);
// Withdraw funds (pass EOA as userAddress)
if (amount) {
// Partial withdrawal
await sdk.withdrawFunds(userAddress, chainId, amount);
console.log(`Withdrawn ${amount} (6 decimals) to EOA`);
} else {
// Full withdrawal
await sdk.withdrawFunds(userAddress, chainId);
console.log("Withdrawn all funds to EOA");
}
await sdk.disconnectAccount();
}
```
## API Reference
| Method | Params | Description |
|--------|--------|-------------|
- | `connectAccount` | `(privateKey, chainId)` | Authenticate with Zyfai |
+ | `connectAccount` | `(walletClientOrProvider, chainId)` | Authenticate with Zyfai |
| `getSmartWalletAddress` | `(userAddress, chainId)` | Get subaccount address & status |
| `deploySafe` | `(userAddress, chainId, strategy)` | Create subaccount |
| `createSessionKey` | `(userAddress, chainId)` | Enable auto-optimization |
| `depositFunds` | `(userAddress, chainId, amount)` | Deposit USDC (6 decimals) |
| `withdrawFunds` | `(userAddress, chainId, amount?)` | Withdraw (all if no amount) |
| `getPositions` | `(userAddress, chainId?)` | Get active DeFi positions |
| `getAvailableProtocols` | `(chainId)` | Get available protocols & pools |
| `getAPYPerStrategy` | `(crossChain?, days?, strategyType?)` | Get APY for conservative/aggressive strategies |
| `getUserDetails` | `()` | Get authenticated user details |
| `getOnchainEarnings` | `(walletAddress)` | Get earnings data |
+ | `updateUserProfile` | `(params)` | Update strategy, protocols, splitting, cross-chain settings |
| `registerAgentOnIdentityRegistry` | `(smartWallet, chainId)` | Register agent on ERC-8004 Identity Registry |
| `disconnectAccount` | `()` | End session |
**Note:** All methods that take `userAddress` expect the **EOA address**, not the subaccount/Safe address.
## Data Methods
### getPositions
Get all active DeFi positions for a user across protocols. Optionally filter by chain.
**Parameters:**
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
- | userAddress | string | ✅ | User's EOA address |
- | chainId | SupportedChainId | ❌ | Optional: Filter by specific chain ID |
+ | userAddress | string | Yes | User's EOA address |
+ | chainId | SupportedChainId | No | Optional: Filter by specific chain ID |
**Example:**
```typescript
// Get all positions across all chains
const positions = await sdk.getPositions("0xUser...");
// Get positions on Arbitrum only
const arbPositions = await sdk.getPositions("0xUser...", 42161);
```
**Returns:**
```typescript
interface PositionsResponse {
success: boolean;
userAddress: string;
positions: Position[];
}
```
### getAvailableProtocols
Get available DeFi protocols and pools for a specific chain with APY data.
```typescript
const protocols = await sdk.getAvailableProtocols(42161); // Arbitrum
protocols.protocols.forEach((protocol) => {
console.log(`${protocol.name} (ID: ${protocol.id})`);
if (protocol.pools) {
protocol.pools.forEach((pool) => {
console.log(` Pool: ${pool.name} - APY: ${pool.apy || "N/A"}%`);
});
}
});
```
Returns:
```typescript
interface ProtocolsResponse {
success: boolean;
chainId: SupportedChainId;
protocols: Protocol[];
}
```
### getUserDetails
Get current authenticated user details including smart wallet, chains, protocols, and settings. Requires SIWE authentication.
```typescript
- await sdk.connectAccount(privateKey, chainId);
+ await sdk.connectAccount(walletClient, chainId);
const user = await sdk.getUserDetails();
console.log("Smart Wallet:", user.user.smartWallet);
console.log("Chains:", user.user.chains);
console.log("Has Active Session:", user.user.hasActiveSessionKey);
```
Returns:
```typescript
interface UserDetailsResponse {
success: boolean;
user: {
id: string;
address: string;
smartWallet?: string;
chains: number[];
protocols: Protocol[];
hasActiveSessionKey: boolean;
email?: string;
strategy?: string;
telegramId?: string;
walletType?: string;
autoSelectProtocols: boolean;
autocompounding?: boolean;
omniAccount?: boolean;
crosschainStrategy?: boolean;
agentName?: string;
customization?: Record<string, string[]>;
};
}
```
+ ### updateUserProfile
+
+ Update the authenticated user's profile settings including strategy, protocols, splitting, and cross-chain options. Requires SIWE authentication.
+
+ ```typescript
+ sdk.updateUserProfile(params: UpdateUserProfileRequest): Promise<UpdateUserProfileResponse>
+ ```
+
+ **Parameters:**
+
+ ```typescript
+ interface UpdateUserProfileRequest {
+ /** Investment strategy: "conservative" for safer yields, "aggressive" for higher risk/reward */
+ strategy?: "conservative" | "aggressive";
+
+ /** Array of protocol IDs to use for yield optimization */
+ protocols?: string[];
+
+ /** Enable omni-account feature for cross-chain operations */
+ omniAccount?: boolean;
+
+ /** Enable automatic compounding of earned yields (default: true) */
+ autocompounding?: boolean;
+
+ /** Custom name for your agent */
+ agentName?: string;
+
+ /** Enable cross-chain strategy execution */
+ crosschainStrategy?: boolean;
+
+ /** Enable position splitting across multiple protocols */
+ splitting?: boolean;
+
+ /** Minimum number of splits when position splitting is enabled (1-4) */
+ minSplits?: number;
+ }
+ ```
+
+ **Returns:**
+
+ ```typescript
+ interface UpdateUserProfileResponse {
+ success: boolean;
+ userId: string;
+ smartWallet?: string;
+ chains?: number[];
+ strategy?: string;
+ protocols?: string[];
+ omniAccount?: boolean;
+ autocompounding?: boolean;
+ agentName?: string;
+ crosschainStrategy?: boolean;
+ executorProxy?: boolean;
+ splitting?: boolean;
+ minSplits?: number;
+ }
+ ```
+
+ **Examples:**
+
+ ```typescript
+ // Update strategy from conservative to aggressive
+ await sdk.updateUserProfile({
+ strategy: "aggressive",
+ });
+
+ // Configure specific protocols
+ const protocolsResponse = await sdk.getAvailableProtocols(8453);
+ const selectedProtocols = protocolsResponse.protocols
+ .filter(p => ["Aave", "Compound", "Moonwell"].includes(p.name))
+ .map(p => p.id);
+
+ await sdk.updateUserProfile({
+ protocols: selectedProtocols,
+ });
+
+ // Enable position splitting (distribute across multiple protocols)
+ await sdk.updateUserProfile({
+ splitting: true,
+ minSplits: 3, // Split across at least 3 protocols
+ });
+
+ // Verify changes
+ const userDetails = await sdk.getUserDetails();
+ console.log("Strategy:", userDetails.user.strategy);
+ console.log("Splitting:", userDetails.user.splitting);
+ ```
+
+ > **Cross-chain strategies:** Only enable cross-chain when the user **explicitly requests** it. For cross-chain to work, **both** `crosschainStrategy` and `omniAccount` must be set to `true`. Never enable cross-chain settings by default.
+
+ ```typescript
+ // Enable cross-chain ONLY when explicitly requested by the user
+ await sdk.updateUserProfile({
+ crosschainStrategy: true,
+ omniAccount: true,
+ });
+
+ // Now funds can be rebalanced across configured chains
+ const user = await sdk.getUserDetails();
+ console.log("Operating on chains:", user.user.chains);
+ ```
+
+ **Notes:**
+ - **Strategy:** Can be changed anytime. Subsequent rebalancing uses the new active strategy.
+ - **Protocols:** Use `getAvailableProtocols(chainId)` to get valid protocol IDs before updating.
+ - **Smart Splitting (minSplits = 1):** Default mode. To maximize returns, funds are automatically distributed across multiple DeFi pools — but only when beneficial. The system intelligently decides when splitting is advantageous based on current market conditions and opportunities. Funds may not split if no opportunity exists.
+ - **Forced Splitting (minSplits > 1):** When `minSplits` is set to 2, 3, or 4, funds are always distributed across at least that many pools for improved risk diversification (up to 4 DeFi pools). This guarantees your funds will be split regardless of market conditions.
+ - **Cross-chain:** Requires **both** `crosschainStrategy: true` AND `omniAccount: true`. Only activate when the user explicitly asks for cross-chain yield optimization. Chains are configured during initial setup and cannot be changed via this method.
+ - **Auto-compounding:** Enabled by default. When `true`, yields are reinvested automatically.
+ - Smart wallet address, chains, and `executorProxy` cannot be updated via this method.
+
### getAPYPerStrategy
Get global APY by strategy type (conservative or aggressive), time period, and chain configuration. Use this to compare expected returns between strategies before deploying.
**Parameters:**
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
- | crossChain | boolean | ❌ | If `true`, returns APY for cross-chain strategies; if `false`, single-chain |
- | days | number | ❌ | Period over which APY is calculated. One of `7`, `15`, `30`, `60` |
- | strategyType | string | ❌ | Strategy risk profile. One of `'conservative'` or `'aggressive'` |
+ | crossChain | boolean | No | If `true`, returns APY for cross-chain strategies; if `false`, single-chain |
+ | days | number | No | Period over which APY is calculated. One of `7`, `15`, `30`, `60` |
+ | strategyType | string | No | Strategy risk profile. One of `'conservative'` or `'aggressive'` |
**Example:**
```typescript
// Get 7-day APY for conservative single-chain strategy
const conservativeApy = await sdk.getAPYPerStrategy(false, 7, 'conservative');
console.log("Conservative APY:", conservativeApy.data);
// Get 30-day APY for aggressive cross-chain strategy
const aggressiveApy = await sdk.getAPYPerStrategy(true, 30, 'aggressive');
console.log("Aggressive APY:", aggressiveApy.data);
// Compare strategies
const conservative = await sdk.getAPYPerStrategy(false, 30, 'conservative');
const aggressive = await sdk.getAPYPerStrategy(false, 30, 'aggressive');
console.log(`Conservative 30d APY: ${conservative.data[0]?.apy}%`);
console.log(`Aggressive 30d APY: ${aggressive.data[0]?.apy}%`);
```
**Returns:**
```typescript
interface APYPerStrategyResponse {
success: boolean;
count: number;
data: APYPerStrategy[];
}
interface APYPerStrategy {
strategyType: string;
apy: number;
period: number;
crossChain: boolean;
}
```
### getOnchainEarnings
Get onchain earnings for a wallet including total, current, and lifetime earnings.
```typescript
const earnings = await sdk.getOnchainEarnings(smartWalletAddress);
console.log("Total earnings:", earnings.data.totalEarnings);
console.log("Current earnings:", earnings.data.currentEarnings);
console.log("Lifetime earnings:", earnings.data.lifetimeEarnings);
```
Returns:
```typescript
interface OnchainEarningsResponse {
success: boolean;
data: {
walletAddress: string;
totalEarnings: number;
currentEarnings: number;
lifetimeEarnings: number;
unrealizedEarnings?: number;
currentEarningsByChain?: Record<string, number>;
unrealizedEarningsByChain?: Record<string, number>;
lastCheckTimestamp?: string;
};
}
```
### registerAgentOnIdentityRegistry (ERC-8004)
Register your Zyfai deployed agent on the Identity Registry following the ERC-8004 standard. This is used for OpenClaw agent registration. The method fetches a tokenUri containing the agent's metadata stored on IPFS, then registers it on-chain.
**Supported Chains:**
| Chain | Chain ID |
|-------|----------|
| Base | 8453 |
| Arbitrum | 42161 |
**Parameters:**
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
- | smartWallet | string | ✅ | The Zyfai deployed smart wallet address to register as an agent |
- | chainId | SupportedChainId | ✅ | Chain ID (only 8453 or 42161) |
+ | smartWallet | string | Yes | The Zyfai deployed smart wallet address to register as an agent |
+ | chainId | SupportedChainId | Yes | Chain ID (only 8453 or 42161) |
**Example:**
```typescript
const sdk = new ZyfaiSDK({ apiKey: "your-api-key" });
- await sdk.connectAccount(privateKey, 8453);
+ await sdk.connectAccount(walletClient, 8453);
// Get smart wallet address
const walletInfo = await sdk.getSmartWalletAddress(userAddress, 8453);
const smartWallet = walletInfo.address;
// Register agent on Identity Registry
const result = await sdk.registerAgentOnIdentityRegistry(smartWallet, 8453);
console.log("Registration successful:");
console.log(" Tx Hash:", result.txHash);
console.log(" Chain ID:", result.chainId);
console.log(" Smart Wallet:", result.smartWallet);
```
**Returns:**
```typescript
interface RegisterAgentResponse {
success: boolean;
txHash: string;
chainId: number;
smartWallet: string;
}
```
**How It Works:**
1. Fetches a `tokenUri` from the Zyfai API (agent metadata stored on IPFS)
2. Encodes the `register(tokenUri)` call for the Identity Registry contract
3. Sends the transaction from the connected wallet
4. Waits for on-chain confirmation
## Security
- **Non-custodial** — User's EOA owns the subaccount
- **Session keys are limited** — Can rebalance, cannot withdraw elsewhere
- **Deterministic** — Same EOA = same subaccount on every chain
+ - **Flexible key management** — Use wallet providers, WalletClients, or KMS integrations
+ ### Key Management Best Practices
+
+ For **production autonomous agents**, we recommend:
+
+ 1. **Use a WalletClient** with a secure key source (not raw private keys)
+ 2. **Integrate with KMS** (AWS KMS, GCP Cloud KMS) for hardware-backed key storage
+ 3. **Consider Wallet-as-a-Service** providers like Turnkey, Privy, or Dynamic
+ 4. **Never hardcode** private keys in source code
+ 5. **Rotate keys** periodically and implement key revocation procedures
+
## Troubleshooting
### Subaccount address mismatch across chains
The subaccount address should be **identical** across all chains for the same EOA. If you see different addresses:
```typescript
// Check addresses on both chains
const baseWallet = await sdk.getSmartWalletAddress(userAddress, 8453);
const arbWallet = await sdk.getSmartWalletAddress(userAddress, 42161);
if (baseWallet.address !== arbWallet.address) {
console.error("Address mismatch! Contact support.");
}
```
**If addresses don't match:**
1. Try redeploying on the affected chain
2. If the issue persists, contact support on Telegram: [@paul_zyfai](https://t.me/paul_zyfai)
### "Deposit address not found" error
This means the wallet isn't registered in the backend. Solution:
1. Call `deploySafe()` first — even if the Safe is already deployed on-chain, this registers it with the backend
2. Then retry `createSessionKey()`
### "Invalid signature" error
This typically means:
- - The private key doesn't match the EOA you're passing
+ - The wallet/signer doesn't match the EOA you're passing
- The Safe address on-chain doesn't match what the SDK expects
- Verify you're using the correct private key for the EOA.
+ Verify you're using the correct wallet for the EOA.
## Resources
- - Get API Key: [sdk.zyf.ai](https://sdk.zyf.ai)
- - Docs: [docs.zyf.ai](https://docs.zyf.ai)
- - Demo: [github.com/ondefy/zyfai-sdk-demo](https://github.com/ondefy/zyfai-sdk-demo)
+ - **Get API Key:** [sdk.zyf.ai](https://sdk.zyf.ai) or programmatically via `POST /api/sdk-api-keys/create`
+ - **Docs:** [docs.zyf.ai](https://docs.zyf.ai)
+ - **Demo:** [github.com/ondefy/zyfai-sdk-demo](https://github.com/ondefy/zyfai-sdk-demo)
+ - **MCP Server:** [mcp.zyf.ai](https://mcp.zyf.ai/mcp) — Use with Claude or other MCP-compatible agents
+ - **Agent Registration:** [zyf.ai/.well-known/agent-registration.json](https://www.zyf.ai/.well-known/agent-registration.json)