version: "1.0.1" name: agentek-cli description: Invoke any of 150+ blockchain and data tools from the shell using the agentek CLI. Use this skill when the user wants to query blockchain data, check token balances, resolve ENS names, get gas prices, fetch DeFi yields, search tweets, or interact with any on-chain protocol across EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon). license: AGPL-3.0 compatibility: Requires Node.js >= 18.17.0 and npx or global install of @agentek/cli metadata: author: NaniDAO version: "1.0"

agentek CLI

Overview

Agentek is a command-line interface that exposes 150+ blockchain and data tools as simple shell commands. Each tool has a typed schema, accepts flags, and returns structured JSON on stdout.

Install globally or run via npx:

# Global install
npm install -g @agentek/cli
 
# Or run directly
npx @agentek/cli <command>

Commands

Setup and configuration

Check which API keys are configured:

agentek setup

Save a key to the config file (~/.agentek/config.json):

agentek config set PERPLEXITY_API_KEY pplx-xxxxxxxxxxxx

View a saved key (redacted by default):

agentek config get PERPLEXITY_API_KEY
agentek config get PERPLEXITY_API_KEY --reveal

List all known keys with their status:

agentek config list

Remove a key from the config:

agentek config delete PERPLEXITY_API_KEY

Environment variables always take precedence over config file values.

Tool discovery and execution

The CLI follows a discovery workflow: list / search -> info -> exec.

1. List all tools

agentek list

Returns a sorted JSON array of every available tool name.

2. Search for tools

agentek search balance
# [{"name":"getBalance","description":"..."},{"name":"getTokenBalance","description":"..."}]

Searches tool names and descriptions (case-insensitive).

3. Inspect a tool

agentek info <tool-name>

Returns a JSON object with the tool's name, description, parameters (JSON Schema), and supportedChains.

4. Execute a tool

agentek exec <tool-name> [--key value ...]

Runs the tool with the given parameters and prints the JSON result to stdout.

Flag syntax

Values are automatically coerced to the type expected by the tool's schema (number, boolean, string).

Output contract

• stdout — Always valid JSON (the tool result or a JSON array for list).
• stderr — JSON object {"error": "message"} on failure.
• Exit codes:
• 0 — Success
• 1 — Runtime error (tool failed, invalid input, timeout)
• 2 — Usage error (bad command, missing arguments)

Environment variables

Set these before running commands that need them:

Examples

List all available tools:

agentek list
# ["getBalance","getBlock","getBlockNumber",...]

Inspect a tool before using it:

agentek info getBalance
# { "name": "getBalance", "description": "...", "parameters": {...}, "supportedChains": [...] }

Get the latest block number on Ethereum mainnet:

agentek exec getBlockNumber --chainId 1
# { "blockNumber": "21547832" }

Check an address's ETH balance:

agentek exec getBalance --address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 --chainId 1

Resolve an ENS name:

agentek exec getEnsAddress --name vitalik.eth --chainId 1

Tips

• Always run agentek info <tool> before exec to see required parameters and their types.
• Use --chainId to target a specific chain. Common chain IDs: 1 (Ethereum), 10 (Optimism), 42161 (Arbitrum), 137 (Polygon), 8453 (Base).
• Tools that write on-chain require PRIVATE_KEY. Read-only tools work without it.
• Pipe output to jq for filtering: agentek exec getBalance --address 0x... | jq '.balance'.
• The CLI times out after 120 seconds per tool execution.