Skip to main content
get_domain_mix_report Compare supplied discovery lanes for a saved competitor set; frozen inventories are optional. Reports generic/niche splits from imported labels, label coverage, per-lane counts and ours versus each inventory. Lanes are not stored: 1–20, up to 2000 rows each. Works with new admission disabled; no discovery or checks.
Name recorded in the 2026-10-17 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 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

Omitting revision reads the current competitor set. Omitted inventoryIds compares only supplied lanes; no competitor inventory is inferred. Lane rows remain request data and are not stored. Missing class labels stay unlabelled; missing added dates remain missing.

Defaults when omitted

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • metadata (object, required).
  • ours (array, required).
  • members (array, required).
Types, allowed values, limits and nested fields:
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. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

These existing resource routes share the operation’s domain behavior. Their parameter placement, status and response envelope can differ from generic invocation. See HTTP route details.

Continue

get_competitor_set Follow the related workflow. See capability status for availability or the command index for another operation.