{
  "object": "jepeta_high_intent_answer",
  "schemaVersion": "1.0.0",
  "language": "en",
  "category": "agent_api",
  "question": "What makes a token risk API machine-readable?",
  "intent": "Choose an API that autonomous software can consume reliably",
  "directAnswer": "Machine-readable means more than returning JSON. A useful risk API has a versioned schema, stable field semantics, explicit null/error behavior, deterministic identifiers, documented limitations, and discoverable contracts such as OpenAPI or agent manifests.",
  "canonicalUrl": "https://jepeta.dev/guides/machine-readable-token-risk-api/",
  "jsonUrl": "https://jepeta.dev/guides/machine-readable-token-risk-api/index.json",
  "sections": [
    {
      "heading": "Schema over prose",
      "paragraphs": [
        "Agents need to know whether a field is boolean, nullable, bounded, or required. They also need to know what happens when a source is unavailable. Free-form text alone makes policy enforcement brittle.",
        "Jepeta publishes OpenAPI 4.3.0 plus agent manifests, llms files, methodology, changelog, and explicit schema versions for its preview, risk feed, and public evidence."
      ]
    },
    {
      "heading": "Unknown values must stay unknown",
      "paragraphs": [
        "A machine contract should distinguish false from unavailable and zero from missing. Otherwise a downstream system can convert data gaps into false reassurance.",
        "Jepeta fails closed on required honeypot/mintability unknowns and keeps optional unavailable metrics null with source-status context."
      ]
    },
    {
      "heading": "Stable evidence helps verification",
      "paragraphs": [
        "Permanent evidence pages add a canonical HTML and JSON representation for selected published snapshots. That gives search engines and agents a durable reference separate from the live scan endpoint.",
        "The durable snapshot still includes a last-checked timestamp and a link to run a fresh scan."
      ]
    }
  ],
  "checklist": [
    "Versioned schema",
    "Typed required fields",
    "Explicit null semantics",
    "Bounded errors",
    "Canonical identity",
    "Methodology + changelog",
    "Timestamped evidence"
  ],
  "sources": [
    {
      "label": "Jepeta OpenAPI",
      "url": "https://jepeta.dev/openapi.json"
    },
    {
      "label": "Jepeta agent manifest",
      "url": "https://jepeta.dev/agent.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": "Can I check Base token risk without connecting a wallet?",
      "url": "https://jepeta.dev/guides/base-token-security-api-without-wallet/"
    },
    {
      "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."
  ]
}