Cohere · AI & Cloud · Proposed by @Grace Rosemary Nettey

Claim-to-Evidence Coverage and Contradiction API

Pre-flight checklist - [x] This is an API feature request, not a consumer app or Comet UI request. - [ ] Check current documentation and forum topics for closely equivalent functionality before posting. - [x] The developer workflow or API use case is described below. Feature type New response field or metadata; New endpoint or API capability Affected API area Search API; Agent API Summary Show which parts of a compound claim are supported, disputed or not established by a cited record. Problem One source may validate a date but not an alleged motive, impact or causal relationship. A citation alongside an entire sentence can misrepresent its evidential scope. Proposed API behavior Return claim components and per-component evidence links, including source spans where permitted, support type, contrary records, missing elements and reviewer qualification. Keep uncertain interpretations explicit rather than converting them to unsupported numerical confidence. Example usage For a claim that a policy changed in March and directly caused a later improvement, the API can confirm the dated policy change while marking the claimed causal impact as not established. Workarounds tried / considered Developers can manually split claims and compare excerpts, or ask models to do so; these methods require verification and may conflate inference with source-supported fact. Impact Research, legal-policy, education and compliance applications benefit