create_competitor_set
Approve one customer and up to ten competitors; no link checks or discovery purchases.
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 operation changes saved state. Review its inputs and retry behavior before calling.
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
Requires exactly one customer, distinct member identities and nonoverlapping approved target scopes. Scope target kind, target and subdomain policy are explicit; none is inferred from a default.Output fields
Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.v(number, required).id(string, required): Resource identifier returned by the operation.revision(integer, required): Recorded revision. For an update, use the revision argument named by that operation.workspace_id(string, required): Workspace that owns this record.project_id(string, required): Project that owns this record.approved_by(string, required).approved_at(string, required).members(array, required).current_revision(number, required).retired_at(string / null, required).
All fields and nested objects
All fields and nested objects
Types, allowed values, limits and nested fields: