When to use this
Reach for this when the badge is not enough, when you want the read as data and full control over what happens next. Your own badge design. Your own warning copy. Your own rule for what a given tier means in your product. The widget is the easy path. This is the flexible one.What you get back
A read is small and structured. At minimum it carries the tier and, for most tiers, a numeric score.score — at that level the tier is the answer. The tier field can also be NTT (not a tradeable token) for contracts that do not score, such as NFT contracts and wallet addresses. Additional metadata fields may be present in the full response.
One read or a whole list
Single read
Score one token or one wallet. The same read that powers the widget, available as data.
Batch read
Score a whole list in one call, for discovery feeds and rankings. This is the path rolling out now.
The endpoint
Using the read
However you fetch it, the pattern on your side is the same. Map the tier to whatever your product shows, a color, a label, a gate. Use the numeric score where you want finer-grained display. Additional fields in the full response can carry further detail about the read.This is still the non-invasive model. You are pulling a signal and deciding everything downstream. TrustGate has no opinion about how your product uses it.
Next
Score a list to rank it
The discovery path, including optional reordering.
Prefer the ready-made badge?
Let the widget render trust for you instead.