`api_verify_claims`

Check an agent's claims about a program against the program's own facts. Each claim gets a three-valued verdict with the evidence that decided it; absence claims are backed by the agenda's enumeration, so "zero cards in scope" carries the examined count as its evidence. A refuted claim is a successful check that found something -- the call stays ok and the refuted field says so. Use this before reporting a finding, not after. Same job as yichus verify-claims, which reads the claims from a file and turns refutals into a nonzero exit code.

Kind: VerifyClaims. Origin: Yichus/Mcp::catalog.

CLI: yichus verify-claims — one implementation: both run ClaimVerifier.verify over the same workspace; the CLI reads the claims from a file and turns refutals into a nonzero exit code, the tool takes them as a parameter and answers refuted.

Parameters

sources (required, array) — JSON array of {fileName, source} Bosatsu files the claims are about.
claims (required, object) — JSON object (or encoded JSON string) with a claims array, each claim naming what it asserts about the program.

Read the result according to this tool’s scope: static checks, bounded execution checks, and descriptive diagrams answer different questions. A successful call is not a general approval of the program. The safety and permissions guide compares the checks and provides editable ownership, guard, and role examples.