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, 6,700+ 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/developer (BASIC tier: 200 calls/day, no credit card)
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.
Step 4: Example Agent Conversation
Here is a realistic example of what an ElizaOS agent with the plugin installed looks like in practice. The agent is connected to a Telegram channel:
User: Any elite deployers launch in the last hour?
Agent: Let me check that for you.
[Agent calls GET_DEPLOYER_ALERTS with tier=elite, window=1h]
Found 2 launches from elite-tier deployers in the last hour:
MOONCAT (mint: 7xKp...q3Bm) — launched 23 minutes ago by deployer DPeR...9wKz (elite tier, 14 graduates, 87% win rate)
SOLGHOST (mint: 2nQr...mT4v) — launched 51 minutes ago by deployer FxWq...8rLp (elite tier, 22 graduates, 91% win rate)
Want me to check if any KOLs are accumulating either of these?
User: Yes, check MOONCAT
Agent: Checking KOL activity on MOONCAT.
[Agent calls GET_TOKEN_INFO with mint 7xKp...q3Bm]
MOONCAT currently has 3 KOLs in accumulation mode with a net SOL inflow of 4.2 SOL in the last hour. The token is at roughly 18% of its bonding curve. Deployer has a strong graduation track record. The coordination signal is accumulating.
The agent handles the full research workflow — deployer reputation check, KOL sentiment, coordination signal — in two conversational turns.
Step 5: Combining with Solana Agent Kit
The MadeOnSol plugin handles intelligence and research. To turn that research into executed trades, combine it with the Solana Agent Kit:
npm install solana-agent-kit-plugin-madeonsol
With both plugins loaded, your agent can:
- Detect an elite deployer launch (MadeOnSol
GET_DEPLOYER_ALERTS)
- Check KOL coordination on the new token (MadeOnSol
GET_KOL_COORDINATION)
- Execute a swap via Jupiter or Pump.fun (Solana Agent Kit)
- Set a take-profit or stop-loss trigger (Solana Agent Kit)
The two plugins are designed to work together. MadeOnSol surfaces the signal; Solana Agent Kit executes on it. You configure both in the same character definition.
Step 6: x402 Mode — Agent Pays Per Request
Standard API key auth is subscription-based: you pay monthly and get a daily call quota. x402 mode inverts this. Instead of a subscription, the agent holds SOL or USDC in its own wallet and pays a micropayment for each API call.
Set the environment variable:
SVM_PRIVATE_KEY=your_base58_encoded_private_key
The plugin detects the presence of SVM_PRIVATE_KEY and switches to x402 mode automatically. No other configuration changes are needed.
Use x402 mode when:
- The agent is fully autonomous and should not depend on a human-managed subscription
- You are running many short-lived agents, each with their own funding
- You want precise cost accounting per agent or per task
- You prefer not to commit to a monthly subscription during experimentation
For production agents with consistent high-volume usage, a PRO subscription ($49/month, 10,000 calls/day) will be more cost-efficient than per-call payments. The break-even point depends on how frequently your agent calls the API.
Tier Notes
BASIC (free, 200 calls/day): Suitable for low-volume agents — for example, a Telegram bot that answers a few research questions per day. No credit card required.
PRO ($49/month, 10,000 calls/day): Suitable for production agents running in background, polling coordination signals every few minutes, or handling multiple users.
ULTRA ($199/month, 100,000 calls/day): For high-frequency setups, multiple concurrent agents, or platforms serving many users.
Get your API key at madeonsol.com/developer.
