ElizaOS is the most widely used open-source AI agent framework in crypto. It handles the hard parts of agent infrastructure — memory, multi-platform messaging, plugin composition — so you can focus on what your agent actually does.
Out of the box, an ElizaOS agent can hold a conversation, execute transactions, and interact with wallets. What it cannot do is answer questions like "which tokens are elite deployers launching right now?" or "are multiple KOLs accumulating the same token?" without external data.
The @madeonsol/plugin-madeonsol plugin fills that gap. It connects any ElizaOS agent to the MadeOnSol API, giving it live access to 1,000+ tracked KOL wallets, 15,500+ Pump.fun deployer profiles, and real-time DEX trade data. This post covers installation, configuration, available actions, and how to combine the plugin with Solana Agent Kit for a complete on-chain trading agent.
Prerequisites
- ElizaOS version
>=1.0.0 (the plugin lists @elizaos/core as a peer dependency)
- Node.js 22 or higher
- A MadeOnSol API key — get one free at madeonsol.com/pricing (BASIC tier: 200 calls/day, no payment required)
Installation
npm install @madeonsol/plugin-madeonsol
The package is published to npm under the @madeonsol scope. It has a single peer dependency on @elizaos/core >=1.0.0.
Step 1: Add the Plugin to Your Character
In ElizaOS, plugins are registered in the character definition. Import the plugin and add it to the plugins array:
import { madeonsolPlugin } from "@madeonsol/plugin-madeonsol";
import { Character } from "@elizaos/core";
const character: Character = {
name: "TradingAgent",
plugins: [madeonsolPlugin],
system: `You are a Solana trading research agent. You have access to real-time KOL trades,
deployer launches, and coordination signals via the MadeOnSol API.
When asked about market activity, always use the available tools to get live data.`,
bio: ["Tracks Solana KOL activity and surfaces deployer launches in real time."],
// ... rest of your character definition
};
export default character;
That is the complete integration. The plugin registers its actions with the ElizaOS runtime automatically when it is included in the plugins array.
Step 2: Environment Variables
The plugin supports three authentication modes. Set one of the following in your .env file:
Recommended — MadeOnSol API key:
MADEONSOL_API_KEY=msk_your_key_here
Alternative — RapidAPI key:
RAPIDAPI_KEY=your_rapidapi_key_here
RapidAPI is the legacy auth path. If you have a RapidAPI subscription for MadeOnSol, this works. New integrations should use msk_ keys from the developer portal.
x402 mode — agent pays per request from its own wallet:
SVM_PRIVATE_KEY=your_base58_encoded_private_key
In x402 mode, the agent holds SOL or USDC and pays a micropayment per API call. No subscription required. This is covered in detail in Step 6 below.
Step 3: Actions and What Triggers Them
The plugin registers five actions. ElizaOS actions are triggered by natural language — the runtime matches user input against each action's trigger phrases and metadata.
GET_KOL_FEED
Returns recent trades from tracked KOL wallets.
Trigger phrases: "what are KOLs buying", "show me recent KOL trades", "what's the KOL feed", "which KOLs traded recently", "show me smart money activity"
The action calls /api/v1/kol/feed and returns a formatted list of recent trades with wallet names, token symbols, SOL amounts, and timestamps.
GET_KOL_COORDINATION
Returns tokens where multiple KOLs are trading in the same direction.
Trigger phrases: "what tokens are multiple KOLs buying", "any coordination signals", "which tokens have KOL convergence", "are KOLs accumulating anything", "show me coordination"
The action calls /api/v1/kol/coordination and returns tokens with their signal (accumulating or distributing), kol_count, net_sol_flow, and the wallet names involved.
GET_KOL_LEADERBOARD
Returns ranked KOL wallets by performance.
Trigger phrases: "top performing KOLs", "who's up most this month", "KOL leaderboard", "best KOL traders", "who has the highest PnL"
The action calls /api/v1/kol/leaderboard with a configurable time window (default: 30 days) and returns ranked wallets with PnL, win rate, and strategy tags.
GET_DEPLOYER_ALERTS
Returns newly launched tokens from tracked Pump.fun deployers.
Trigger phrases: "any new elite deploys", "what launched today", "show me deployer alerts", "new launches from good deployers", "any fresh tokens from elite deployers"
The action calls the deployer-hunter alerts endpoint, filters by tier, and returns recent launches with deployer tier, token name, mint, and launch time.
GET_TOKEN_INFO
Returns detailed information about a specific token by mint address.
Trigger phrases: "what's the market cap of [mint]", "is this token from a good deployer", "token info for [address]", "check this mint", "who deployed [mint]"
The action extracts the mint address from the user's message and calls /api/v1/token/{mint}, returning deployer tier, market data, social links, and KOL activity.
