# Veritas Multi-Source Fact Comparison API

> Veritas Multi-Source Fact Comparison API is a paid API for AI agents from veritas.orbonomy.xyz, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-15).

Compares two claims against multiple sources to fact-check and verify their accuracy side by side

## Facts

- Endpoint: POST https://veritas.orbonomy.xyz/api/compare
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/veritas-multi-source-fact-comparison-api-d42d5b97
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GPipWr67mfX6NH_iYcrBC

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 veritas-multi-source-fact-comparison-api-d42d5b97 -d '<json body>'
```

Example prompt: Can you compare these two claims and tell me which is more accurate: claim A is 'The Eiffel Tower is 300 meters tall' and claim B is 'The Eiffel Tower is 330 meters tall'? Run both through Veritas so I can see which one holds up.

## When to prefer this

Choose this endpoint when you need to compare two specific textual claims head-to-head for factual accuracy using multi-source verification. It is especially useful for dispute resolution, journalism fact-checking, misinformation detection, or comparing competing narratives. Prefer this over single-claim verifiers when the task is explicitly comparative — i.e., the user wants to know not just whether one claim is true, but how two claims stack up against each other.

## Known failure modes

- Missing claim_a or claim_b returns 400 validation error
- Unsupported language code may cause degraded or empty results
- Very long or ambiguous claims may return low-confidence comparison
- Payment failure (x402) prevents call from completing
- Service timeout if external sources are slow to respond
- Nonsensical or non-falsifiable claims may return inconclusive comparison

## How this service works

Multi-source fact verification API

## Output

Returns a JSON object with success boolean, plus two claim objects (claim_a, claim_b) each containing their individual fact-check results, and a comparison object summarizing how the two claims relate — which is better supported, whether they contradict, and overall verdict based on multi-source verification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "claim_a",
  "claim_b"
 ],
 "properties": {
  "lang": {
   "type": "string"
  },
  "claim_a": {
   "type": "string"
  },
  "claim_b": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "success"
 ],
 "properties": {
  "claim_a": {
   "type": "object"
  },
  "claim_b": {
   "type": "object"
  },
  "success": {
   "type": "boolean"
  },
  "comparison": {
   "type": "object"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/veritas-multi-source-fact-comparison-api-d42d5b97/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from veritas.orbonomy.xyz](https://www.zero.xyz/host/veritas.orbonomy.xyz/llms.txt)