{
  "object": "jepeta_high_intent_answer",
  "schemaVersion": "1.0.0",
  "language": "en",
  "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",
  "sections": [
    {
      "heading": "Why read-only matters",
      "paragraphs": [
        "A scanner does not need authority over funds to inspect public token and market data. Requiring wallet connection for a simple risk lookup creates permissions that are unrelated to the question being asked.",
        "Jepeta's public scanner and API are read-only. They do not execute trades, request token approvals, sign transactions, or custody buyer funds."
      ]
    },
    {
      "heading": "What the address reveals",
      "paragraphs": [
        "The contract address lets the service query token-security and market sources for the exact Base asset. The response can expose contract controls, taxes, holder observations, liquidity context, source status, and timestamps.",
        "For automation, the same input can be sent to the GET endpoint without browser state or wallet interaction."
      ]
    },
    {
      "heading": "What read-only does not solve",
      "paragraphs": [
        "Read-only architecture improves scanner safety, but it does not make the token safe. You still need to interpret the underlying contract and market evidence.",
        "Keep execution in a separate system with its own wallet, transaction simulation, slippage, and signing controls."
      ]
    }
  ],
  "checklist": [
    "No wallet connection needed",
    "No approvals/signatures",
    "Exact contract address only",
    "Keep execution separate",
    "Still review token evidence"
  ],
  "sources": [
    {
      "label": "Jepeta OpenAPI",
      "url": "https://jepeta.dev/openapi.json"
    },
    {
      "label": "Jepeta methodology",
      "url": "https://jepeta.dev/methodology.json"
    }
  ],
  "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 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 makes a token risk API machine-readable?",
      "url": "https://jepeta.dev/guides/machine-readable-token-risk-api/"
    },
    {
      "question": "How do I add a pre-trade risk gate to a Base trading bot?",
      "url": "https://jepeta.dev/guides/pre-trade-risk-gate-for-base-trading-bot/"
    }
  ],
  "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."
  ]
}