UnifAI CLI

A CLI for searching and invoking services on the UnifAI network. Supports 40+ services across DeFi, token data, social media, web search, news, travel, sports, and utilities.

What it does

unifai enables you to:

• - Search services: Find services and actions using natural language queries
• Invoke services: Execute actions with customizable parameters and retry logic
• Manage configuration: Configure API keys with multiple priority levels

Available service categories

• - DeFi: Swap, lend, borrow, provide liquidity (Aave, Uniswap, Jupiter, Meteora, Pendle, Compound, 1inch, and more)
• Token & market data: Prices, OHLCV, security analysis (Birdeye, CoinGecko, DexScreener, DefiLlama, GoPlusSecurity)
• Wallet & chain data: Token balances across Solana, Ethereum, Base, BSC, Polygon
• Social media: Twitter/X search, user timelines, tweet threads
• Web search & news: General search, Google news, financial data (SerpAPI, Tavily)
• Travel: Flight and hotel search
• Sports: NBA scores, soccer results (ESPN)
• Utilities: Math, time, domain availability, Solana rent reclaimer

Installation

Install globally so the binary is available locally:

CODEBLOCK0

Or use via npx (no install needed)

CODEBLOCK1

Setup

Set your API key:

CODEBLOCK2

Or create a config file:

CODEBLOCK3

Commands

Search for tools

Always returns JSON with full payload schemas (best for agents):

CODEBLOCK4

Compact numbered list (strips schemas):

CODEBLOCK5

Invoke an action

CODEBLOCK6

With transaction signing:

CODEBLOCK7

Payload from file:

CODEBLOCK8

Sign a transaction

CODEBLOCK9

Configuration

CODEBLOCK10

Version

CODEBLOCK11

Agent Workflow

CRITICAL: Always search before invoking. Each action has its own field names (e.g. toWalletAddress for Solana, recipientWalletAddress for Polygon). Do NOT guess field names — they will fail silently or return cryptic server errors.

1. 1. Search to get the action ID and exact payload schema:

1. 2. Read the payload field in the JSON response. It contains every field name, type, and whether it's required. Use these exact field names.

1. 3. Invoke with the correct payload:

1. 4. If --sign is used and the response contains a txId, the transaction is automatically signed and submitted locally.

Important: Field Names Are Not Guessable

Different actions use different field names for similar concepts. Examples:

Always use unifai search first and read the payload schema. Never guess field names.

Understanding Errors

• - Error: API key is required — Set UNIFAI_AGENT_API_KEY env var
• Error: ... private key is required — Set SOLANA_PRIVATE_KEY or EVM_PRIVATE_KEY for signing
• Error: RPC URL is required — Public defaults are provided, but you can override with env vars (e.g. POLYGON_RPC_URL)
• Server-side errors (e.g. "error": "Failed to create transaction: ...") — Usually wrong field names or invalid values. Re-check the payload schema from INLINECODE23
• --sign with no txId — Normal. The action didn't need signing; the response is returned as-is

Transaction Signing

Transaction signing is optional and requires private keys via environment variables:

• - SOLANA_PRIVATE_KEY — Solana key (base58, JSON array, or path to keystore file from solana-keygen)
• INLINECODE27 — EVM key (hex, with or without 0x prefix). Used for Ethereum, Polygon, Base, BSC, Hyperliquid, and Polymarket

RPC URLs (optional, public defaults are provided):

• - SOLANA_RPC_URL — default: INLINECODE29
• INLINECODE30 — default: INLINECODE31
• INLINECODE32 — default: INLINECODE33
• INLINECODE34 — default: INLINECODE35
• INLINECODE36 — default: INLINECODE37

Public RPCs are rate-limited. Set your own RPC URLs for production use.

All signing happens locally within the CLI process. Private keys are used only by the local @solana/web3.js and ethers libraries to sign transactions before submission. The CLI source code is available at https://github.com/unifai-network/unifai-sdk-js/tree/main/src/cli.

Common Examples

CODEBLOCK14

Security Notes

• - Private keys: SOLANA_PRIVATE_KEY and EVM_PRIVATE_KEY are only needed for transaction signing.
• Local signing: All transaction signing happens locally in-process using @solana/web3.js and ethers. Private keys are never sent to external API.