{
  "object": "jepeta_high_intent_answer",
  "schemaVersion": "1.0.0",
  "language": "en",
  "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",
  "sections": [
    {
      "heading": "What an agent needs",
      "paragraphs": [
        "The integration needs a stable chain identifier, exact-contract validation, bounded schemas, explicit error behavior, and fields that distinguish risk from evidence quality. The agent should not infer a PASS from a network failure or missing upstream data.",
        "Jepeta's public preview returns PASS/WARN/BLOCK plus explicit honeypot and mintability booleans, raw tax/liquidity/concentration fields, source status, warnings, and observation time."
      ]
    },
    {
      "heading": "Execution pattern",
      "paragraphs": [
        "Validate the address locally, call the preview endpoint, reject non-200 or schema-invalid responses, stop on BLOCK, apply additional review policy on WARN, and enforce independent execution limits even on PASS.",
        "For traceability, an agent can use the public evidence catalog when a permanent published snapshot exists. The live preview remains the correct input for a current trade."
      ]
    },
    {
      "heading": "Discovery surface",
      "paragraphs": [
        "Jepeta publishes OpenAPI, agent.json, llms.txt, llms-full.txt, methodology.json, changelog.json, a recent risk feed, and stable evidence pages. These give both agent runtimes and search/AI crawlers multiple consistent ways to resolve the same product identity.",
        "The deeper evidence report remains a separate paid contract through Virtuals ACP."
      ]
    }
  ],
  "checklist": [
    "Validate chain 8453 + address",
    "Call GET preview",
    "Fail closed on errors",
    "Stop on BLOCK",
    "Review WARN",
    "Apply own policy on PASS",
    "Use evidence URLs for traceability"
  ],
  "sources": [
    {
      "label": "Jepeta OpenAPI",
      "url": "https://jepeta.dev/openapi.json"
    },
    {
      "label": "Jepeta agent manifest",
      "url": "https://jepeta.dev/agent.json"
    },
    {
      "label": "Jepeta public evidence catalog",
      "url": "https://jepeta.dev/risk/base/"
    }
  ],
  "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": "Can I check Base token risk without connecting a wallet?",
      "url": "https://jepeta.dev/guides/base-token-security-api-without-wallet/"
    },
    {
      "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."
  ]
}