Skip to main content
get_candidate_verification Read a selected candidate check, immutable job observation, source-check usage and local-reference lineage. Candidate latest evidence may refer to a later explicitly requested check.
Available in the deployed MCP and HTTP bundle. Confirm access and inputs with your connected catalog. Workspace scopes and enabled providers 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

Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. 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): must equal 1
  • 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. must equal false
  • replayed (boolean, optional): True when the response reuses an earlier request with the same idempotency value.
Download input schema · Download output schema

Errors and retries

The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the payload under a reused key can conflict. 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, inspect capability status, or return to the command index.