# TrustAgent Quick Verify

> TrustAgent Quick Verify is a paid API for AI agents from trust-agent.onrender.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Screens an EVM address or ERC-8004 agent against the OFAC sanctions list and on-chain reputation data to return an explainable 0-100 trust score with a proceed/hold/block recommendation

## Facts

- Endpoint: GET https://trust-agent.onrender.com/v1/verify/quick
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/trustagent-quick-verify-95b5715d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_23-egoMqN6r4LBGbu-9Z4

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability trustagent-quick-verify-95b5715d
```

Example prompt: Before I send payment, can you run a quick trust check on 0x1234abcd... on Base and tell me if it's safe to proceed — I need the trust score, risk band, and your recommendation?

## When to prefer this

Choose TrustAgent when you need an explainable, sanctions-aware trust score for an EVM address or ERC-8004 agent before executing a payment or interaction — especially when you need OFAC compliance screening combined with on-chain reputation in a single low-latency call. Prefer this over raw on-chain lookups when you need coordinated-feedback filtering, a human-readable recommendation, and a structured risk breakdown rather than raw data. It is particularly suited to autonomous agent workflows on Base and EVM chains where a proceed/hold/block decision is needed programmatically.

## Known failure modes

- Insufficient on-chain history returns insufficient_data recommendation rather than a score — not a system error
- Unknown or unregistered address may return trustScore null and low confidence
- Invalid address format or missing required address parameter returns a 4xx error
- Chain not supported defaults to Base or may return an error
- OFAC list sync lag could temporarily miss very recent additions
- Coordinated feedback filtering may reduce confidence score on addresses with thin authentic reputation

## How this service works

Is this counterparty safe to pay? Screens the address against the OFAC sanctions list, reads its ERC-8004 reputation with coordinated feedback filtered out, and returns an explainable 0-100 trust score with a proceed / hold / block recommendation. Reports insufficient_data rather than guessing when the evidence is not there.

## Output

Returns a JSON object containing: a trustScore (0-100, null if no rule could fire), a riskBand (minimal/low/moderate/elevated/severe/unknown), a recommendation (proceed/proceed_with_caution/hold/block/insufficient_data), a confidence value (0-1), an array of flags with code/severity/title/detail, a per-rule components breakdown from which the score is reconstructable, and any overrides (hard caps) applied after weighting with reasons.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "address"
     ],
     "properties": {
      "type": {
       "type": "string",
       "description": "OPTIONAL. agent | contract | defi_protocol | unregistered_address | unknown."
      },
      "chain": {
       "type": "string",
       "description": "OPTIONAL. Only \"base\" is served; any other value is refused rather than answered from the wrong chain. Defaults to base."
      },
      "address": {
       "type": "string",
       "description": "REQUIRED. EVM address, ERC-8004 agentId, or eip155:<chainId>:<registry>/<agentId>."
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "flags": {
       "description": "array of {code, severity, title, detail}"
      },
      "riskBand": {
       "description": "minimal | low | moderate | elevated | severe | unknown"
      },
      "overrides": {
       "description": "hard caps applied after weighting, each with from/cap/reason"
      },
      "components": {
       "description": "per-rule scoring breakdown; the score is reconstructable from these plus overrides"
      },
      "confidence": {
       "description": "0-1, how much evidence backs the score"
      },
      "trustScore": {
       "description": "0-100, higher is safer; null when no rule could be evaluated"
      },
      "recommendation": {
       "description": "proceed | proceed_with_caution | hold | block | insufficient_data. insufficient_data means no judgment was possible — treat it as unknown, not as risky."
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/trustagent-quick-verify-95b5715d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from trust-agent.onrender.com](https://www.zero.xyz/host/trust-agent.onrender.com/llms.txt)