GET
What the wallet that deployed an EVM token did before
This endpoint is not the Solana deployer record for EVM. That one returns flagged, backed by a rule scored on a holdout and again prospectively. Nothing here has been scored, so there is no flagged field and every payload carries calibrated: false. The two shapes are deliberately not interchangeable.
The Solana record answers from a census that watched launches as they happened. There is no such census on EVM, so this record is walked live from the chain for each request: the address’s contract creations, one level of factory below them, the chain’s own attribution for each, then the venue for each token’s current state. Method and limits in full: EVM deployer records.

The answers

no_record is not clean. It means this walk found nothing, which is a statement about the walk. A wallet that launches through a public launchpad’s factory — one it did not deploy itself — reads as no_record here.

Chains

Only ethereum is served. Etherscan’s v2 endpoint refuses six of the ten chains the engine covers on a free API key, including Base, where most new launches now happen. A request for one of those answers not_supported naming the specific refusal, never an empty record:

A wallet with a record

curl
That record is real, measured on 2026-09-22, and it is worth reading closely because two of its numbers are the whole design. transfers_observed: 0. That token was deployed and never moved a single unit. It never launched. The Solana pipeline would have called it delisted and counted it as a death; counting it here would manufacture a death record out of a contract nobody ever touched. So never_listed is its own outcome and is excluded from died and from the denominator. via: "factory:0x25a...". The launches this address is actually known for were deployed by a factory it created, not by the address directly. Seven of its eight direct creations are not tokens at all. A walk that only read its own transaction list would find one token, see it dead, and report every launch died about a wallet with a live launch.

Reading coverage

Four kinds of nothing, kept apart, because collapsing them turns a gap in our reading into a finding about a wallet: truncated: true means the address has more history than one query returns, so the counts are a floor rather than a total — the record’s own finding sentence says so as well.

What this does not say

Every launch is measured at whatever age it happens to be now, recorded per launch as observed_age_days; ages over a year are normal, and no horizon is claimed. Coverage reaches one level of factory and no further. Survival means listed with tradeable liquidity at the moment of the check — not profit, not legitimacy, not safety. Most importantly: a record saying every listed launch by an address is illiquid is a statement about those contracts. It is not a prediction about the next one, and no measurement here supports turning it into one.
Scienter analyses public blockchain records. A finding states what those records show and how confident we are; it is evidence, not proof of anyone’s identity, intent or wrongdoing, and an attribution we cite is the cited source’s. An empty result means not analysed, never safe. Nothing here is legal, tax or investment advice, or a recommendation to transact with any address or asset — see Disclaimers for the full text.

Authorizations

Authorization
string
header
required

An sc_ key from https://scienter.xyz/settings/api, sent as Authorization: Bearer sc_.... The same key is accepted in the x-scienter-membership header. Prefer the header over any query form: a credential in a URL reaches access logs, proxies and browser history.

Path Parameters

chain
enum<string>
required

The chain to walk. Only ethereum is served; every other value answers not_supported with the reason.

Available options:
ethereum
address
string
required

A 20-byte hex EVM address, 0x-prefixed. Case is not significant and is normalised.

Pattern: ^0x[0-9a-fA-F]{40}$

Response

ok with the deployer record; insufficient_evidence when nothing was found; not_supported for a chain we cannot read; not_deployed when the chain walk could not run.

The four-state envelope. state: ok carries data as described; the three absences carry data: null and reason.

state
enum<string>
Available options:
ok,
insufficient_evidence,
not_deployed,
not_supported
subject
string
data
object
reason
string
sources
object[]
as_of
integer