# Trust402 x402 Diligence Report

> Trust402 x402 Diligence Report is a paid API for AI agents from trust402.aztecbeacon.uk, paid per call via x402, $0.15/call, status unknown (last checked 2026-09-14).

Evaluates and scores an x402-enabled resource endpoint for buyer-side trust, procurement readiness, and due-diligence signals, returning a recommendation on how to proceed.

## Facts

- Endpoint: POST https://trust402.aztecbeacon.uk/api/reports/x402-diligence
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/trust402-x402-diligence-report-8a84dae2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1R5lj0w7mBcCPttUHaAja

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 trust402-x402-diligence-report-8a84dae2 -d '<json body>'
```

Example prompt: Before I pay to use this new API at https://someservice.example.com/api/data (origin https://someservice.example.com), can you run a Trust402 diligence check on it? It costs $0.05, supports x402, has an OpenAPI spec, but I'm not sure if it has a well-known file or receipt support.

## When to prefer this

Use this endpoint when an AI agent or buyer has discovered an x402-gated resource (e.g. via x402scan or probe:402) and needs a structured trust assessment before committing payment. Ideal when you have metadata about the resource (price, schema availability, receipt readiness) and want a procurement recommendation rather than just raw metadata.

## Known failure modes

- Invalid or unreachable origin/endpoint URLs cause validation errors
- Missing required fields result in 400-level errors
- Payment failure via x402 protocol blocks execution
- Ambiguous or low-signal inputs may yield a conservative recommendation
- Endpoint returns ok:false if diligence cannot be completed

## How this service works

Produce a full diligence report for an x402 endpoint or origin with hash-ready evidence.

## Output

A JSON object with an 'ok' boolean, the tool identifier ('reports.x402_diligence'), and a 'recommendation' string (e.g. 'test-first') indicating how the buyer should proceed with the resource.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "has402": {
   "type": "boolean"
  },
  "origin": {
   "type": "string",
   "format": "uri",
   "description": "Resource origin URL."
  },
  "endpoint": {
   "type": "string",
   "format": "uri",
   "description": "Resource endpoint URL."
  },
  "priceUsd": {
   "type": "number"
  },
  "hasOpenApi": {
   "type": "boolean"
  },
  "description": {
   "type": "string"
  },
  "hasWellKnown": {
   "type": "boolean"
  },
  "receiptReady": {
   "type": "boolean"
  },
  "hasInputSchema": {
   "type": "boolean"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "tool": "reports.x402_diligence",
  "recommendation": "test-first"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/trust402-x402-diligence-report-8a84dae2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from trust402.aztecbeacon.uk](https://www.zero.xyz/host/trust402.aztecbeacon.uk/llms.txt)