Skip to main content
get_public_contacts Extract explicitly published emails and contact-page candidates from the latest saved public HTML. Returns dated evidence; does not infer emails, verify deliverability or send outreach.
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.
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

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

Requires a completed watch check and retained public HTML. Addresses must be explicitly published; extraction does not test deliverability or send a message. The current observation must have complete, usable public HTML with a matching retained capture. Unknown, unqualified or misbound captures are refused; there is no fallback to an older check. Expired evidence requires a new check. Contact addresses retain the observation date and remain unverified for deliverability; a complete page without the expected backlink may still contain useful public contacts.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • watch_id (string, required): Identifier returned by the related operation.
  • observation_id (string, required): Identifier returned by the related operation.
  • contacts (array, required).
  • contact_pages (array, required).
  • coverage (object, required): Dataset scope and completeness, including limits on what these results establish.
Types, allowed values, limits and nested fields:
Download input schema · Download output schema

Errors and retries

Follow the error recovery before retrying this read. Preserve the selected workspace, project, filters and feed. Recovering a read does not require an idempotency key or another verification job. 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_history Follow the related workflow. See capability status for availability or the command index for another operation.