{
  "object": "jepeta_high_intent_answer",
  "schemaVersion": "1.0.0",
  "language": "en",
  "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",
  "sections": [
    {
      "heading": "Risk and evidence are different axes",
      "paragraphs": [
        "Risk fields ask what the available data says about the token. Data-quality fields ask how much usable evidence was available to support that conclusion.",
        "Combining the two prevents a common failure mode: interpreting missing fields as zero risk."
      ]
    },
    {
      "heading": "Jepeta fail-closed boundary",
      "paragraphs": [
        "Jepeta requires GoPlus coverage and explicit honeypot/mintability values for a successful strict preview. Required unknowns do not become false.",
        "DEX Screener market context can be partial or unavailable; Jepeta surfaces that source status separately and keeps unavailable market values null."
      ]
    },
    {
      "heading": "Why permanent pages require a quality gate",
      "paragraphs": [
        "T037 only promotes already-published tokens with HIGH or MEDIUM public data quality, explicit security booleans, and at least two non-null public evidence dimensions.",
        "This means ordinary or low-quality scans do not become indexable SEO pages, reducing both misinformation risk and thin-content risk. It also keeps citations and search snippets tied to evidence that is complete enough to explain responsibly."
      ]
    }
  ],
  "checklist": [
    "Read data quality separately from risk level",
    "Inspect source status",
    "Keep null distinct from zero",
    "Require explicit critical booleans",
    "Prefer fresh evidence"
  ],
  "sources": [
    {
      "label": "Jepeta methodology",
      "url": "https://jepeta.dev/methodology.json"
    },
    {
      "label": "GoPlus Token Security API",
      "url": "https://docs.gopluslabs.io/reference/tokensecurityusingget_1"
    }
  ],
  "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 do PASS, WARN, and BLOCK mean in token risk screening?",
      "url": "https://jepeta.dev/guides/what-does-pass-warn-block-mean-token-risk/"
    },
    {
      "question": "What Base token risk API can an AI agent use before execution?",
      "url": "https://jepeta.dev/guides/base-token-risk-api-for-ai-agents/"
    },
    {
      "question": "What should I check before buying a Base token?",
      "url": "https://jepeta.dev/guides/base-token-risk-checklist-before-buy/"
    }
  ],
  "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."
  ]
}