Skip to main content

Requirements

  • Node.js v18 or higher
  • npm (included with Node.js)
  • A running fibx-server instance only if you use Privy-managed wallet operations
No global installation is needed. All commands use npx fibx@latest, which always fetches the latest version (currently v0.8.2).

Installation Options

Run FibX directly with npx:
Or install it globally:

Installing Agent Skills

To add fibx skills to your AI agent, use the Vercel Skills CLI:
This installs the pre-built skill definitions from the fibx-skills repository into your agent’s skill registry. No separate installation of fibx is needed — all skills execute via npx fibx@latest.

Verify Your Environment

Try It Without a Wallet

Before setting anything up, you can check live prices — quote needs no session, wallet, or keys:

Authentication

Commands that inspect or act on a wallet — including address, wallets, balance, portfolio, send, trade, aave status, and Aave actions — need an active session. Public or local commands such as quote, status, tx-status, config, and aave markets can run without one. Two authentication methods are available: If you already have a wallet with a private key, this is the fastest way to get started. The key is encrypted and stored in a local session file for the duration of the session. This mode does not require fibx-server.
Your private key will be stored locally in an encrypted session file. Only use this method on a trusted device.
This is ideal for developers and agents that already manage their own wallets. The imported key is used directly for signing transactions — no external server holds your key.

Email OTP (Alternative — Privy Server Wallets)

If you do not have a private key or prefer a managed wallet, you can authenticate via email OTP. This creates a server-managed wallet through Privy. Signing is requested through fibx-server, and the private key itself is not returned to the CLI. This mode requires fibx-server to be running and reachable.

Session Management

Common Command Options

These flags are available where shown in the command reference:

Chain Selection

Commands that accept --chain default to Base unless their reference says otherwise.

First Transaction

After authenticating, run through a complete workflow to verify everything is working:
1

Check your balance

2

Execute a swap

The CLI finds a route via Fibrous, handles any required token approval, estimates the swap where supported, and submits it.
3

Verify the transaction

This returns the on-chain status, gas used, and a block explorer link.

Preview Behavior

send --simulate, trade --simulate, and Aave actions with --simulate return a no-broadcast preview. Review the result and the command-specific limitations before submitting the live operation.
Preview output varies by path. If an ERC-20 trade needs approval, trade --simulate reports requiresApproval: true without submitting the approval or returning a gas estimate. An Aave preview returns the normalized request only; it does not perform on-chain validation or estimate gas. Preview success does not guarantee that later execution will succeed.