> ## Documentation Index
> Fetch the complete documentation index at: https://conto.finance/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Trust & Risk Providers
> External trust scoring, reputation, and compliance providers integrated with Conto
# Trust & Risk Providers
Conto integrates with external providers to enrich trust scores, screen for sanctions, and assess wallet reputation. These providers feed into the [trust score calculation](/docs/introduction/concepts#trust-score-factors) (via the **Verification** factor, weighted at 20%) and the [policy rule engine](/docs/policies/advanced#supported-rule-types).
Reputation data supplements Conto's existing trust signals. Sanctions screening remains a separate
compliance control and can block a payment regardless of the reputation result.
## Fairscale (Solana Reputation)
[Fairscale](https://fairscale.xyz) provides composable reputation scoring for Solana wallets. It analyzes onchain behavioral signals, token holdings, transaction patterns, staking activity, and social connections, to produce a 0-100 reputation score.
### What it provides
| Signal | Description |
| ----------------- | ------------------------------------------------------------------------------------------------- |
| **Score** (0-100) | Composite reputation score |
| **Tier** | `bronze`, `silver`, or `gold` |
| **Pillars** | Six scored dimensions: verification, reliability, social, track record, economic stake, ecosystem |
| **Badges** | Behavioral badges (e.g. "LST Staker", "No Instant Dumps") |
### How Conto uses it
* **Trust score enrichment**: For Solana counterparties with no existing network data, Fairscale scores are normalized (0-100 to 0.0-1.0) and used as the network trust score
* **Cold-start enrichment**: Unknown Solana addresses get real trust scores instead of blank `UNKNOWN` defaults
* **Policy rules**: Use `TRUST_SCORE` with the normalized 0.0-1.0 trust score to gate payments
### Policy rule
Require a normalized trust score before allowing payments:
```json theme={null}
{
"ruleType": "TRUST_SCORE",
"operator": "GTE",
"value": "0.5",
"action": "ALLOW"
}
```
Use `TRUST_SCORE` for policy gates. Fairscale enrichment contributes through the normalized trust
score path for unknown Solana counterparties.
### Availability
Fairscale enrichment is available for eligible Solana addresses when it is enabled for your
organization. Contact [support@conto.finance](mailto:support@conto.finance) for availability.
Fairscale is **Solana-only**. It is automatically skipped for EVM addresses, and Conto also skips
it when no enrichment result is available.
### SDK trust result
`GET /api/sdk/network/trust/{address}` returns a normalized trust summary for the requested
address. It includes the global score, verification state, risk level, network relationship count,
active risk-signal count, aggregate transaction history, and the authenticated agent's relationship
summary when one exists.
### Counterparty lifecycle fields
SDK counterparty list, create, and detail responses include a canonical `lifecycleStatus` in
addition to the compatibility fields used by older policies:
* `lifecycleStatus`: one of `DISCOVERED`, `PENDING_REVIEW`, `APPROVED`, `TRUSTED`, `MONITORED`,
`QUARANTINED`, or `BLOCKED`
* `approvalStatus`: `PENDING`, `APPROVED`, or `BLOCKED`
* `trustLevel`: the policy-compatible trust posture, including `SUSPICIOUS` for quarantined
counterparties
Use `lifecycleStatus` for operator workflow state and `trustLevel` / `approvalStatus` for existing
policy rules and SDK clients that have not moved to lifecycle-aware controls yet.
***
## Sanctions Screening
Conto screens wallet addresses against sanctions lists to support compliance requirements. Screening checks known sanctioned addresses (Tornado Cash, Lazarus Group, Garantex, etc.) and can be extended with enterprise providers for deeper risk analysis.
### Providers
| Provider | Description |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Local OFAC** (default) | Built-in OFAC SDN list, screens against known sanctioned wallet addresses. No API key needed. |
| **Chainalysis** | Enterprise-grade blockchain risk scoring via the [Chainalysis KYT API](https://www.chainalysis.com/). Identifies sanctions exposure through cluster analysis. |
| **TRM Labs** | Blockchain intelligence and compliance via the [TRM Labs Screening API](https://www.trmlabs.com/). Screens addresses for sanctions risk indicators. |
### Availability
**Local OFAC** screening is **built into Conto**, no configuration needed. All organizations on [conto.finance](https://conto.finance) automatically get OFAC sanctions screening against known sanctioned addresses.
For enterprise compliance needs, **Chainalysis** and **TRM Labs** provide deeper risk analysis. Contact [support](https://conto.finance) to enable enterprise sanctions screening for your organization.
Sanctions screening is **fail-closed** for enterprise providers: if Chainalysis or TRM Labs is
unavailable, the address is treated as sanctioned to prevent compliance gaps. Local OFAC screening
is always available since it uses a built-in address list.
### Policy rules
Block transactions to sanctioned countries using `GEOGRAPHIC_RESTRICTION`:
```json theme={null}
{
"ruleType": "GEOGRAPHIC_RESTRICTION",
"operator": "IN_LIST",
"value": "[\"CU\", \"IR\", \"KP\", \"SY\", \"RU\"]",
"action": "DENY"
}
```
See [Geographic Restrictions OFAC](/docs/policies/advanced#geographic-restrictions-ofac) for the rule
shape and country-code format.
Always consult legal counsel for compliance requirements. This is not legal advice.
***
## Network Intelligence
In addition to external providers, Conto's built-in **Network Intelligence** aggregates anonymized trust signals across all organizations on the platform:
* Cross-organization address flagging
* Collective fraud detection
* Automatic trust score adjustments based on network-wide behavior
Network Intelligence data is anonymized. Organizations share aggregate trust signals, not
transaction details.
***
## How Scores Are Selected
Conto uses two complementary trust views:
* **Organization trust**, your organization's view of a counterparty based on its own transaction
history.
* **Network trust**, an aggregate view based on shared Conto Network Intelligence signals.
Policies that reference a `TRUST_SCORE` rule use organization trust when it is available and fall
back to the network score for an unknown address. See
[Trust Scoring](/docs/guides/trust-scoring) for the full data model.