CLAIM_CONTRADICTION_SCAN @ 3.0.0

Claim-set contradiction scan

From $0.004 per call

What you get — full service description

Send 2 to 200 claims ({"id","text","subject"?,"source"?}); get back every pair about the same subject that cannot both be right, by two mechanical tests: identical wording except for a negation (CONTRADICTION, e.g. "reserves are fully backed" / "reserves are not fully backed") and different values for the same labelled quantity (DISCONFIRMATION, e.g. "reserve ratio 104" / "reserve ratio 87"). Claims from the same source are not paired. Findings name your claim ids; claim text is never echoed or stored. The method statement comes with every result: an empty result means none of these two shapes, not that the claims are true. Example request: {"claims":[{"id":"a","text":"Reserves are fully backed","subject":"USDX"},{"id":"b","text":"Reserves are not fully backed","subject":"USDX"}]}.

Terms

Product: CLAIM_CONTRADICTION_SCAN @ 3.0.0
Category: Verification
Family: Arbiter Verify
Source: Your request only, computed by Arbiter's own registered program (no third-party data, no network)
Price: From $0.004 per call. Every request is quoted; the 402 response states the exact amount before anything is paid.
Pays with: x402 on eip155:1, eip155:10, eip155:1329, eip155:137, eip155:143, eip155:42161, eip155:43114, eip155:5042, eip155:8453
Freshness: Cacheable Snapshot
Latency: Fast

Get an exact quote

Edit the example request below. Requesting a quote does not pay for or start the job. You will see the amount, accepted networks, destination and expiry first.

Payment uses an x402-compatible client. This page prepares the quote; it does not connect to or charge your wallet.

Buy it with x402 or the API

POST https://arbiterverse.com/api/x402/CLAIM_CONTRADICTION_SCAN with a JSON body {"request": {...}}. An unpaid call answers 402 with the exact x402 v2 terms. Check the amount, asset, network, payTo and expiry before authorizing payment. Retry the same request with its payment proof. Work follows the product's published payment and fulfillment terms; payment must be confirmed before the paid result is delivered. A 202 response means processing: retry the same request and payment identity to collect the result without creating another purchase.

A working example request:

{
  "request": {
    "claims": [
      {
        "id": "a",
        "text": "Reserves are fully backed",
        "subject": "USDX"
      },
      {
        "id": "b",
        "text": "Reserves are not fully backed",
        "subject": "USDX"
      }
    ]
  }
}

Schema and errors: /docs/CLAIM_CONTRADICTION_SCAN.json and /openapi.json. All services.