FINNPUTER/scan
live on mainnet
token safety · x402

See the wallets
they try to hide.

The FINNPUTER safety scan, now a pay-per-call API. Your agent — or you — pays a few cents over HTTP and sees the on-chain red flags before the buy. Signals, not guarantees: it lowers risk, it can't catch everything.

Run a scan How agents use it
finnputer · safety scan
$ scan mint 7xKp…Bnk2
cluster 1 same funding source
├ 7xPm…2kTz 12.4%
└ Ax9R…eF3m 5.8% → holding
cluster 2 bought together
└ BM4n…C6nB 4.2% → forwarded → 2bxL…KKYY
fresh 7 wallets created <24h
snipers 3 in first blocks
authority mint revoked · freeze revoked
LP not locked
holders top 10 = 61% (LP excluded)
TRADE WITH CARE   2 clusters · 1 forward · LP unlocked
settled 0.02 USDC · you decide
! Signals, not guarantees. FINNPUTER surfaces on-chain red flags so you — or your agent — can make a better call than buying blind. It lowers risk; it cannot catch everything, and it does not predict price. Not financial advice.
01

The check runs before your money moves

Same engine that runs inside the FINNPUTER Trade bot — now exposed as a paid endpoint anything can call. A request comes in, the server answers HTTP 402 — Payment Required, the caller's wallet pays the exact amount, the request retries, and the scan comes back. No account, no API key, no subscription. Payment is the access.

02

What the scan shows you

The two that matter most — because they catch what a snapshot can't:

core

Wallet cluster mapping

Traces shared funding sources and coordinated buys that move as one — so ten wallets behind one actor read as one actor, not ten "organic" holders.

cluster → 6 wallets · 1 funder · bought together
rare

Forward detection

Follows tokens forwarded to hidden collection wallets — the exit they prep early. A cluster can dissolve so the snapshot looks clean; the trail still shows where supply went.

snapshot clean · trail → forwarded to collection wallet
freshFresh-wallet scoring — flags wallets created under 24h before launch. The farm, surfaced.
snipersSniper tracking — bots buying in the first blocks, before you ever click.
authorityMint & freeze authority — whether the dev can still mint more or freeze your tokens.
LPLP lock status — is the liquidity locked or can it be pulled.
holdersHolder concentration with LP pools excluded, so the top-holder numbers are honest.
verdictA plain summary — e.g. "2 clusters · 1 forward · trade with care." Signals to weigh, not a buy/sell call.
03

How an agent uses it

STEP 1

Ask

Agent calls the scan endpoint with a token mint.

STEP 2

402

Server replies "payment required" with the exact price.

STEP 3

Pay

The caller's x402 client signs and settles the USDC automatically.

STEP 4

Signals

Same request retries, returns the flags. The agent decides.

// any x402-capable agent — payment handled by the client
const client = createX402Client({ wallet, network: "solana" });

const res = await client.fetch("https://api.finnputerdex.com/scan", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ mint })
});

// → 402, pays ~$0.02 USDC, retries, returns the signals:
// { clusters: 2, forwarded: 1, freshWallets: 7, snipers: 3,
//   mintRevoked: true, freezeRevoked: true, lpLocked: false,
//   topHolders: "61%", note: "trade with care", settled: true }

Not building an agent? The same scan is built into the FINNPUTER Trade bot — run it on any mint straight from Telegram, before you buy.

04

Pricing & the burn

$0.02
per scan · pay-per-call
  • No account, no API key
  • No subscription, no minimum
  • USDC on Solana, settled on-chain
  • Payment is the access — that's it

Scans feed the burn

Like the Trade bot's fees, scan revenue is designed to buy back $FINNPUTER on the open market and burn it — on-chain and provable. Every check that helps someone avoid a trap tightens the supply behind the scanner.

scan fee → treasury
treasury → buy $FINNPUTER
$FINNPUTER → burn 🔥

watch the burns live ↗

Scan first. Then ape.

One request. A few cents. The flags in front of you before you commit.

Run a scan