verify_prospect
Explicitly request one source-page check for a saved exact-page opportunity. Reserves one source-check unit, preserves recurring monitoring preferences and replays the same idempotency key.
Name recorded in the 2026-10-27 deployment. This page describes current source; verify inputs and access in your connected catalog. Provider configuration and workspace access still apply.
This explicit one-time verification admits one source check. It requires an exact source page, ordinary allowance and a stable idempotency key; it does not enroll recurring monitoring.
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 instructuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.
Full response example
Full response example
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
Request one explicit check of an exact source page. Admission reserves one source-check unit under the current allowance. It does not check a separate destination or change recurring monitoring, cadence or its saved due time. Preserve the original idempotencyKey and arguments after a timeout. The same value returns the same job; a changed placement or another operation under that value conflicts. Do not create another request identifier to recover an uncertain request. Queued is not verified. Read get_check_job with the returned jobId, then get_prospect for evidence. Reading the existing job starts no check. A complete matching present observation can establish a win; a publication claim cannot. Publisher-only and archived records refuse new verification. Current membership, credential, website access, deletion state and exact placement authority are checked again before fetching and publishing evidence. Existing disavow and credit limits still apply.Output fields
Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.watchId(string, required): Identifier returned by the related operation.jobId(string, required): Identifier returned by the related operation.state(string, required): Saved lifecycle or evidence state, as enumerated for this record.errorCode(string / null, required).replayed(boolean, required): True when the response reuses an earlier request with the same idempotency value.recurringMonitoringCreated(boolean, required).usage(object, required).prospect(object, required).
All fields and nested objects
All fields and nested objects
Types, allowed values, limits and nested fields:
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. Operation-specific errors includeUNAUTHORIZED, INSUFFICIENT_SCOPE, CAMPAIGNS_NOT_READY, PROSPECT_ACCESS_DENIED, INVALID_PROSPECT_INPUT, PROSPECT_NOT_FOUND, PROSPECT_SOURCE_REQUIRED, PROSPECT_ARCHIVED, PROSPECT_VERIFICATION_UNAVAILABLE, IDEMPOTENCY_CONFLICT, ADMISSION_REJECTED, WATCH_BUSY, CHECK_COOLDOWN, BILLING_MONITORING_PROTECTED.
See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.