GoPlus role
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.
What Jepeta adds
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.
Why the distinction matters
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.
Practical checklist
- GoPlus = security source
- Jepeta = Base policy layer
- Know upstream dependencies
- Read source status
- Use the layer appropriate to your workflow