KOkobaltlabs
marketing-requirement-coverage

Get Run Coverage

Which requirements this analysis read the collateral against, and how each came out.

Grouped by standards document, because that is how a compliance reviewer holds the library in their head — "we checked it against the brand standards and the card disclosures" — and because the document is what a citation resolves to.

get/marketing/requirement-coverage/run/{run_id}

Request

  • Base URL
    https://api.kobaltlabs.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.kobaltlabs.com/marketing/requirement-coverage/run/{run_id}
  • Auth
    none declared

Path parameters

run_idstring uuid required

Response

Successful Response

evaluatedboolean
run_idstring uuid required
document_idstring uuid nullable
checked_atstring date-time nullable
guidelines_consideredinteger
guidelines_without_libraryinteger
candidates_totalinteger
candidates_checkedinteger
exclusionsobject
narrowing_skippedNarrowingSkipped[]
batches_skippedinteger
attachment'document' | 'text'

How the collateral was put in front of the judge.

Recorded because a verdict reached from the text layer is not the same claim as one reached from the rendered page, and afterwards the two are indistinguishable. A PASSED on a rule about a logo, a disclosure's prominence or where a footnote sits means nothing if the model only ever saw extracted text — and prompt_fingerprint cannot tell them apart, because the system prompt, the tool and the schema are identical either way.

Changes

No recorded changes to this operation across all 8 revisions of this API.