Skip to main content

​
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. Conceptually, for a token or a wallet, you get the tier, the score where one is surfaced, a confidence level, a state where it applies, and any flags.
The JSON below is illustrative. It shows the shape of a read, not the canonical field names or the live endpoint. The programmatic API is being finalized with the batch path. Once it ships, the exact request, fields, and response get documented here verbatim. Until then, do not hardcode against these names.
{
  "subject": "0x...",
  "tier": "HIGH",
  "score": 78,
  "confidence": "high",
  "state": "graduated",
  "flags": ["coordinated_buying"]
}
A few things worth saying about the shape. The top tiers may come back without a numeric score, because at that level the tier is the answer. The state field applies to tokens that came through a launchpad, mining or graduated, and may be absent otherwise. And flags is a list, plain-language patterns, which can be empty.

​
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

The live endpoint and its auth, if any, are being finalized. Rather than print a URL that might change, this slot is held for the real value. Send it to me when it is ready and I will document the working request and response in full, with a copyable example.
Method     to confirm
Endpoint   to confirm
Auth       to confirm

​
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. Treat the flags as the detail that tells a user or your own logic where to look. And lean on confidence and state so you do not present a thin, early read as a settled one.
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.