This is the path for a paying customer of the hosted API. If you would rather run the whole thing on your own machine for nothing, that is Run it yourself, and it needs no key at all.

​
1. Get a key

  1. Buy a plan on scienter.xyz/pricing. Whop takes the payment.
  2. Paste the mem_ id from your receipt once at scienter.xyz/activate.
  3. Create a key at scienter.xyz/settings/api.
The key starts sc_, is shown once, is stored only as a hash, and expires after 90 days.

​
2. Make the call

Send the key as a header, never in the query string: a credential in a URL reaches access logs, proxies and browser history.

​
3. Read state before anything else

Every route answers with the same envelope, and state is the first thing to read — not the HTTP status. A refusal to answer is still HTTP 200 with a state that says why.
An empty result is not a clean result. If your code treats insufficient_evidence the same as ok with no findings, you have the bug Data states exists to prevent.

​
If you get a 402

The plan is not the only reason. The body names which of these it is: A 429 is different: the plan is fine and the day’s allowance is spent. It resets at midnight UTC. See Plans and pricing for the allowance on each plan.

​
Then

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.