Skip to main content
verify_discovery_candidates Queue checks for 1 to 50 selected stored candidates under one workspace budget reservation. Returns every item outcome, including budget rejections. Replay the same key after a network failure. Verification is asynchronous and does not enroll monitoring.
Development preview. This command is absent from the hosted MCP readback. Generic CLI/HTTP calls require a matching development server. Configure LINKTRAIL_API_URL; production does not expose these command routes.
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

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

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. 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

get_candidate_verification_batch Follow the related workflow, inspect capability status, or return to the command index.