Skip to main content
verify_discovery_candidate Queue a saved candidate check with an idempotency key. Returns verification/job records with immutable lineage. Uses check allowance on execution; no synchronous verdict.
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.
Checks and monitoring can consume workspace capacity. Queued admission is not a completed observation; inspect the returned job or saved state.

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

Omitted localReference remains null. The candidate must belong to the supplied saved run. Admission returns a queued job, not verified presence.

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

When retrying with idempotencyKey, reuse the original value and the same arguments; preserve originally omitted optional fields. Generic HTTP puts idempotencyKey in the JSON body, while resource routes use the header where listed below. A changed 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

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