What a Base honeypot checker tells you
A honeypot check is designed to identify tokens that appear buyable but cannot be sold normally, or that expose related transfer restrictions. It is an important blocker, but it is only one part of a pre-trade risk check.
Why “not a honeypot” is not the same as “safe”
A token can be sellable and still have upgradeable permissions, minting risk, high taxes, shallow liquidity or concentrated holders. Market conditions and contract state can also change after a scan.
How to check a Base token
- Copy the exact 42-character ERC-20 contract address. Do not rely on a ticker symbol.
- Run the address through the Jepeta Base scanner.
- Read the PASS / WARN / BLOCK result together with the raw signals and source status.
- For WARN or BLOCK, inspect the specific evidence rather than treating the score alone as the decision.
- Apply your own execution policy. Jepeta does not connect to your wallet or execute trades.
For autonomous agents
The free preview is a GET-only JSON endpoint, so an agent can place Jepeta between token resolution and its own execution policy.
For strict field definitions and error behavior, use the OpenAPI contract and LLM guide.
Frequently asked questions
How do I check if a Base token is a honeypot?
Use the exact Base contract address and a current security source. Jepeta uses GoPlus as the required security source and adds market context from DEX Screener when available.
Does PASS mean the token is safe?
No. PASS is a screening result at one point in time. The underlying contract, liquidity and available data can change.
Does Jepeta need wallet access?
No. The free scanner is read-only. No wallet connection, signature or payment is required for the preview.