GET
What the wallet that deployed an EVM token did before

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