Contract snapshot / Base Mainnet

On-chain facts first.

Enter a token contract address on Base. Get a short verdict and checkable owner and proxy signals.

Block and data sourceUp to 3 reasonsJSON and SVG card
One report0.02 USDC

Check a contract

A snapshot is prepared before payment. Reading the report requires an x402 payment on Base.

Base contract address

API access is currently closed. This page does not collect payments.

What you get

Short answers, with evidence.

Each report is tied to one block. You can inspect the source and observed value behind every signal.

01 / SNAPSHOT

Verdict and one-sentence summary

A limited reading of observable signals. It is not a guarantee of safety.

02 / EVIDENCE

Up to three reasons

Contract fields, block number and hash, RPC source, and what remains unknown.

03 / FORMAT

JSON and a card

Compact JSON for agents and an SVG card you can share.

For agents

A simple API flow.

Send a Base contract address. The API stores a snapshot and returns an ID without disclosing the findings. An x402-capable client then requests the paid report.

This is a limited technical check, not a code audit, liquidity analysis, or investment advice. An absent signal does not mean a token is safe.

POST /v1/prepare
{"address":"0x..."}

GET /v1/reports/{report_id}
402 → x402 / Base / USDC
200 → JSON + SVG card