get_domain_baseline_monitor_batch
Read a monitor batch receipt. Per-item outcomes distinguish created, already monitored, ineligible and failed; reading never activates a watch or checks a source.
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.
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
Saved receipt read is scoped and never activates monitoring.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.baseline_run_id(string, required): Identifier returned by the related operation.workspace_id(string, required): Workspace that owns this record.project_id(string, required): Project that owns this record.manifest_hash(string, required).cadence_seconds(integer, required): Configured check interval in seconds. Scheduling and admission can delay completion.state(string, required): Saved lifecycle or evidence state, as enumerated for this record.counts(object, required).items(array, required): Records in this bounded page.replayed(boolean, required): True when the response reuses an earlier request with the same idempotency value.
All fields and nested objects
All fields and nested objects
Types, allowed values, limits and nested fields: