Skip to main content
verify_discovery_candidates Queue 1–50 saved candidate checks under one workspace budget reservation. Returns all outcomes, including budget refusals. Retry the same key after network failure. Asynchronous; no monitoring enrollment.
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. A client requesting supported MCP task handling receives a task handle for the same job or batch instead of this ordinary call result. Poll using the negotiated task methods; see task protocol behavior. A cancellation acknowledgement does not establish that work stopped.

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

Every item belongs to one saved run; candidate IDs must be selected deliberately. Omitted per-item localReference remains null. Save the batch identifier and inspect every per-item outcome. Budget refusals and completed unknown observations remain explicit; no recurring monitoring is created.

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).
  • id (string, required): Resource identifier returned by the operation.
  • 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.
  • state (string, required): Saved lifecycle or evidence state, as enumerated for this record.
  • counts (object, required).
  • items (array, required): Records in this bounded page.
  • reservation (object / null, required).
  • replayed (boolean, optional): True when the response reuses an earlier request with the same idempotency value.
  • recurring_monitoring_created (boolean, required): Whether this operation enrolled recurring monitoring.
  • created_at (string, required): UTC timestamp when the record was created.
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_batch Follow the related workflow. See capability status for availability or the command index for another operation.