the same on-chain read that powers the extension, exposed as a public API, no key, no wallet connect, just a handle in and a verdict out
# one GET, that is the whole api curl "https://lens-liard.vercel.app\ /api/lookup?username=exitliq_dev"
{
"verdict": "STOP",
"trust": 18,
"devSold": true,
"feeShare": "95%",
"liquidity": "unlocked",
"linked": ["@rugzn", "@dumpct"],
"funder": "shared"
}
no signup needed to try it, the endpoint is open and read only
an X handle like exitliq_dev, or a Base contract address starting with 0x
one GET to /api/lookup, no auth header, no body, nothing to sign
parse CLEAR CAUTION or STOP plus the signals behind it, and act before you ape
curl "https://lens-liard.vercel.app/api/lookup?username=exitliq_dev"
const handle = "exitliq_dev"; const res = await fetch( `https://lens-liard.vercel.app/api/lookup?username=${handle}` ); const read = await res.json(); if (read.verdict === "STOP") console.log("do not ape");
import requests handle = "exitliq_dev" read = requests.get( f"https://lens-liard.vercel.app/api/lookup?username={handle}" ).json() print(read["verdict"], read["trust"])
LENS resolves the deployer behind a profile and scores it into one word your agent can branch on
dev sold 3.4B to DEX, claims 95% of fees, account is 4 days old, strong rug pattern
the API hands back the full read, but the part that matters is verdict, a single value your bot can route on without parsing a block explorer
ship the skill pack or wire the MCP server, either way your agent vets a dev before it engages
a ready skill that takes a handle or contract and returns a CLEAR CAUTION STOP verdict, built for AEON and any agent that reads SKILL.md
expose lens-scan as an MCP tool so your model can pull the wallet read mid conversation and decide on its own
one route does the work, give it a target and read the fields it returns
| username | X handle to resolve, with or without the leading @ |
| contract | Base contract address starting with 0x, used in place of a handle |
| verdict | CLEAR, CAUTION, or STOP, the single value to branch on |
| trust | score from 0 to 100, higher is safer |
| devSold | true when the deployer dumped supply to a DEX router |
| feeShare | share of fees the dev captures |
| liquidity | locked or unlocked |
| linked | other handles sharing the same wallet |
| funder | shared or self, plus sibling deployer count |
only fields the read actually returns are present, a missing signal is omitted rather than guessed
try a scan in your terminal right now, or drop the skill into your agent and let it decide