For developers

A reliable tracker has to preserve meaning as information moves from a source into an interface. This archive focuses on the link between API records and transaction interpretation. Stable identifiers, explicit units, observation timestamps, and separate data states are useful foundations. So is a clear distinction between a submitted transaction, its execution details, and an application’s accounting classification. A technically valid response can still produce an incorrect conclusion when these layers are collapsed.

Read the API guide to design normalization, error handling, and provenance. Read the onchain guide to understand why a transfer list alone cannot establish profit, ownership, or intent. Then inspect the downloadable JSON reference on the API resource page and run its local browser example. The file contains educational profiles rather than market observations, so the interface labels it accordingly. Keep confidential provider credentials out of public static assets, test incomplete responses, and preserve the source needed to reproduce a mapping decision. The aim is a smaller, understandable data contract before adding more integrations or fields.