{
  "object": "jepeta_high_intent_answer",
  "schemaVersion": "1.0.0",
  "language": "en",
  "category": "comparison",
  "question": "What is the difference between Jepeta and GoPlus Token Security?",
  "intent": "Understand source data versus a policy layer built on top of it",
  "directAnswer": "GoPlus is a security-data provider; Jepeta consumes GoPlus token-security evidence as a required input and adds its own Base-specific policy layer, DEX Screener market context, data-quality semantics, public evidence publishing, and agent-commerce surface. Jepeta is not a replacement for GoPlus inside its own architecture.",
  "canonicalUrl": "https://jepeta.dev/guides/jepeta-and-goplus-difference/",
  "jsonUrl": "https://jepeta.dev/guides/jepeta-and-goplus-difference/index.json",
  "sections": [
    {
      "heading": "GoPlus role",
      "paragraphs": [
        "GoPlus documents a Token Security API that accepts a chain ID and token contract address and returns token security information. Its broader documentation exposes many security items and APIs for developers.",
        "Jepeta relies on that token-security source for required honeypot and mintability evidence and for several other public and paid fields."
      ]
    },
    {
      "heading": "What Jepeta adds",
      "paragraphs": [
        "Jepeta normalizes the exact Base contract, combines required security evidence with exact matching Base liquidity context from DEX Screener, applies configured PASS/WARN/BLOCK rules, and preserves explicit source-status and data-quality behavior.",
        "It also creates human and machine surfaces around the result: scanner UI, OpenAPI, agent manifests, recent signals, stable evidence pages, Telegram distribution, and a paid evidence report through Virtuals ACP."
      ]
    },
    {
      "heading": "Why the distinction matters",
      "paragraphs": [
        "If you need raw GoPlus security data, call GoPlus directly. If you need a deterministic Base pre-trade gate that combines that source with market context and Jepeta policy semantics, Jepeta is the higher-level layer.",
        "Because Jepeta depends on upstream providers, it surfaces provider degradation rather than pretending the source relationship does not exist."
      ]
    }
  ],
  "checklist": [
    "GoPlus = security source",
    "Jepeta = Base policy layer",
    "Know upstream dependencies",
    "Read source status",
    "Use the layer appropriate to your workflow"
  ],
  "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 is the difference between a honeypot check and a token risk check?",
      "url": "https://jepeta.dev/guides/honeypot-check-vs-token-risk-check/"
    },
    {
      "question": "How is Jepeta different from Honeypot.is for Base tokens?",
      "url": "https://jepeta.dev/guides/jepeta-vs-honeypot-is/"
    },
    {
      "question": "How is Jepeta different from TokenSniffer on Base?",
      "url": "https://jepeta.dev/guides/jepeta-vs-tokensniffer/"
    }
  ],
  "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."
  ]
}