{ "object": "jepeta_high_intent_guides", "schemaVersion": "1.0.0", "generatedAt": "2026-09-24T16:50:04.391Z", "count": 20, "canonicalUrl": "https://jepeta.dev/guides/", "pages": [ { "slug": "base-token-risk-api-for-ai-agents", "category": "agent_api", "question": "What Base token risk API can an AI agent use before execution?", "intent": "Integrate a deterministic token-risk gate into an autonomous agent", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/base-token-risk-api-for-ai-agents/", "jsonUrl": "https://jepeta.dev/guides/base-token-risk-api-for-ai-agents/index.json" }, { "slug": "base-token-risk-checklist-before-buy", "category": "workflow", "question": "What should I check before buying a Base token?", "intent": "Use a practical pre-trade Base token checklist", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/base-token-risk-checklist-before-buy/", "jsonUrl": "https://jepeta.dev/guides/base-token-risk-checklist-before-buy/index.json" }, { "slug": "base-token-security-api-without-wallet", "category": "agent_api", "question": "Can I check Base token risk without connecting a wallet?", "intent": "Screen a token read-only without wallet permissions", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/base-token-security-api-without-wallet/", "jsonUrl": "https://jepeta.dev/guides/base-token-security-api-without-wallet/index.json" }, { "slug": "honeypot-check-vs-token-risk-check", "category": "comparison", "question": "What is the difference between a honeypot check and a token risk check?", "intent": "Avoid treating one sellability test as complete due diligence", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/honeypot-check-vs-token-risk-check/", "jsonUrl": "https://jepeta.dev/guides/honeypot-check-vs-token-risk-check/index.json" }, { "slug": "how-to-check-base-token-honeypot", "category": "risk_signal", "question": "How do I check if a Base token is a honeypot?", "intent": "Detect sell-blocking or honeypot behavior on Base", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/how-to-check-base-token-honeypot/", "jsonUrl": "https://jepeta.dev/guides/how-to-check-base-token-honeypot/index.json" }, { "slug": "how-to-check-holder-concentration-base-token", "category": "risk_signal", "question": "How do I check holder concentration risk for a Base token?", "intent": "Assess concentration in the observed top holders", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/how-to-check-holder-concentration-base-token/", "jsonUrl": "https://jepeta.dev/guides/how-to-check-holder-concentration-base-token/index.json" }, { "slug": "how-to-check-liquidity-lock-base-token", "category": "risk_signal", "question": "How do I check whether Base token liquidity is locked?", "intent": "Understand LP-lock evidence and its limits", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/how-to-check-liquidity-lock-base-token/", "jsonUrl": "https://jepeta.dev/guides/how-to-check-liquidity-lock-base-token/index.json" }, { "slug": "how-to-check-liquidity-risk-base-token", "category": "risk_signal", "question": "How do I check liquidity risk for a Base token?", "intent": "Estimate whether the exact Base market has enough observable liquidity", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/how-to-check-liquidity-risk-base-token/", "jsonUrl": "https://jepeta.dev/guides/how-to-check-liquidity-risk-base-token/index.json" }, { "slug": "how-to-check-token-buy-sell-tax-base", "category": "risk_signal", "question": "How do I check buy and sell tax on a Base token?", "intent": "Find transfer taxes that can affect entry or exit", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/how-to-check-token-buy-sell-tax-base/", "jsonUrl": "https://jepeta.dev/guides/how-to-check-token-buy-sell-tax-base/index.json" }, { "slug": "how-to-monitor-new-base-token-risk-signals", "category": "evidence", "question": "How can I monitor new Base token risk signals?", "intent": "Discover recent published risk signals and follow them into evidence", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/how-to-monitor-new-base-token-risk-signals/", "jsonUrl": "https://jepeta.dev/guides/how-to-monitor-new-base-token-risk-signals/index.json" }, { "slug": "how-to-use-base-token-risk-evidence", "category": "evidence", "question": "How should I use a permanent Base token risk evidence page?", "intent": "Verify and cite a timestamped Jepeta risk snapshot", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/how-to-use-base-token-risk-evidence/", "jsonUrl": "https://jepeta.dev/guides/how-to-use-base-token-risk-evidence/index.json" }, { "slug": "is-this-base-token-safe", "category": "discovery", "question": "Is this Base token safe?", "intent": "Evaluate one exact Base token before a trade", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/is-this-base-token-safe/", "jsonUrl": "https://jepeta.dev/guides/is-this-base-token-safe/index.json" }, { "slug": "jepeta-and-goplus-difference", "category": "comparison", "question": "What is the difference between Jepeta and GoPlus Token Security?", "intent": "Understand source data versus a policy layer built on top of it", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/jepeta-and-goplus-difference/", "jsonUrl": "https://jepeta.dev/guides/jepeta-and-goplus-difference/index.json" }, { "slug": "jepeta-vs-honeypot-is", "category": "comparison", "question": "How is Jepeta different from Honeypot.is for Base tokens?", "intent": "Understand overlapping and different Base-token screening roles", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/jepeta-vs-honeypot-is/", "jsonUrl": "https://jepeta.dev/guides/jepeta-vs-honeypot-is/index.json" }, { "slug": "jepeta-vs-tokensniffer", "category": "comparison", "question": "How is Jepeta different from TokenSniffer on Base?", "intent": "Compare Base support, risk output, and agent integration", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/jepeta-vs-tokensniffer/", "jsonUrl": "https://jepeta.dev/guides/jepeta-vs-tokensniffer/index.json" }, { "slug": "machine-readable-token-risk-api", "category": "agent_api", "question": "What makes a token risk API machine-readable?", "intent": "Choose an API that autonomous software can consume reliably", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/machine-readable-token-risk-api/", "jsonUrl": "https://jepeta.dev/guides/machine-readable-token-risk-api/index.json" }, { "slug": "pre-trade-risk-gate-for-base-trading-bot", "category": "agent_api", "question": "How do I add a pre-trade risk gate to a Base trading bot?", "intent": "Design a safe deterministic gate before a Base swap", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/pre-trade-risk-gate-for-base-trading-bot/", "jsonUrl": "https://jepeta.dev/guides/pre-trade-risk-gate-for-base-trading-bot/index.json" }, { "slug": "what-does-mintable-token-mean", "category": "risk_signal", "question": "What does it mean if a Base token is mintable?", "intent": "Understand mintability as a token risk signal", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/what-does-mintable-token-mean/", "jsonUrl": "https://jepeta.dev/guides/what-does-mintable-token-mean/index.json" }, { "slug": "what-does-pass-warn-block-mean-token-risk", "category": "interpretation", "question": "What do PASS, WARN, and BLOCK mean in token risk screening?", "intent": "Interpret Jepeta policy decisions correctly", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/what-does-pass-warn-block-mean-token-risk/", "jsonUrl": "https://jepeta.dev/guides/what-does-pass-warn-block-mean-token-risk/index.json" }, { "slug": "what-does-token-data-quality-mean", "category": "interpretation", "question": "What does data quality mean in a token risk scan?", "intent": "Separate evidence completeness from risk severity", "directAnswer": "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.", "canonicalUrl": "https://jepeta.dev/guides/what-does-token-data-quality-mean/", "jsonUrl": "https://jepeta.dev/guides/what-does-token-data-quality-mean/index.json" } ] }