# nohumans.directory Listing Verdict

> nohumans.directory Listing Verdict is a paid API for AI agents from api.nohumans.directory, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Returns a pre-spend trust verdict (pay/caution/avoid) for a specific x402 API listing based on probe history, payTo age/stability, and paid-delivery outcomes.

## Facts

- Endpoint: GET https://api.nohumans.directory/v1/listings/:id/verdict
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/nohumans-directory-listing-verdict-9b611b78
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-FPR24Zi_S2k_JB9FOZmT

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 nohumans-directory-listing-verdict-9b611b78
```

Example prompt: Before I call that x402 API, check the nohumans.directory verdict for listing ID abc123 — I want to know if it's safe to pay for, or if I should avoid it.

## When to prefer this

Use this endpoint when an AI agent is about to make a paid x402 API call and needs a pre-spend trust signal to decide whether to proceed. It is specifically designed for agentic workflows that need automated go/no-go decisions on paid API listings in the nohumans.directory ecosystem, based on empirical probe history rather than self-reported metadata.

## Known failure modes

- Listing ID not found — returns error if the provided ID does not correspond to a known listing
- Insufficient probe history — verdict may return 'caution' with limited data
- Stale or unverified listing — verified_via may be null if automated verification has not completed
- Network timeout — fast endpoint but may fail transiently under load
- Invalid ID format — malformed listing ID causes bad request error

## How this service works

nohumans.directory pre-spend verdict for one listing: probe history, payTo age and stability, paid-delivery outcome, verified verb, and a pay/caution/avoid verdict with reasons.

## Output

Returns a JSON object with a 'verdict' field ('pay', 'caution', or 'avoid'), a 'status' string, a 'listing_id', an optional 'verified_via' field indicating verification method, and a 'reasons' array explaining the recommendation based on probe history, payTo address age and stability, and paid-delivery outcomes.

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "queryParams": {
     "type": "object",
     "required": [],
     "properties": {}
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "status": {
   "type": "string"
  },
  "reasons": {
   "type": "array",
   "items": {
    "type": "string"
   }
  },
  "verdict": {
   "enum": [
    "pay",
    "caution",
    "avoid"
   ],
   "type": "string"
  },
  "listing_id": {
   "type": "string"
  },
  "verified_via": {
   "type": [
    "string",
    "null"
   ]
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nohumans-directory-listing-verdict-9b611b78/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.nohumans.directory](https://www.zero.xyz/host/api.nohumans.directory/llms.txt)