agentek

An extensible TypeScript toolkit for EVM and Solana blockchain interactions. Up to 205 composable tools (191 without optional API credentials) covering on-chain actions, DeFi protocols, market data, and off-chain services — designed for AI agents, MCP clients, and developers.

Quick Start

Requires Node.js 20.18.1 or newer.

CLI (fastest way to try it):

npx @agentek/cli list          # browse up to 205 tools
npx @agentek/cli info getBalance  # inspect a specific tool
npx @agentek/cli exec getBalance --json '{"chainId":1,"address":"0x0000000000000000000000000000000000000000"}'

MCP Server (for Claude Desktop, Cursor, etc.):

pnpx @agentek/mcp-server

TypeScript SDK:

pnpm add @agentek/tools

Packages

Versions above are workspace manifest versions; they do not establish npm publication status.

Requirements

• Node.js >= 20.18.1
• pnpm (for development)
• Bun for the private Nani bundle build
• Foundry/Anvil for Gym fork environments and integration tests

Installation

# Core tools
pnpm add @agentek/tools viem zod

# Vercel AI SDK integration
pnpm add @agentek/ai-sdk @agentek/tools viem zod

Usage

Using with Vercel AI SDK

import { allTools } from '@agentek/tools';
import { AgentekToolkit } from '@agentek/ai-sdk';
import { http } from 'viem';
import { mainnet } from 'viem/chains';

const tools = await allTools({
  perplexityApiKey: process.env.PERPLEXITY_API_KEY,
  zeroxApiKey: process.env.ZEROX_API_KEY,
});

const toolkit = new AgentekToolkit({
  accountOrAddress: '0x...',
  chains: [mainnet],
  transports: [http()],
  tools,
});

// Pass to Vercel AI SDK
const aiTools = toolkit.getTools();

Using the toolkit directly

import { createAgentekClient } from '@agentek/tools/client';
import { allTools } from '@agentek/tools';
import { http } from 'viem';
import { mainnet } from 'viem/chains';

const tools = await allTools({});

const client = createAgentekClient({
  accountOrAddress: '0x...',
  chains: [mainnet],
  transports: [http()],
  tools,
});

const result = await client.execute('getBalance', {
  address: '0x...',
  chainId: 1,
});

Using the MCP Server

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "agentek": {
      "command": "pnpx",
      "args": ["@agentek/mcp-server"],
      "env": {
        "ACCOUNT": "YOUR_ETHEREUM_ADDRESS",
        "PERPLEXITY_API_KEY": "...",
        "TALLY_API_KEY": "..."
      }
    }
  }
}

Use ACCOUNT for address context and unsigned EVM intents. Configure a signer or PRIVATE_KEY to submit EVM transactions; Solana signing is configured separately.

See the MCP Server README for full configuration details.

Using the CLI

# List all available tools
npx @agentek/cli list

# Search for tools by keyword
npx @agentek/cli search "swap"

# Get detailed info about a tool
npx @agentek/cli info intentApprove

# Execute a tool
npx @agentek/cli exec getCryptoPrice --symbol ethereum

See the CLI Guide for complete documentation.

Composing a custom tool set

You don't have to use all 205 tools. Import only what you need:

import { rpcTools, erc20Tools, defillamaTools } from '@agentek/tools';

const tools = [
  ...rpcTools(),
  ...erc20Tools(),
  ...defillamaTools(),
];

Tools (up to 205)

allTools({}) returns 191 tools. Optional service credentials add up to 14 more; availability depends on configuration. Host-integrated Nani tool sets may expose a different selection. Tool support also varies by chain.

Blockchain Core

DeFi

Cross-Chain

Market Data

Block Explorer (Blockscout)

33 tools covering addresses, transactions, blocks, tokens, smart contracts, and search across supported networks.

Governance

Social & Web

Security & Utility

Solana

Supported Networks

EVM

• Ethereum Mainnet
• Optimism
• Arbitrum
• Polygon
• Base
• Mode
• Sepolia

These are the default CLI/MCP EVM client networks; individual tools declare their own supported chains.

Solana

• Mainnet-beta by default. Tools take a cluster parameter (mainnet-beta, devnet, testnet) to switch cluster; a private or self-hosted endpoint is configured once via SOLANA_RPC_URL or solana.rpcUrl rather than passed per call.

Solana

Solana tools sit alongside the EVM ones and share the same client. Reads work with no configuration at all. Writes need a key, which lives in its own solana config block because Solana uses ed25519 keys rather than secp256k1:

import { createAgentekClient } from '@agentek/tools/client';
import { allTools } from '@agentek/tools';
import { http } from 'viem';
import { mainnet } from 'viem/chains';

const client = createAgentekClient({
  accountOrAddress: '0x...',
  chains: [mainnet],
  transports: [http()],
  tools: await allTools({}),
  solana: {
    // A base58 secret key (Phantom export), a JSON byte array
    // (solana-keygen), or the raw 64 bytes.
    privateKey: process.env.SOLANA_PRIVATE_KEY,
    rpcUrl: process.env.SOLANA_RPC_URL,
    jupiterApiKey: process.env.JUPITER_API_KEY,
  },
});

await client.execute('getSolBalance', {
  address: '5tzFkiKscXHK5ZXCGbXZxdw7gTjjD1mBwuoFbhUvuAi9',
});

SOL and SPL transfer intent tools mirror the EVM ones: with a key configured they sign and submit, returning the signature and confirmationStatus. A submitted or unknown outcome is not confirmation; reconcile the signature before retrying. Without a key, pass solana.address instead and they return the unsigned transaction as base64 for you to sign elsewhere. intentSwapSolana always returns Jupiter's untrusted transaction and request ID for an external wallet to decode, validate, simulate, approve, sign, and execute; agentek never signs or submits a Jupiter swap intent:

{
  "intent": "send 0.25 SOL to 5tzFki...",
  "chain": "solana",
  "transaction": "AQAAAAAA...",
  "signature": "4pF2s...",
  "confirmationStatus": "confirmed"
}

The public mainnet-beta endpoint is heavily rate limited — set SOLANA_RPC_URL to your own endpoint for anything beyond casual use.

Environment Variables

Most tools work without any API keys. Optional keys unlock additional features.

EVM tools fall back to public RPC endpoints, which are shared and rate limited — point RPC_URLS (or the per-chain variables) at your own provider for anything beyond casual use.

Copy the example to get started:

cp -n .env.example .env

Agent evaluations (Gym)

@agentek/gym runs agents against disposable, pinned Anvil forks using a public development account, restricted Agentek tools, and separate correctness, safety, and cost reports. It supports resumable suites and saved-report comparisons. Across destination settlement is simulated with an Anvil state override, rather than a destination bridge fill transaction. The included smoke fixtures are development tests, not a canonical benchmark.

See the Gym guide for setup and examples.

Development

git clone https://github.com/NaniDAO/agentek.git
cd agentek
pnpm i
pnpm run build
pnpm exec vitest run -c ./test/vitest.config.ts
# The default test script watches; the command above runs once.

Some existing tests call public RPCs or external APIs; a full run is not an offline test suite. A .env file is not automatically loaded by every command; pass it explicitly where needed, for example node --env-file=.env ....

Interested in contributing? Check out our CONTRIBUTING.md guide.

License

AGPL-3.0