{
  "object": "jepeta_high_intent_answer",
  "schemaVersion": "1.0.0",
  "language": "en",
  "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",
  "sections": [
    {
      "heading": "Honeypot is necessary but narrow",
      "paragraphs": [
        "A token that blocks selling is an obvious stop condition, so honeypot testing belongs near the top of a pre-trade workflow. Simulation tools can also reveal taxes and gas behavior.",
        "But a sellable token can still be mintable, highly concentrated, thinly traded, or subject to mutable controls."
      ]
    },
    {
      "heading": "Broader screening adds context",
      "paragraphs": [
        "Jepeta combines explicit honeypot and mintability signals with taxes, observed holder concentration, observed LP-lock coverage, Base liquidity, source status, and data quality.",
        "The policy result is designed to help a workflow decide whether to block, review, or continue to independent execution rules."
      ]
    },
    {
      "heading": "Use the right label",
      "paragraphs": [
        "Do not call a negative honeypot result safe. Say the honeypot check was negative at that timestamp. Likewise, do not call a PASS verdict a guarantee.",
        "Precise language makes evidence more useful to humans and less likely to be exaggerated when quoted by an AI system or search result."
      ]
    }
  ],
  "checklist": [
    "Honeypot = sellability and transfer risk",
    "Risk check = multiple dimensions",
    "Never translate negative honeypot to safe",
    "Keep timestamps",
    "Use broader context"
  ],
  "sources": [
    {
      "label": "Jepeta methodology",
      "url": "https://jepeta.dev/methodology.json"
    },
    {
      "label": "Honeypot.is API documentation",
      "url": "https://docs.honeypot.is/ishoneypot"
    }
  ],
  "evidenceExample": {
    "tokenAddress": "0x940181a94a35a4569e4529a3cdfb74e38fd98631",
    "canonicalUrl": "https://jepeta.dev/risk/base/0x940181a94a35a4569e4529a3cdfb74e38fd98631/",
    "lastCheckedAt": "2026-09-24T16:48:11.089+00:00",
    "decision": "WARN",
    "riskScore": 35
  },
  "related": [
    {
      "question": "What is the difference between Jepeta and GoPlus Token Security?",
      "url": "https://jepeta.dev/guides/jepeta-and-goplus-difference/"
    },
    {
      "question": "How is Jepeta different from Honeypot.is for Base tokens?",
      "url": "https://jepeta.dev/guides/jepeta-vs-honeypot-is/"
    },
    {
      "question": "How is Jepeta different from TokenSniffer on Base?",
      "url": "https://jepeta.dev/guides/jepeta-vs-tokensniffer/"
    }
  ],
  "methodologyUrl": "https://jepeta.dev/methodology.json",
  "freshScanUrl": "https://jepeta.dev/#scanner",
  "limitations": [
    "Educational risk-screening content, not investment advice.",
    "A token-risk snapshot is timestamped and can become stale.",
    "PASS is not a safety guarantee."
  ]
}