Skip to main content

​
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 a signed attestation. Some want USDC to route onchain. Pick the path that matches how far you want to go.

Drop in the badge

Fastest path. widget.js for one ERC-20. widget-discovery.js for a list.

Consume the score

Free widget and batch HTTP. Build your own UI and rules.

Score a list

Live POST /api/batch. Badge by default. Reorder only if you call it.

Trust Oracle

Authoritative wallet (and ERC-20) reads. 0.001 USDC via x402.

Gate with attestations

EIP-712 attestations and a protocol-owned ladder. You own policy.

Protocol Guard

Context-aware checks and alerts. Free, anonymous checks work.

Onchain contracts

AgentRegistry, TrustScoring, TrustGate.claim(), verifier.

Sui capability

Require the non-transferable cap object before a wallet can act.

​
Which one is right

If you just want users to see trust on a swap input, use widget.js. If you run a search or launchpad list, use widget-discovery.js or POST /api/batch. If you want control over how trust looks or behaves, consume the score. Widget and batch are free. The oracle is the paid, authoritative wallet path. If you want trust to actually block or allow an action, that is gating. On Arc that means an attestation plus your ladder. On Sui that means the capability object. If you are settling USDC to agents, that is the contract path, not the scoring policy.

​
Before you build

Everything here runs on testnet today. Widget, batch, gating, and Protocol Guard are free during testnet. Oracle queries cost 0.001 USDC. Treat reads as a signal to weigh, not a settled mainnet judgment.
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. Where a detail is chain-specific, the guide says so. Gating and Protocol Guard have no CORS. Those two are backend integrations. Base URL for every Arc HTTP path below:
Use the www host. The apex redirects, and browsers drop CORS headers on that hop.

​
Most teams start here

The badge, step by step

The single most common integration, start to finish.

Full API reference

Every endpoint in one place.