Bulk wallet screen

POST /api/v1/bulk/wallet-screen

Triage a list. For each address this answers one question — does either dataset Scienter owns outright have a record of it — and nothing more.

curl

curl -X POST https://scienter.xyz/api/v1/bulk/wallet-screen \
  -H "Authorization: Bearer sc_..." \
  -H "Content-Type: application/json" \
  -d '{"addresses":["0x28C6c06298d514Db089934071355E5743bf21d60","8dEgpaZ6znNZWBWLuciBYF1kfRtUEQUmVTZQWebezu2n"]}'

{
  "state": "ok",
  "subject": "bulk/wallet-screen",
  "data": {
    "requested": 2,
    "screened": 2,
    "max_per_request": 500,
    "answers": "label and deployer record only; not a forensic reconstruction",
    "full_record_endpoint": "/api/v1/wallet/{address}/score",
    "results": [
      {
        "address": "0x28c6c06298d514db089934071355e5743bf21d60",
        "state": "ok",
        "label": { "label": "Binance 14", "entity": "Binance", "role": "hot_wallet", "confidence": "documented" }
      },
      {
        "address": "8dEgpaZ6znNZWBWLuciBYF1kfRtUEQUmVTZQWebezu2n",
        "state": "ok",
        "deployer": { "settled": 1136, "survived": 0, "delisted": 1136, "illiquid": 0, "flagged": true, "sentence": "…" }
      }
    ]
  },
  "sources": [
    { "name": "scienter:exchange-wallet-table" },
    { "name": "scienter:solana-launch-corpus", "as_of": 1790000000 }
  ]
}

Why this is a screen and not a score

It would be reasonable to expect /api/v1/bulk/wallet-score — a batched form of the single-address score. That route makes four upstream reads per address: the explorer summary, the engine’s scorecard, its entity resolution and its flagged feed. Five hundred addresses is two thousand upstream calls against a provider budget shared with the rest of the product, inside a sixty-second ceiling. It would not finish. So this route answers the narrower question and is named for it. Every field is read from data compiled into the build — no network call is made, per address or at all:

Field	Source
`label`	the published exchange-wallet table (EVM addresses)
`deployer`	the Solana launch corpus (base58 addresses)

That is what makes five hundred of them cheap, and it is also exactly why it is not a score. A screen says whether a dataset has heard of an address. A score is a reconstruction. Use the screen to decide which addresses are worth spending a single-address call on.

Per-address state

Each result carries its own state. They are not interchangeable.

State	Meaning
`ok`	at least one dataset holds a record, and it is attached
`insufficient_evidence`	neither dataset holds a record for this address
`not_supported`	not an EVM `0x` address or a base58 Solana address

insufficient_evidence does not mean the address is clean. The exchange-wallet table is partial by construction and the launch corpus covers a measured window; an address absent from both has not been examined, which is a different fact from having been examined and found unremarkable. The reason field says so on every such result rather than leaving the caller to infer it.

Limits and cost


Addresses per request	500
Charged as	one request against the daily allowance, not one per address
Analyst	1,000 requests a day
Desk, Enterprise	unmetered

The per-request charge is deliberate: the route spends no upstream quota, so charging per address would price a cost it does not incur. The expensive work stays on the single-address routes. A body over 500 addresses is a 400 naming the count it received. Malformed JSON, a missing addresses array and an empty array are each a 400 with the shape it expected.

Using the API

Streaming

Scienter API (paid)

Intelligence service

MCP tools

Bulk wallet screen

POST /api/v1/bulk/wallet-screen

Why this is a screen and not a score

Per-address state

Limits and cost

​POST /api/v1/bulk/wallet-screen

​Why this is a screen and not a score

​Per-address state

​Limits and cost

POST /api/v1/bulk/wallet-screen

Why this is a screen and not a score

Per-address state

Limits and cost