JSON Evidence Contradiction Finder

Choose this endpoint when you need to specifically detect logical contradictions and conflicting evidence within a JSON document before acting on it — particularly valuable in agentic pipelines where an LLM has generated structured evidence and you need to verify its internal consistency. Prefer this over general JSON validation when your concern is semantic/logical conflicts between data fields rather than schema compliance or syntax errors.

• Invalid or malformed input JSON returns a parse error
• Missing required body fields returns a 400-level error
• Payment not provided or insufficient USDC balance results in a 402 Payment Required response
• Very large or deeply nested JSON documents may timeout
• Empty JSON object may return ok:true with no contradictions found