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, the same input can be sent to the GET endpoint without browser state or wallet interaction.
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.
Practical checklist
- No wallet connection needed
- No approvals/signatures
- Exact contract address only
- Keep execution separate
- Still review token evidence