Skip to main content
start_domain_baseline Start a baseline. Requires a prepared offer, explicit consent and a retry key. Returns the same durable baseline on replay. Daily spend caps apply before any supplier call; retries never buy twice.
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.
Provider-backed admission requires enabled configuration and available allowance; registration alone does not make retrieval available. Inspect usage and the run’s coverage before interpreting results.

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

New live baseline work requires admission in the selected deployment. Without admission it returns a configuration error; saved runs remain readable. Configuration alone does not guarantee a successful provider result. Synthetic development results do not establish provider coverage. Saved baseline identity and exact website scope survive retries. Indexed candidates, one-off observations and explicitly selected recurring monitors remain separate.

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 / number, required).
  • id (string, required): Resource identifier returned by the operation.
  • workspace_id (string, required): Workspace that owns this record.
  • competitor_binding (object, optional).
  • project_id (string, required): Project that owns this record.
  • scope (object, required).
  • source (string, required).
  • data_mode (string, required).
  • state (string, required): Saved lifecycle or evidence state, as enumerated for this record.
  • created_at (string, required): UTC timestamp when the record was created.
  • updated_at (string, required): UTC timestamp of the last record update.
  • execution_deadline (string, required).
  • timing (object, required).
  • components (object, required).
  • summary (object / null, required).
  • counts (object, required).
  • coverage (object, required): Dataset scope and completeness, including limits on what these results establish.
  • selection (object, required).
  • recurring_monitoring_created (boolean, required): Whether this operation enrolled recurring monitoring.
  • recovery (string, required).
  • progress (object, optional): Read-time progress: live counts, last movement and an honest stalled state. Stalled work may still finish.
  • replayed (boolean, optional): True when the response reuses an earlier request with the same idempotency value.
Types, allowed values, limits and nested fields:
Download input schema · Download output schema

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. 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_domain_baseline · list_domain_baseline_candidates Follow the related workflow. See capability status for availability or the command index for another operation.