Base token risk guides
Direct answers to questions people and autonomous agents ask before acting on a Base token. Each guide links back to methodology, current public evidence and a fresh scan path.
What Base token risk API can an AI agent use before execution?
An AI agent should call a deterministic, machine-readable risk endpoint with an exact Base contract address and treat the result as policy input rather than natural-language advice. Jepeta exposes a GET-only public preview, OpenAPI, agent manifests, methodology, a public signal feed, and permanent evidence URLs.
WorkflowWhat should I check before buying a Base token?
Before a Base token trade, verify the exact contract, then check honeypot status, mintability, taxes, holder concentration, liquidity, observed LP-lock evidence, data quality, and source freshness. A single green metric is not enough; the goal is to catch reasons to stop or review before execution.
Agent ApiCan I check Base token risk without connecting a wallet?
Yes. A pre-trade token-risk check can be completely read-only: provide the exact Base contract address and retrieve security and market evidence without wallet connection, approvals, signatures, or custody. This reduces the scanner's own attack surface.
ComparisonWhat is the difference between a honeypot check and a token risk check?
A honeypot check asks a narrow execution question: can the token be sold under the tested conditions, and are there suspicious transfer or tax behaviors? A broader token-risk check also considers permissions, supply controls, liquidity, holder concentration, evidence completeness, and other reasons to stop or review.
Risk SignalHow do I check if a Base token is a honeypot?
Use an exact-contract honeypot check that can return an explicit boolean rather than guessing from missing data. On Base, a honeypot check is an important first gate, but it is not the whole risk assessment: a token can be sellable and still be mintable, heavily taxed, illiquid, or highly concentrated.
Risk SignalHow do I check holder concentration risk for a Base token?
Review the share held by the largest observed holders, but do not treat wallet counts as beneficial ownership. High concentration can amplify dump, governance, or control risk; low concentration does not prove decentralization because contracts, exchanges, custodians, and related wallets can distort the picture.
Risk SignalHow do I check whether Base token liquidity is locked?
Look for lock evidence on the relevant liquidity position, but separate observed lock coverage from a claim that all liquidity is locked forever. A lock is useful context, not proof that a token is safe or that every pool is protected.
Risk SignalHow do I check liquidity risk for a Base token?
Check liquidity on the exact matching Base pair and distinguish missing market data from zero liquidity. Thin liquidity can increase slippage and make exits fragile; unavailable data should trigger caution rather than a fabricated zero-risk or zero-liquidity assumption.
Risk SignalHow do I check buy and sell tax on a Base token?
Check the exact Base contract with a source that reports buy and sell tax separately, and keep unavailable values as unknown rather than zero. High or asymmetric taxes can materially change execution risk even when a token is not a honeypot.
EvidenceHow can I monitor new Base token risk signals?
Use a recent-signal feed for discovery and permanent evidence pages for durable verification. Jepeta's risk feed lists recently published Base signals; when a token meets the evidence-quality gate, it can also receive a stable HTML and JSON evidence URL.
EvidenceHow should I use a permanent Base token risk evidence page?
Use a permanent evidence page as a timestamped record of what Jepeta publicly observed for an exact Base token at a specific time. It is designed for verification, citations, comparisons, and audit trails. For a current trade, use the page's fresh-scan link because token and market conditions can change.
DiscoveryIs this Base token safe?
No scanner can prove that a token is safe. A useful pre-trade check should instead ask whether the exact Base contract shows known risk signals now: honeypot behavior, mintability, unusual taxes, weak liquidity, concentrated holders, incomplete source data, or other reasons to stop and review. Jepeta turns those signals into PASS, WARN, or BLOCK, but PASS is not a safety guarantee.
ComparisonWhat is the difference between Jepeta and GoPlus Token Security?
GoPlus is a security-data provider; Jepeta consumes GoPlus token-security evidence as a required input and adds its own Base-specific policy layer, DEX Screener market context, data-quality semantics, public evidence publishing, and agent-commerce surface. Jepeta is not a replacement for GoPlus inside its own architecture.
ComparisonHow is Jepeta different from Honeypot.is for Base tokens?
The tools overlap on honeypot and tax screening, but they are not identical products. Honeypot.is centers its documented API around honeypot checks and transaction simulation details. Jepeta uses explicit token-security evidence plus Base market context to produce a deterministic PASS/WARN/BLOCK policy, machine-discovery surfaces, and permanent public evidence pages.
ComparisonHow is Jepeta different from TokenSniffer on Base?
TokenSniffer and Jepeta both support Base-related token screening, but their surfaces and emphasis differ. TokenSniffer documents broad multi-chain scam and contract analysis plus Base DEX and locker coverage. Jepeta is narrowly focused on Base pre-trade policy, explicit source-quality semantics, agent-readable contracts, and permanent evidence URLs.
Agent ApiWhat makes a token risk API machine-readable?
Machine-readable means more than returning JSON. A useful risk API has a versioned schema, stable field semantics, explicit null/error behavior, deterministic identifiers, documented limitations, and discoverable contracts such as OpenAPI or agent manifests.
Agent ApiHow do I add a pre-trade risk gate to a Base trading bot?
Put the risk gate before transaction construction or signing: resolve the exact Base token, call a deterministic risk API, validate the schema, and convert the result into explicit stop/review/continue rules. Do not let an LLM free-form its way around missing evidence.
Risk SignalWhat does it mean if a Base token is mintable?
Mintable means the token contract or an authorized role can create additional supply under the conditions exposed by the security source. That is not automatically malicious, but it changes the risk model because future supply can dilute holders or be used in abusive ways if the permission is uncontrolled or compromised.
InterpretationWhat do PASS, WARN, and BLOCK mean in token risk screening?
PASS, WARN, and BLOCK are policy decisions, not predictions. BLOCK means Jepeta observed a configured hard blocker. WARN means one or more material risks or evidence-quality issues require review. PASS means no configured WARN/BLOCK condition was observed in the available evidence; it never means guaranteed safe.
InterpretationWhat does data quality mean in a token risk scan?
Data quality describes how complete and reliable the available evidence is; it is not the same as the token's risk level. A token can have low measured risk but incomplete evidence, which should reduce confidence rather than be translated into a clean bill of health.