Gizatech Agent SDK Skill

Product summary

Gizatech is a TypeScript SDK and MCP server for building autonomous DeFi yield optimization agents. Agents manage smart-account wallets, automatically rebalance capital across lending protocols (Aave, Compound, Morpho, etc.), and maximize yield while minimizing gas costs. The SDK provides two integration paths: Agentic (Giza handles execution) or IaaS (you bring your own infrastructure and consume optimization intelligence). Key files: @gizatech/agent-sdk (TypeScript SDK), @gizatech/mcp-server (MCP integration). Primary docs: https://build.gizatech.xyz

When to use

• Building yield agents: Create smart accounts, activate agents with token/protocol selection, monitor performance
• Integrating with Claude/Cursor: Use the MCP server to expose 22 tools for LLM-driven agent management
• Optimization workflows: Call the optimizer endpoint to get optimal allocations, APR improvements, and action plans
• Portfolio monitoring: Track APR, performance history, deposits, withdrawals, and rewards
• Custom execution: Use IaaS mode to get optimization intelligence while keeping your own smart account infrastructure
• Constraint-based allocation: Enforce diversification, cap exposure, exclude protocols, set minimum allocations

Quick reference

Configuration

Supported Chains

Chain.BASE (8453) - Base Mainnet
Chain.ARBITRUM (42161) - Arbitrum One
Chain.ETHEREUM (1) - Ethereum Mainnet
Chain.POLYGON (137) - Polygon Mainnet
Chain.SEPOLIA (11155111) - Sepolia Testnet
Chain.BASE_SEPOLIA (84532) - Base Sepolia Testnet

Supported Tokens

SDK Architecture

Two primary classes:

• Giza: Top-level client. Chain-level queries (protocols, tokens, stats, optimizer). Factory for Agent instances.
• Agent: Wallet-scoped handle bound to a single smart-account address. All lifecycle, monitoring, withdrawal, rewards, protocol operations.

Agent Lifecycle Methods

Monitoring Methods

MCP Server Tools (22 total)

Error Types

ValidationError       // Invalid input (bad address, missing fields)
GizaAPIError         // HTTP error (includes statusCode)
TimeoutError         // Request exceeded timeout
NetworkError         // DNS, connection refused

Decision guidance

Workflow

1. Initialize SDK and Create Smart Account

import { Giza, Chain } from '@gizatech/agent-sdk';

const giza = new Giza({
  chain: Chain.BASE,
  apiKey: process.env.GIZA_API_KEY,
  partner: process.env.GIZA_PARTNER_NAME,
  apiUrl: process.env.GIZA_API_URL,
});

// Create smart account for user EOA
const agent = await giza.createAgent('0xUserEOA...');
console.log('Smart account:', agent.wallet);

2. Get Available Protocols and Tokens

// Chain-level query: protocols supporting USDC
const protocols = await giza.protocols('0xUSDCAddress');

// Get supported tokens on chain
const tokens = await giza.tokens();

3. Activate Agent After User Deposits

// User sends deposit to smart account, get tx hash
const activateResponse = await agent.activate({
  owner: '0xUserEOA...',
  token: '0xUSDCAddress',
  protocols: ['aave', 'compound', 'morpho'],
  txHash: '0xDepositTxHash...',
  constraints: [
    {
      kind: 'max_allocation_amount_per_protocol',
      params: { protocol: 'aave', amount: '500000000' },
    },
  ],
});

4. Monitor Portfolio and Performance

// Get current state
const info = await agent.portfolio();
console.log('Status:', info.status);

// Get APR
const { apr } = await agent.apr();
console.log(`Current APR: ${apr.toFixed(2)}%`);

// Get performance history
const { performance } = await agent.performance();
performance.forEach(point => {
  console.log(`${point.date}: $${point.value_in_usd}`);
});

5. Handle Withdrawals and Rewards

// Partial withdrawal
await agent.withdraw({
  amount: '1000000000', // in token units
  recipient: '0xUserEOA...',
});

// Claim rewards
const claimed = await agent.claimRewards();

// Full deactivation
await agent.deactivate({
  recipient: '0xUserEOA...',
});

6. Use Optimizer for Custom Allocation (IaaS)

const result = await giza.optimize({
  token: '0xUSDCAddress',
  capital: '10000000000',
  currentAllocations: { aave: '5000000000', morpho: '5000000000' },
  protocols: ['aave', 'morpho', 'compound'],
  constraints: [
    {
      kind: 'min_protocols',
      params: { min_protocols: 2 },
    },
  ],
});

console.log('Optimal allocation:', result.optimal_allocation);
console.log('APR improvement:', result.apr_improvement);
console.log('Action plan:', result.action_plan);

Common gotchas

• Smart account address is deterministic: Calling createAgent() with the same EOA always returns the same address. Don’t create duplicates.
• Activation requires deposit tx hash: Must call activate() after user sends deposit to smart account. Without tx hash, activation fails.
• API credentials are required: All authenticated endpoints need GIZA_API_KEY and GIZA_PARTNER_NAME. Set as environment variables or pass to constructor.
• MCP tools require connected wallet: Most MCP tools fail if no wallet is connected. Call connect_wallet first.
• Constraints are optional but recommended: Without constraints, optimizer may concentrate allocation in single protocol. Use MIN_PROTOCOLS for diversification.
• Pagination is lazy: Paginator doesn’t fetch all pages upfront. Use for await...of for automatic paging or .first(n) for limited results.
• Timeout default is 45 seconds: Network calls may fail if timeout is too short. Increase with timeout: 60000 for slower networks.
• Deactivation is irreversible: Once deactivated, agent exits all positions and stops. User must go through activation flow again to restart.
• 10% fee on gains only: Withdrawal fee applies only to profits, never to principal. Clarify this in UI.
• Gas covered after activation: Initial deposit transaction requires native token for gas. All subsequent rebalances are gasless.

Verification checklist

Before submitting work with Gizatech:

• Environment variables set: GIZA_API_KEY, GIZA_PARTNER_NAME, GIZA_API_URL
• Chain specified in config matches user’s network (Base, Arbitrum, etc.)
• Smart account created before activation attempt
• Deposit transaction confirmed on-chain before calling activate()
• Token address is correct for selected chain (USDC vs USDT0)
• Protocols in activation request are supported on selected chain
• Constraints are valid (no conflicting min/max values)
• Error handling wraps SDK calls in try-catch with typed error classes
• Paginated results use for await...of or .first() for proper iteration
• MCP server has wallet connected before calling agent-scoped tools
• API calls made from backend, not exposed to client-side code
• Tested on testnet (Sepolia, Base Sepolia) before production

Resources

Comprehensive navigation: https://build.gizatech.xyz/llms.txt

Critical documentation pages:

• SDK Overview & Configuration — SDK architecture, config, error handling
• Agent Lifecycle — Activation, deactivation, top-ups, runs
• MCP Server Overview — 22 tools, Claude/Cursor integration, configuration tiers

For additional documentation and navigation, see: https://build.gizatech.xyz/llms.txt