Why read-only matters
A scanner does not need authority over funds to inspect public token and market data. Requiring wallet connection for a simple risk lookup creates permissions that are unrelated to the question being asked.
Jepeta's public scanner and API are read-only. They do not execute trades, request token approvals, sign transactions, or custody buyer funds.
What the address reveals
The contract address lets the service query token-security and market sources for the exact Base asset. The response can expose contract controls, taxes, holder observations, liquidity context, source status, and timestamps.
For automation, send the contract address to the canonical V5 POST endpoint without browser state or wallet interaction. The documented V4 GET route remains a compatibility option.
What read-only does not solve
Read-only architecture improves scanner safety, but it does not make the token safe. You still need to interpret the underlying contract and market evidence.
Keep execution in a separate system with its own wallet, transaction simulation, slippage, and signing controls.
When a lookup unexpectedly asks you to connect
For the basic Jepeta lookup, the input is the exact token contract on Base. If a page asks for an allowance, seed phrase or transaction signature merely to display that lookup, the request exceeds this documented read-only task. Verify the official domain and API documentation before continuing. A wallet-free lookup can still reveal the queried address to the service and its network providers; read-only does not mean anonymous or that the token itself is safe.
AI-assisted review of linked documentation; no independent product benchmark. Screening observations and policy labels do not guarantee token safety.
Practical checklist
- No wallet connection needed
- No approvals/signatures
- Exact contract address only
- Keep execution separate
- Still review token evidence
