Skip to main content
get_candidate_verification Read one candidate check, its job observation, check usage and local-reference lineage. Candidate latest evidence may come from a later requested check.
Name recorded in the 2026-10-17 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

The job observation remains tied to this verification. Candidate latest evidence can point to a later explicitly requested check.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • schema_version (number, required).
  • workspace_id (string, required): Workspace that owns this record.
  • project_id (string, required): Project that owns this record.
  • run_id (string, required): Identifier returned by the related operation.
  • candidate_id (string, required): Identifier returned by the related operation.
  • watch_id (string, required): Identifier returned by the related operation.
  • job_id (string, required): Identifier returned by the related operation.
  • local_reference (string / null, required): Customer reference for joining this record to a local ledger entry.
  • created_at (string, required): UTC timestamp when the record was created.
  • candidate (object, required).
  • job (object, required).
  • observation (object / null, required).
  • watch (object, required).
  • recurring_monitoring_created (boolean, required): Whether this operation enrolled recurring monitoring.
  • replayed (boolean, optional): True when the response reuses an earlier request with the same idempotency value.
Types, allowed values, limits and nested fields:
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. 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

monitor_discovery_candidate Follow the related workflow. See capability status for availability or the command index for another operation.