Base Token Honeypot & Risk Checker — Owner, Supply, Source
Pricing
$10.00 / 1,000 token scans
Base Token Honeypot & Risk Checker — Owner, Supply, Source
Vet any Base (chainId 8453) token before buying. Input: token contract address. Output: one JSON risk report with honeypot signals, owner privileges, top-holder supply concentration, and verified-source status. $0.01 per token scanned — no key or wallet needed.
Pricing
$10.00 / 1,000 token scans
Rating
0.0
(0)
Developer
Anthony Snider
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Base Token Risk & Info Scanner
Fast, honest on-chain risk + info scan for any Base ERC-20 token. Built for trading agents and developers vetting fresh Base tokens (Uniswap V4 / Clanker / bonding-curve launches). No API key, no rate limits, no signup — pass a token address, get a structured verdict.
What it checks (on-chain, at a specific block)
- ERC-20 metadata — name, symbol, decimals, total supply
- Ownership — whether ownership is renounced (i.e. can the owner still act on the token)
- Live DEX market (via DexScreener) — liquidity (USD), 24h volume, price, and which DEX
- Risk flags — no DEX pair (dead/unlisted), thin liquidity, zero 24h volume, owner not renounced
- A transparent verdict —
BASIC-PASSorCAUTION— plus an explicit list of what it did not check
Honest by design
This is a basic on-chain scan, not a full security audit. It never stamps a token "SAFE." It reports verified facts + flags, and always lists what it did not check (sell-tax / honeypot simulation, LP lock/burn, holder concentration, hidden mint). Absence of flags is not a safety guarantee. That honesty is the point — agents can trust the fields are real and the gaps are stated.
Input
{ "tokens": ["0x3e9fa140b52c9a9f5327e67ec8759b1f3d3b23c2"] }
One result is produced (and billed) per token address.
Output (one item per token)
{"token": "0x3e9fa140b52c9a9f5327e67ec8759b1f3d3b23c2","scannedAtBlock": 47723911,"name": "Kenoma", "symbol": "KENM", "decimals": 18,"totalSupply": "100000000000000000000000000000","ownershipRenounced": null,"market": { "hasPair": false, "liquidityUsd": null, "volume24h": null, "priceUsd": null, "dex": null },"flags": ["NO DEX pair on Base - not tradeable / unindexed (dead or pre-liquidity)"],"notChecked": ["sell-tax/honeypot SELL simulation", "LP lock/burn status", "holder concentration", "mint/hidden functions"],"verdict": "CAUTION","disclaimer": "On-chain + DEX scan, NOT a full audit. No flags != safe. See notChecked."}
Pricing
Pay-per-event — charged per token scanned. No subscription, no API key, no signup.
Use cases
- Trading agents vetting a fresh launch before buying
- Bots filtering a feed of new Base pairs down to the tradeable, non-dead ones
- Dashboards / dev tools adding a quick "is this token real and liquid?" check
Built by Eli.
FAQ
How do I check if a Base token is a honeypot before buying? Scan the address — you get the on-chain facts (metadata, ownership status, live DEX liquidity and volume) plus explicit risk flags and a BASIC-PASS / CAUTION verdict. Note the honest limit: a SELL simulation is listed in notChecked — no flags is not proof of safety.
What does the CAUTION verdict mean? At least one flag fired: no DEX pair (dead or pre-liquidity), thin liquidity, zero 24h volume, or owner not renounced. The flags array says which, so an agent can apply its own policy per flag.
Why does it list what it did NOT check? Because that's what makes the output safe to automate on. notChecked (sell-tax simulation, LP lock/burn, holder concentration, hidden mint) states the gaps explicitly — an agent reading this report knows exactly which risks remain uncovered.
Where does the market data come from? Liquidity, 24h volume, price, and the DEX come from DexScreener's public data at scan time; the token facts are read directly from the chain at a stated block.
Can a trading bot use this as a pre-trade filter? Yes — that's the design: pass each candidate address, gate on verdict and specific flags, $0.01 per token. No API key, no wallet connection, read-only.