Scan X around the clock. Build a thesis on a coin from the very first time anyone writes about it, and keep updating it until the story dies. Work out where momentum actually is, and eventually place the trade without a human in the loop.
Everything below is that note turned into something buildable, with the parts that are hard stated as hard rather than hidden.
Not one agent doing everything. Six narrow jobs, each cheap to run and each independently checkable, because a wrong answer in one of them has to be visible instead of blended into a confident summary.
Pulls posts from a watchlist of accounts in batches, plus keyword and cashtag sweeps for tickers nobody on the list has mentioned yet. Extracts ticker, contract address, chain and whether the post is a call, a mention or paid promo.
The moment a token is seen for the first time, it gets a file. Every later mention is appended with who said it, when, and how big their audience is. The file is the coin's biography: first sighting, who picked it up, when the tone changed, when it died. Nothing is ever overwritten.
Backtests every account on its own past calls. Median return, hit rate, and the only number that really matters: how early they are relative to everyone else on the same coin. An account that is loud but late is worse than useless, it is a sell signal.
Before you ever see an alert: pool age, liquidity, is the LP burned, what the dev wallet holds, top ten holder concentration, and whether the contract can be minted or frozen. Kills most candidates outright. This is the filter that stops the fleet becoming a rugpull delivery service.
The CYBERLEEK pattern: not one caller, but more and more accounts talking about the same thing while the gaps between mentions get shorter. Fires when two or more scored accounts converge on one contract inside a window and the rate is accelerating - not on any single tweet.
And it fires again on the way out. The same counter that says get in says get out: the moment the known-late accounts and the automated whale feeds start posting the ticker, the crowd has arrived and there is nobody left to sell to. On CYBERLEEK that was whalewatchalert and dexvralisting, half an hour behind the wave. Exit alert, not a buy alert.
Last, and switched off. Fixed size per call, a hard daily cap, an automatic exit ladder, and a separate wallet holding nothing but the trading budget. Cannot run until the five agents above have a track record on paper.
Build the watchlist and backtest it. No list exists yet, so the fleet seeds its own: work backwards from CYBERLEEK, CATE and EGG and find who mentioned each of them first, then second, then third. Those accounts become candidates, and their own history gets scored the same way. Deliberately slow - batched scrapes, spread over days, so nothing gets hammered. Output: a ranked list of who is genuinely early.
Every token the scouts see gets a file from first sighting. Runs read-only for a few weeks so we can look back and ask: at what point in this file was it obvious? That question cannot be answered on historical data alone, because dead tokens lose their pool history and quietly drop out of any backtest, flattering the result.
Convergence plus safety check, pushed to WhatsApp within minutes with liquidity, market cap, pool age and the thesis so far. Every alert is logged with entry price at alert time, so the scoreboard on this page is not curated afterwards.
Fixed size into every alert, exits by rule, no discretion. Compared against the benchmark below. If paper does not clear it over a meaningful number of trades, the project stops here, and that result gets published on this page too.
Separate wallet, funded with the trading budget only, seed used nowhere else. Hard per-trade and per-day limits. Never the main wallet - whatever key sits on that machine is a key the machine can spend.
One caller was backtested properly before any of this was built. Everything the fleet produces gets measured against it - if a whole agent fleet cannot beat one guy's timeline, it is not worth running.
| Strategy | Return |
|---|
Full call-by-call breakdown: stitch-calls-concept.jouwidealewebsite.nl
Read live from the billing API, not from a tally the system keeps about itself. The loop checks it before every single scrape and refuses to start one that would cross the line - at the ceiling it stops scraping and keeps publishing, it does not slow down and carry on.
Roughly 0.0002 dollar per post, and only ever batched - one request covers four accounts at once. Polling accounts separately is billed per query and would run into hundreds a day, so the fleet never does it.
One batch every six hours, one at a time, with a wait between every price lookup. Roughly sixteen accounts a day. Nothing here is time-critical, and the same machine also runs the CRM, WhatsApp and the NFT watchers - those come first.
A single node process under PM2, asleep almost all the time. Price history comes from a free endpoint at one request every 2.5 seconds, well under its limit. Stop it any time with pm2 stop crypto-agents.
| Date | Change |
|---|