Skip to main content
get_link_review_checkpoint Read the latest explicit human review checkpoint for one authorized project. Includes the exact held artifact, sequence and retained-history gaps. Reading or copying never completes a review or changes monitoring.
Name recorded in the 2026-10-27 deployment. This page describes current source; verify inputs and access in your connected catalog. Provider configuration and workspace access still apply.
This read does not start a verification job.

Example request

Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.

Returned result

Schema-validated example; IDs and dates are illustrative. MCP returns this data in structuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.

Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

Validation and omitted values

projectId is required and must be accessible to the current workspace principal with events:read. This capability is disabled by default; LINK_REVIEW_DISABLED refuses before checkpoint access. It requires separately reviewed migrations and runtime activation. checkpoint is null before an explicit human completion. Otherwise it retains the greatest acknowledged sequence and exact held artifact digest, completion time and incomplete-history flags. Reading, copying or preparing a review never completes one. A human acknowledgment does not resolve retained-history gaps or claim link recovery. Later events remain unreviewed.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions. Download input schema · Download output schema

Errors and retries

Follow the error recovery before retrying this read. Preserve the selected workspace, project, filters and feed. Recovering a read does not require an idempotency key or another verification job. Operation-specific errors include INVALID_INPUT, LINK_REVIEW_DISABLED, PROJECT_NOT_FOUND, WORKSPACE_ACCESS_DENIED, INSUFFICIENT_SCOPE. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

These existing resource routes share the operation’s domain behavior. Their parameter placement, status and response envelope can differ from generic invocation. See HTTP route details.

Continue

get_link_change_report · get_link_reports Follow the related workflow. See capability status for availability or the command index for another operation.