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. Admission is disabled until supplier prerequisites are recorded; retries cannot activate it.
Development preview. This command is absent from the verified deployed bundle. Use a matching development environment.
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

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

Supplier admission remains disabled. 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. 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}$”
  • scope (object, required): additional fields rejected
  • source (string, required): must equal “dataforseo”
  • data_mode (string, required): values: “synthetic”, “provider_index”
  • state (string, required): Saved lifecycle or evidence state, as enumerated for this record. values: “queued”, “fetching”, “checking”, “ready”, “partial”, “empty”, “failed”, “cancelled”, “reconciliation_required”
  • created_at (string, required): UTC timestamp when the record was created. format: “date-time”; pattern: ”^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d\.\d{3}(?:Z))$”
  • updated_at (string, required): UTC timestamp of the last record update. format: “date-time”; pattern: ”^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d\.\d{3}(?:Z))$”
  • execution_deadline (string, required): format: “date-time”; pattern: ”^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d\.\d{3}(?:Z))$”
  • timing (object, required): additional fields rejected
  • components (object, required): additional fields rejected
  • summary (object / null, required): Grouped change counts included in this delivery, limited to accessible websites.
  • counts (object, required): additional fields rejected
  • coverage (object, required): Dataset scope and completeness, including limits on what these results establish. additional fields rejected
  • selection (object, required): additional fields rejected
  • recurring_monitoring_created (boolean, required): Whether this operation enrolled recurring monitoring. must equal false
  • recovery (string, required): values: “read_saved_run”, “reconcile_receipt”, “explicit_new_offer”
  • replayed (boolean, optional): 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_domain_baseline · list_domain_baseline_candidates Follow the related workflow, inspect capability status, or return to the command index.