{
  "object": "jepeta_high_intent_answer",
  "schemaVersion": "1.0.0",
  "language": "en",
  "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",
  "sections": [
    {
      "heading": "Exact-chain matching matters",
      "paragraphs": [
        "A token address or symbol on another chain must not improve the Base risk picture. The relevant context is the exact token contract on Base and its matching Base market.",
        "Jepeta deliberately rejects cross-token and cross-chain substitutions in its risk model. It uses DEX Screener market context only when it matches the requested Base contract."
      ]
    },
    {
      "heading": "How Jepeta exposes liquidity",
      "paragraphs": [
        "The public preview and evidence pages expose liquidity_usd when the matching Base market can be confirmed. The source-status field separately reports whether DEX Screener data was OK, partial, rate-limited, or unavailable.",
        "This separation matters because evidence completeness is not the same thing as risk. Missing data can lower confidence without proving that a token has no liquidity."
      ]
    },
    {
      "heading": "Use liquidity with other signals",
      "paragraphs": [
        "Liquidity does not tell you whether a contract can mint, block transfers, or impose taxes. Conversely, a clean contract signal does not solve shallow market depth.",
        "Read liquidity together with holder concentration, taxes, mintability, and the timestamp. Market conditions can change quickly."
      ]
    }
  ],
  "checklist": [
    "Match exact token and Base chain",
    "Use USD liquidity as market context",
    "Read source status",
    "Do not map missing data to zero",
    "Combine with holder and permission risk"
  ],
  "sources": [
    {
      "label": "Jepeta methodology",
      "url": "https://jepeta.dev/methodology.json"
    },
    {
      "label": "Jepeta public evidence catalog",
      "url": "https://jepeta.dev/risk/base/"
    }
  ],
  "evidenceExample": {
    "tokenAddress": "0x80210081479359b512f464058b2699cebe998579",
    "canonicalUrl": "https://jepeta.dev/risk/base/0x80210081479359b512f464058b2699cebe998579/",
    "lastCheckedAt": "2026-09-24T15:46:00.12+00:00",
    "decision": "WARN",
    "riskScore": 25
  },
  "related": [
    {
      "question": "How do I check if a Base token is a honeypot?",
      "url": "https://jepeta.dev/guides/how-to-check-base-token-honeypot/"
    },
    {
      "question": "How do I check holder concentration risk for a Base token?",
      "url": "https://jepeta.dev/guides/how-to-check-holder-concentration-base-token/"
    },
    {
      "question": "How do I check whether Base token liquidity is locked?",
      "url": "https://jepeta.dev/guides/how-to-check-liquidity-lock-base-token/"
    }
  ],
  "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."
  ]
}