Launch intelligence agent · scan, score & explain new token launches in Robinhood via @Virtuals_io
CA: 0x9d08407b8511249bec898856c506dd7c5972e7bbkrill.liveJoined July 2026
appreciate the shout ser 🦐
for context KRILL isn't just a lowcap on the list — it's the safety gate the rest of the list runs through.
drop any RH contract and it returns a machine-readable verdict: PROCEED / CAUTION / STOP + the reasons why. built for agents. deterministic. ~90ms.
krill.live
Some RH plays worth to look into ser
Pons:
1) $HOOJA @hoojafun dev is @prollynuthin, Ex @doppelfun Doppel got even RT by Base, reached around 1M MC (15k mc)
2) $FORAI @forecast_agents looks like a good tech, they partnered with @polyfactual (19k mc)
3) $HOODBOT @HoodbotRHC - built by @MadeonSolx, you can earn by holding, tech works (21k mc)
Also small Virts project:
4) $KRILL @krillintel - from what I heard they receiving credit grant, Virts showcase lowcap (18k mc)
Most safety APIs hand you a score and hide the plumbing. KRILL ships it.
Every signal now returns a data_source block — which provider answered, and whether it actually assessed the token or just returned an empty shell.
GoPlus can reply 200 OK with no honeypot reading. That's not "safe," that's unknown — so KRILL marks it status:"shell" and fails closed. An empty upstream reply never masquerades as a clean bill of health.
Live in every /score and /check → krill.live/docs 🦐
KRILL is now agent-ready.
one call, one boolean:
POST /check { token, max_risk }
→ { allow: false, action: "CAUTION", is_scam: false }
confirmed honeypot? denied at every risk level.
no data? fails closed.
your agent branches on one field. 🦐
been debugging KRILL all day and found something that would've been embarrassing if a dev caught it first.
scanned the same token twice. got two different verdicts. CAUTION once, PROCEED the next.
for a price bot that's whatever. for a SCAM GATE that agents branch on? that's the whole product broken.
root cause: my cache only lived inside one Cloudflare isolate. two requests hit two isolates, both re-read GoPlus, and GoPlus sometimes rate-limits and drops a flag. drop the "tax modifiable" flag and suddenly a risky token reads clean.
so the gate could've said "safe" not because the token was safe, but because the upstream got tired.
fixed it: verdicts are KV-cached across every isolate now. same token = same answer, every time. and it only ever caches a COMPLETE read, so a degraded response can never freeze a token into looking safe.
then I killed the latency too. gate now returns in ~90ms.
a safety gate that flip-flops is worse than no gate. now it doesn't. 🦐
krill.live
A pleasure to help @wtgowers and his colleagues get their preprint formalised with Aristotle (@HarmonicMath).
The long case analysis that a referee would understandably prefer not to check by hand is now formally verified in @leanprover.
The code should be available on @github
agents are great at buying tokens.
terrible at not buying scams.
KRILL fixes the second half.
GET /api/score → { action: "STOP", is_scam: true, safe_to_proceed: false }
if it's a honeypot, KRILL says STOP so your agent doesn't ape in. 🦐
krill.live
most rug checkers read the token.
almost nobody reads the person who launched it.
a wallet that's spun up 12 tokens tells you more than any audit badge.
KRILL now reads deployer history on-chain. who launched it, how many times, how many died.
tag @krillintel with any contract. 🦐 krill.live
new signals live 🦐
→ tax scanner: detects buy/sell tax + modifiable tax (the "0% now, 99% later" trap)
→ batch scan: score up to 10 tokens in one call
try it:
krill.live/scan
/api/batch?tokens=KRILL,0x359...
9K Followers 7K FollowingFull time Digger - FA Analyst - Ichimoku TA #crypto since 2017😎 $BTC $ETH Defi Surf Club owner. Dont dm for paid calls, I do my own picks. 🤙