Risk intelligence
without the guesswork.
Use Jepeta as a fail-closed pre-trade risk guard inside a Base agent. The user-facing scanner is the preview and acquisition surface; the public preview requires no API key, wallet connection or signature.
One endpoint. One exact contract.
Send the exact Base ERC-20 contract address. Jepeta returns a strict preview with a machine decision, raw risk signals, source status and uncertainty.
https://aitgmgfumsdqecmanrab.supabase.co/functions/v1/jepeta-risk-scan
const tokenAddress = '0x532f27101965dd16442e59d40670faf5ebb142e4';
const response = await fetch('https://aitgmgfumsdqecmanrab.supabase.co/functions/v1/jepeta-risk-scan', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ tokenAddress }),
signal: AbortSignal.timeout(20000)
});
const report = await response.json();
if (!response.ok || report.status !== 'VERDICT' || report.token_address !== tokenAddress) {
throw new Error(report.failure?.code || 'NO_VERDICT');
}
if (report.verdict === 'BLOCK') throw new Error('Stop execution');
if (report.verdict === 'WARN') throw new Error('Review required');
if (report.verdict !== 'PASS') throw new Error('Unknown verdict');
// Inspect evidence_quality and logical_signals; apply your own transaction policy.
curl -sS --fail-with-body --max-time 20 -X POST 'https://aitgmgfumsdqecmanrab.supabase.co/functions/v1/jepeta-risk-scan' -H 'Content-Type: application/json' -d '{"tokenAddress":"0x532f27101965dd16442e59d40670faf5ebb142e4"}'
# No API key. Inspect the current decision; demo outcomes can change.
The tested JavaScript guard remains available for V4 GET compatibility integrations. The canonical V5 example above requires status: VERDICT; PASS never authorizes a trade.
Three outputs. No fake certainty.
The decision is a policy hint, not a prediction and not permission to trade.
No configured warning or block observed.
Useful as a low-friction policy signal, but never a safety guarantee. Source quality and warnings still matter.
Material review condition observed.
Inspect the exact signal before proceeding. Typical examples include mintability or elevated concentration.
Hard stop condition observed.
Designed for conditions such as an explicit honeypot signal. Your execution policy should stop or escalate.
What comes back.
V5 returns status, verdict, risk, evidence_quality, logical_signals, source_status and conflicts. Read the full canonical V5 schema; paid-only evidence remains private. The table and illustrative response below document the still-supported V4 GET compatibility contract.
| Field | Type | Meaning |
|---|---|---|
decision | PASS · WARN · BLOCK | Machine policy hint. |
risk_score | 0–100 | Observed heuristic score, not loss probability. |
is_honeypot | boolean | Explicit GoPlus honeypot signal. |
is_mintable | boolean | Explicit GoPlus mintability signal. |
buy_tax_percent | number · null | Observed buy tax when available. |
sell_tax_percent | number · null | Observed sell tax when available. |
top10_holder_concentration_percent | number · null | Observed sum from up to ten holder records. |
lp_locked_percent_observed | number · null | Observed lock coverage in the sampled LP-holder records. |
liquidity_usd | number · null | Largest exact matching Base pair returned by DEX Screener. |
data_quality | HIGH · MEDIUM · LOW | How complete the usable evidence is. |
source_status | object | GoPlus + DEX Screener availability state. |
warnings | string[] | User-friendly observed concerns and caveats. |
Example V4 GET compatibility response +
{
"schema_version": "4.0.0",
"chain_id": 8453,
"token_address": "0x...",
"decision": "WARN",
"risk_score": 35,
"risk_level": "MEDIUM",
"is_honeypot": false,
"is_mintable": true,
"buy_tax_percent": null,
"sell_tax_percent": null,
"data_quality": "MEDIUM",
"source_status": {
"goplus": "OK",
"dexscreener": "OK"
},
"warnings": [
"GoPlus reports that token supply can be minted."
],
"observed_at": "2026-09-22T12:00:00Z"
}
Canonical V5 public preview contract.
JSON request body
tokenAddressrequiredExact Base ERC-20 contract address. Must match ^0x[a-fA-F0-9]{40}$.
Errors & retry behavior
400Invalid requestBad or malformed token address.405Method not allowedCanonical V5 uses POST. V4 GET remains available on the explicit V4 endpoint and default GET.422Insufficient coverageRequired security evidence is unavailable; no verdict is issued.429Rate limitedHonor the Retry-After header before retrying.503Required source unavailableNo assessment is issued when the required security provider is unavailable.Free decision. Paid evidence when it matters.
The public preview answers “stop, review, or continue with your own policy.” Choose the purchase rail that matches the buyer: Telegram for people, Virtuals ACP for autonomous agents.
Telegram · 25 Stars
Buy a user-friendly report for one Base token in @Jepeta_bot for 25 Telegram Stars. It covers permissions, taxes, liquidity, holders, activity, source status and risk rationale. The bot confirms the price, terms and invoice before payment.
Select a token for Telegram checkout →Virtuals ACP · 0.03 USDC / scan
The paid Token Risk Scan adds dangerous permissions, liquidity-risk assessment, concentration analysis, 24h activity and a structured evidence summary.
Buy via Virtuals ACP · 0.03 USDCAvailable through Virtuals ACP at 0.03 USDC per Token Risk Scan. Checkout and payment are handled on Virtuals ACP.
For agent integrations, Virtuals ACP v2 is the marketplace protocol. The structured Jepeta deliverable uses the v3 report contract. The marketplace listing is the source of truth for current price, SLA and availability.
Raw contracts, when you actually want them.
These files are intentionally machine-first. Users can stay on this page; agents and tooling can consume the raw contracts directly.
For the user-friendly explanation of checks, sources, decision semantics and fail-closed behavior, see Methodology.
Canonical machine surface: Jepeta Risk Guard · Base / 8453 · Virtuals ACP · 0.03 USDC per Token Risk Scan · Telegram report 25 Stars · Last updated 2026-10-04.
V5 default POST, explicit V5 POST, response and error contract.
V4 COMPATIBILITYopenapi.jsonSupported V4 GET request, response and error contract.
AGENTagent.jsonAgent identity, public preview and commerce metadata.
LLMllms.txtCompact machine-readable integration guide.
LLM FULLllms-full.txtExtended agent-facing operational context.
SAMPLEsample-full-report.jsonDeterministic synthetic ACP v3 example; not a live scan or a Telegram delivery example.
METHODmethodology.jsonChecks, sources, decision semantics, examples and limitations.
CHANGEchangelog.jsonDated machine-contract changes and current service facts.
EVIDENCEPublic risk evidencePermanent evidence-rich Base token snapshots with HTML + JSON URLs.
GUIDESHigh-intent risk guides20 direct-answer Base token risk resources with evidence and machine JSON.
GUIDEBase risk guideUser-facing explanation of honeypot and related risk signals.
Start with one contract.
No account. No wallet. No signature.