Skip to main content
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.
Development preview. This command is absent from the verified deployed bundle. Use a matching development environment.
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

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

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): must equal 1
  • id (string, required): Resource identifier returned by the operation. pattern: ”^[a-zA-Z0-9_-]{1,128}$”
  • baseline_run_id (string, required): Identifier returned by the related operation. pattern: ”^[a-zA-Z0-9_-]{1,128}$”
  • workspace_id (string, required): Workspace that owns this record. pattern: ”^[a-zA-Z0-9_-]{1,128}$”
  • project_id (string, required): Project that owns this record. pattern: ”^[a-zA-Z0-9_-]{1,128}$”
  • manifest_hash (string, required): minLength: 1
  • cadence_seconds (integer, required): minimum: 3600; maximum: 2592000
  • state (string, required): Saved lifecycle or evidence state, as enumerated for this record. values: “pending”, “partial”, “completed”
  • counts (object, required): additional fields rejected
  • items (array, required): Records in this bounded page. maxItems: 10
  • replayed (boolean, required): True when the response reuses an earlier request with the same idempotency value.
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

This operation has no separate resource alias. Use its generic command route in a matching environment.

Continue

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