# TrustAgent Quick Verify

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

Returns a trust score, risk band, and proceed/block recommendation for an EVM address, ERC-8004 agent, or DeFi contract on Base.

## Facts

- Endpoint: GET https://trust-agent.io/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-e09a01e6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TtmzWRFHAUKvsIaOynNiX

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-e09a01e6
```

Example prompt: Before I send that payment, can you check if the address 0x1234...abcd on Base is safe to pay — run it through TrustAgent and tell me the trust score, risk band, and whether we should proceed or block?

## When to prefer this

Use TrustAgent Quick Verify when an agent needs a fast, opinionated safety judgment (proceed/block/hold) for a Base chain address before executing a payment or interaction. It is purpose-built for ERC-8004 agent-to-agent payment safety, DeFi contract screening, and pre-transaction risk gating — prefer it over generic blockchain analytics tools when you need a structured recommendation with per-rule scoring components and hard override caps rather than raw on-chain data.

## Known failure modes

- Address not found or not indexed on Base — returns insufficient_data recommendation with null trustScore
- Chain other than 'base' specified — request refused rather than answered from wrong chain
- Malformed or non-EVM address input — likely 400 validation error
- Insufficient on-chain evidence to evaluate — confidence near 0, recommendation is insufficient_data (not risky)
- Payment failure for x402 micropayment — endpoint returns 402 before evaluation occurs

## 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

A JSON object containing: trustScore (0-100, higher = safer, null if unevaluable), riskBand (minimal/low/moderate/elevated/severe/unknown), recommendation (proceed/proceed_with_caution/hold/block/insufficient_data), confidence (0-1), flags (array of {code, severity, title, detail}), components (per-rule scoring breakdown), and 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."
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "flags": "array of {code, severity, title, detail}",
  "riskBand": "minimal | low | moderate | elevated | severe | unknown",
  "overrides": "hard caps applied after weighting, each with from/cap/reason",
  "components": "per-rule scoring breakdown; the score is reconstructable from these plus overrides",
  "confidence": "0-1, how much evidence backs the score",
  "trustScore": "0-100, higher is safer; null when no rule could be evaluated",
  "recommendation": "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-e09a01e6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from trust-agent.io](https://www.zero.xyz/host/trust-agent.io/llms.txt)