# Verity Suite Arbiter

> Verity Suite Arbiter is a paid API for AI agents from suite.veritylayer.dev, paid per call via x402, $0.25/call, status unknown (last checked 2026-09-14).

Adjudicates conflicting claims against provided evidence, returning a calibrated verdict with cited reasons and an optional cryptographic receipt

## Facts

- Endpoint: POST https://suite.veritylayer.dev/arbiter
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/verity-suite-arbiter-5d9bd30e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_f13e5Tn9ci6I77MUvEzdg

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 verity-suite-arbiter-5d9bd30e -d '<json body>'
```

Example prompt: I have two conflicting claims about whether the 2008 financial crisis was primarily caused by deregulation vs. predatory lending — can you adjudicate them against these three evidence excerpts I retrieved and tell me which claim is best supported, with specific reasons citing the evidence?

## When to prefer this

Choose this endpoint when an AI agent needs a calibrated, fail-closed verdict on conflicting claims backed by retrieved evidence, especially when an auditable cryptographic receipt is required. Prefer over general LLM prompting when you need structured verdicts with explicit evidence citations, consistent enum outputs, and tamper-evident receipts for compliance or multi-agent trust pipelines.

## Known failure modes

- Fewer than two claims provided — nothing to adjudicate
- Evidence array empty or off-topic — verdict will be insufficient_evidence
- Claims are not genuinely conflicting — may return undecidable
- Signing not configured — receipt field returns null
- Malformed input schema — 400-level error
- Payment not included or insufficient — x402 payment required error

## How this service works

The trust fabric for AI agents — calibrated, fail-closed services agents pay per call.

## Output

Returns a verdict enum (claim_supported, undecidable, or insufficient_evidence), a confidence score, an array of concrete reasons citing specific evidence items by content and claim index, and optionally an Ed25519-signed VerityLayer receipt for audit/verification purposes.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "claims": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "title": "Claims",
   "description": "Two or more mutually conflicting claims/positions to adjudicate, one per item, in stable order. Fewer than two means nothing to adjudicate."
  },
  "evidence": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "title": "Evidence",
   "description": "Retrieved evidence excerpts/sources to judge from. If empty, weak, or off-topic, the verdict MUST reflect that (insufficient_evidence)."
  },
  "question": {
   "anyOf": [
    {
     "type": "string",
     "maxLength": 2000
    },
    {
     "type": "null"
    }
   ],
   "title": "Question",
   "default": null,
   "description": "The specific point in dispute the claims are answering, if narrower than the claims themselves. Used to scope relevance only."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/verity-suite-arbiter-5d9bd30e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from suite.veritylayer.dev](https://www.zero.xyz/host/suite.veritylayer.dev/llms.txt)