GET
Published receipts index
Receipts are written investigations of specific incidents, rendered for people at /receipts/{id}. This route is the machine-readable index of the same files, so a client can find the receipt covering an address and hand back a URL a human can open. It is an index, not a generator. A receipt exists because somebody reconstructed an incident, so most addresses have none and that is the normal answer rather than a failure.

Finding one

by address
by free text
address matches the receipt’s subject or deployer. q matches title, description and tags. limit defaults to 20 and is capped at 50. With neither filter you get the whole published index.
published_total and drafts_withheld are counts at the time of the call, not fixed numbers. Read them from the payload rather than from this page.

Nothing found is a stated answer

The reason names the size of the index, so a caller can tell “we have very few receipts” from “we have many and none of them is about this address.”

Unreviewed drafts are excluded, not marked

Some receipts still carry [VERIFY: markers against figures nobody has checked. The web page renders those behind a visible banner, which works because a person reads the banner. An API result does not carry its banner into whatever consumes it. A model summarising three receipts will not reproduce a caveat attached to one of them. So a draft is simply absent from the response, and drafts_withheld reports how many were dropped — the index is filtered, not short, and the caller can tell which.
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.

Query Parameters

address
string

Return receipts whose subject or deployer is this address.

q
string

Free-text match on title, description and tags.

limit
integer
default:20
Required range: x <= 50

Response

ok with the matching receipts, or insufficient_evidence when none covers the query (most addresses have no receipt; one is written for a specific investigation).

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

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

Unix seconds.

data
object
reason
string

Only on an absence: why, in plain words.