# Trust402 Compare Resources

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

Compares and ranks multiple x402 pay-per-call API candidates against a buyer's goal and budget, returning a trust-scored recommendation.

## Facts

- Endpoint: POST https://trust402.aztecbeacon.uk/api/trust/compare-resources
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/trust402-compare-resources-10b87860
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OO3rF_7ADAxwuuI6oyZQ5

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-compare-resources-10b87860 -d '<json body>'
```

Example prompt: I have three x402 API endpoints I'm considering for summarizing text — compare them for me given my goal of 'high-quality text summarization' and a budget of $0.10 USD, and tell me which one to use first.

## When to prefer this

Use this endpoint when an AI agent needs to autonomously select among multiple x402 pay-per-call API options before committing budget — especially when candidates vary in price, network, or trust signals. Prefer over manual comparison or single-endpoint trust checks when you have 2+ candidates and a defined goal.

## Known failure modes

- Missing or empty candidates array returns validation error
- Budget too low for all candidates results in no viable recommendation
- Malformed endpoint URIs in candidates cause schema rejection
- Unknown x402 networks in candidate metadata may reduce scoring accuracy
- Truncated or missing price fields lead to incomplete ranking

## How this service works

Rank 2-10 candidate paid resources for a goal, budget, and risk policy.

## Output

A JSON object with ok status, tool identifier ('trust.compare_resources'), and a recommendation string (e.g. 'test-first') indicating which candidate or strategy the buyer should pursue based on trust scoring and budget fit.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "goal": {
   "type": "string"
  },
  "budgetUsd": {
   "type": "number"
  },
  "candidates": {
   "type": "array",
   "items": {
    "type": "object",
    "anyOf": [
     {
      "required": [
       "endpoint"
      ]
     },
     {
      "required": [
       "url"
      ]
     }
    ],
    "properties": {
     "id": {
      "type": "string",
      "description": "Stable candidate identifier used in rankings and receipts."
     },
     "url": {
      "type": "string",
      "format": "uri",
      "description": "Alternate field for the x402 resource endpoint."
     },
     "name": {
      "type": "string",
      "description": "Human-readable resource name."
     },
     "x402": {
      "type": "object",
      "description": "Optional parsed x402 challenge metadata."
     },
     "asset": {
      "type": "string",
      "description": "Payment asset address or symbol."
     },
     "payTo": {
      "type": "string",
      "pattern": "^0x[a-fA-F0-9]{40}$"
     },
     "price": {
      "oneOf": [
       {
        "type": "number",
        "minimum": 0
       },
       {
        "type": "string"
       }
      ],
      "description": "Alternate price field accepted by Trust402."
     },
     "accept": {
      "type": "object",
      "description": "Optional single x402 accept object."
     },
     "has402": {
      "type": "boolean",
      "description": "Whether the endpoint is known to return an x402 challenge."
     },
     "network": {
      "type": "string",
      "description": "x402 payment network, for example eip155:8453."
     },
     "endpoint": {
      "type": "string",
      "format": "uri",
      "description": "HTTPS x402 resource endpoint."
     },
     "metadata": {
      "type": "object",
      "description": "Additional public-safe metadata used during scoring."
     },
     "observed": {
      "type": "object",
      "description": "Optional probe observations such as status or latency."
     },
     "priceUsd": {
      "oneOf": [
       {
        "type": "number",
        "minimum": 0
       },
       {
        "type": "string"
       }
      ],
      "description": "Advertised resource price in USD."
     },
     "hasOpenApi": {
      "type": "boolean",
      "description": "Whether the origin publishes OpenAPI metadata."
     },
     "openapiUrl": {
      "type": "string",
      "format": "uri"
     },
     "proofReady": {
      "type": "boolean",
      "description": "Alternate receipt/proof rea
… (truncated)
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/trust402-compare-resources-10b87860/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)