> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trustgated.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Pick your integration

> Three ways to bring TrustGate into your product. Choose by how much you want to build.

## Start here

There is no single way to integrate TrustGate, because teams want different amounts of it. Some want a badge live by the end of the day. Some want raw tiers and flags to drive their own logic. Some want to enforce trust as an actual gate. Pick the path that matches how far you want to go.

<CardGroup cols={2}>
  <Card title="Drop in the badge" icon="code" href="/integrate/widget">
    The fastest path. One script tag renders a live trust badge in your UI. No backend.
  </Card>

  <Card title="Consume the score" icon="plug" href="/integrate/consume-score">
    Read tiers and flags as data and build whatever you want on top.
  </Card>

  <Card title="Optional reorder" icon="arrow-down-wide-short" href="/integrate/reorder">
    Score a list and, if you choose, re-rank a discovery feed by trust.
  </Card>

  <Card title="Gate by capability (Sui)" icon="lock" href="/integrate/sui-cap">
    Require the onchain capability object before a wallet can act.
  </Card>
</CardGroup>

## Which one is right

If you just want users to see trust, use the badge. It is the least work by a wide margin and it covers most cases. Show it next to a token or a wallet and you are done.

If you want control over how trust looks or behaves in your product, consume the score. You get the tier and flags as data and decide everything else, your own badges, your own warnings, your own thresholds for what to do with a given read.

If you run a feed and want trust reflected in it, look at discovery and the reorder path. Badge and flag your list as the default, and reach for reordering only if and when you want it.

And if you want trust to actually block or allow an action, not just inform one, that is gating. On Sui that means requiring the capability object.

## Before you build

<Note>
  Everything here runs on testnet today, and integration is free during testnet. Treat reads as a signal to weigh, not a settled mainnet judgment.
</Note>

Two principles hold across every path. TrustGate is non-invasive: you consume a signal, you keep your interface, nothing takes over your UI or your rules. And the score means the same thing everywhere, so an integration you understand on one chain carries straight over to the other. Where a detail is chain-specific, the guide says so.

## Most teams start here

<CardGroup cols={2}>
  <Card title="The badge, step by step" icon="rocket" href="/integrate/widget">
    The single most common integration, start to finish.
  </Card>

  <Card title="Raw data instead" icon="plug" href="/integrate/consume-score">
    If you would rather build the UI yourself.
  </Card>
</CardGroup>