Integrations Overview

web3agent bundles ten integrations that load automatically when the server starts. There's no plugin installation or manual registration. Every tool from every integration is immediately available to any MCP-compatible AI agent the moment npx web3agent runs.

The integrations span three broad categories: on-chain execution (Orbs, LI.FI, EVM), indexed data (Blockscout, GOAT SDK), and the agentic economy (ACP, aGDP, ERC-8004, X-402). CCXT covers centralized exchange access.

Integration Table

Integration	Tool Prefix	Capabilities	Required Config
Orbs	`orbs_`	Liquidity Hub swaps, dTWAP, dLIMIT, Spot orders	None
LI.FI	`lifi_`	Cross-chain bridges and swaps (20+ chains)	`LIFI_API_KEY` (optional, for higher rate limits)
GOAT SDK	varies	Uniswap, Balancer, ERC-20/721, ENS, DexScreener	None (0x: `ZEROX_API_KEY`, CoinGecko: `COINGECKO_API_KEY`)
Blockscout	`blockscout_`	Indexed blockchain data (addresses, txs, NFTs, ABIs)	None
EVM	`evm_`	Live on-chain state (balances, reads, writes, gas, ENS)	None
CCXT	`ccxt_`	Exchange discovery and public/private CEX access	`CCXT_CONFIG_PATH` (for private calls)
ACP	`acp_`	Agent Cooperation Protocol job lifecycle	None
aGDP	`agdp_`	Agent marketplace (hire, offer, discover)	None
ERC-8004	`erc8004_`	On-chain agent identity and reputation	None
X-402	`x402_`	HTTP-native stablecoin payments	None

How Integrations Load

When the MCP server starts, it registers all tool definitions from every integration into a single flat namespace. An AI agent calling orbs_swap or evm_get_balance goes through the same invocation path regardless of which integration owns the tool.

npx web3agent
  → loads all integrations
  → registers 100+ tools
  → starts MCP stdio server
  → AI agent connects and discovers tools

No configuration is needed to activate most integrations. The exceptions are:

LI.FI: works without a key but rate limits apply. Set LIFI_API_KEY for production use.
GOAT SDK 0x plugin: requires ZEROX_API_KEY to activate.
GOAT SDK CoinGecko plugin: requires COINGECKO_API_KEY to activate.
CCXT private calls: require CCXT_CONFIG_PATH pointing to a JSON credentials file.

Programmatic SDK

Every integration also exposes SDK functions for use in Node.js projects. Import from the web3agent package:

import {
  prepareSwapIntent,   // Orbs
  prepareBridgeIntent, // LI.FI
  resolveToken,        // Token resolver
  getAddressInfo,      // Blockscout
} from "web3agent";

// aGDP and X-402 have dedicated entry points
import { AgdpClient } from "web3agent/agdp";
import { fetchWithPayment } from "web3agent/x402";

SDK functions call the same underlying tool handlers as the MCP layer. The behavior is identical whether an AI agent invokes a tool over MCP or a Node.js application calls the SDK function directly.

Choosing Between Integrations

Some capabilities overlap. Here's a quick guide:

For token swaps on the same chain: Orbs Liquidity Hub (orbs_swap) aggregates liquidity across DEXs and runs a solver auction. For simple swaps, it's the best starting point.

For cross-chain transfers: LI.FI (lifi_execute_bridge) handles routing across 20+ chains and picks the best bridge automatically.

For historical transaction data: Blockscout (blockscout_ tools) queries indexed data. For live state like current balances or contract storage, use EVM tools (evm_ prefix) instead.

For advanced order types: Orbs Spot orders support dTWAP (time-weighted average price), dLIMIT (execute at target price), stop-loss, and take-profit. These are on-chain orders settled by a keeper network.

For CEX data or trading: CCXT tools cover public market data and, with credentials configured, private account access across hundreds of exchanges.