GET
The Wall of Rugs, as data
This leaderboard endpoint is paid. /api/v1/leaderboard needs an sc_ key from an active Analyst, Desk or Enterprise plan, and returns the flagged token contracts behind the Wall of Rugs.It is not the provider leaderboard, which scores data vendors and is free. Two boards, similar names; asking about the wrong one gets you a confident answer about something you did not buy.
Every row is a model output about a named token contract. That is the reason this route is shaped the way it is: it feeds MCP clients, a language model restates rows without whatever surrounded them, and a wrong row in a transcript outlives its correction.

What comes back

curl
limit defaults to 20 and is capped at 100.

Three outcomes, and two of them look the same if you collapse them

The middle row is the one worth understanding before you build on it. An empty wall is an answer:
No wallets crossed the flag threshold in the last 24 hours. This is a real result, not a gap in coverage.
ever_written separates the two empty cases that remain: false means the flag table has never been written at all, which is a gap rather than a quiet day, and null means the producer could not confirm either way on this read.

The blue-chip allowlist runs on this response

Established tokens are filtered out here even though the producer is supposed to have excluded them already, and established_suppressed reports how many this response dropped. The wall reads whatever SCIENTER_INTELLIGENCE_URL points at, and one environment variable can repoint it at an older engine. USDC appearing in an MCP tool result for an hour is not worth the saved filter.

What this does not say

A flag is a model output about a token contract. It is not a legal finding, not an allegation against any person, and not advice. See the rug model’s methodology for what the score is and is not — in particular that it is a rank, not a probability.
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

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

Response

ok with the entries (possibly empty, with empty_reason), or not_deployed.

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.