get_owner_digest
Read your own website digest settings. Requires a signed-in owner or administrator.
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 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 instructuredContent 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 signed-in owner or administrator. Recipients come from the verified account address, never request arguments. Delivery must be separately enabled. Accepted handoff is not confirmed delivery; unknown outcomes are retained and never blindly resent. Exact event links may expire with retained history.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
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. Operation-specific errors includeOWNER_DIGEST_HUMAN_REQUIRED, OWNER_DIGEST_ACCESS_DENIED, OWNER_DIGEST_NOT_READY, OWNER_DIGEST_SCOPE_CLOSED, OWNER_DIGEST_CONFLICT, OWNER_DIGEST_RECIPIENT_REQUIRED, OWNER_DIGEST_SUPPRESSED, OWNER_DIGEST_EVENT_EXPIRED, INVALID_OWNER_DIGEST_INPUT, INVALID_CURSOR.
See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.