Read the machine-readable files

Available files #

The website publishes structured descriptions of its coverage and policy. These files describe the supported methods; they do not guarantee that a source is available at the moment you read them.

Status rules run deterministically from the versioned policy. An LLM does not choose or revise the results.

• coverage.json contains the reviewed stock-token oracle mappings.
• projects.json contains reviewed project identity profiles and their own coverage version.
• policy.json identifies the current deterministic policy and its parameters.
• receipt.schema.json accepts stored v1, v2, v3 and v4 receipts; schema/1.json, schema/2.json, schema/3.json and schema/4.json describe each version.
• llms.txt points tools to the documentation, the not-assessed list, the observation endpoint and machine-readable resources. Its links are relative to the origin serving it.
• sitemap.xml lists the canonical public pages.

Inspect a receipt as JSON #

Open the JSON representation from a receipt page to read that stored observation. It describes the same evidence as the human-readable receipt and does not run a fresh check.

New receipts use schema v4 and policy 2.2.0. They add pinned-block control reads (owner, EIP-1967 slots, ERC-165 flags), the largest indexed holders, a one-line summary and a fixed notAssessed list to the classification, discovery, project evidence and four panels introduced earlier. Every figure in the summary also exists as a typed field under evidence.

Older v1, v2 and v3 receipts keep their recorded schema and policy. Use the receipt’s schema version when reading fields, and preserve unknowns, nulls and not-attempted results. A shared oracle sweep omits explorer, holder and DEX requests; its null discovery value does not mean a provider returned an empty result.

Handle records carefully #

Keep the chain and full contract address together. Preserve source timestamps, expiry and demo labels. If you encounter a version or status you do not understand, stop interpreting that field until you have its documented meaning.

A saved observation cannot grant permission to trade or establish current conditions after expiry.

Interface scope #

The scanner uses an internal application endpoint. It is not a supported public scanning API or SDK contract. These docs do not promise API keys, bulk scanning, paid access or compatibility for internal routes.

A public API quickstart and OpenAPI description belong with a separately verified public interface. Use Receipts for the current sharing workflow.

For tools that can only fetch a URL, GET /api/check?address=0x… creates the same stored observation as the website’s POST request, under the same rate limits. It is a new observation each time, not a cached read.