Skip to main content
start_competitor_analysis Retrieve an approved competitor profile in the background and save its inventory automatically. Requires supplier admission and explicit consent. This version retrieves up to 1000 supplier rows; source checks, context and AI assessment remain unavailable. No recurring monitors.
This command name appears in deployment evidence dated 2026-10-16. This page describes current source; read your connected catalog for deployed inputs and access. Workspace scopes and enabled providers 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

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

Requires the exact approved set revision and member, explicit consent, and current supplier admission. The response saves background intent; it does not mean retrieval has finished. This version retrieves up to 1000 supplier rows and saves the inventory automatically. Source checks, occurrence context and managed assessments remain unavailable; no recurring monitors are created. Retry the same idempotencyKey and input while admission remains available. If admission is disabled, read the saved analysis by ID. The retrieval deadline does not authorize additional supplier requests.

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}$"
  • 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}$"
  • competitor_binding (object, required): additional fields rejected
  • scope (object, required): additional fields rejected
  • state (string, required): Saved lifecycle or evidence state, as enumerated for this record. values: "pending", "running", "completed", "partial", "failed", "stopped"
  • stages (object, required): additional fields rejected
  • baseline_run_id (string / null, required): Identifier returned by the related operation.
  • inventory_id (string / null, required): Identifier returned by the related operation.
  • 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))$"
  • last_activity_at (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))$"
  • next_eligible_at (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))$"
  • retrieval_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))$"
  • attempt_count (integer, required): minimum: 0; maximum: 9007199254740991
  • retry_count (integer, required): minimum: 0; maximum: 9007199254740991
  • last_error_code (string / null, required).
  • recurring_monitoring_created (boolean, required): Whether this operation enrolled recurring monitoring. must equal false
  • 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

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. Operation-specific errors include COMPETITOR_ANALYSIS_UNAVAILABLE, COMPETITOR_SUPPLIER_AUTHORITY_UNAVAILABLE, INVALID_COMPETITOR_ANALYSIS_INPUT, COMPETITOR_ANALYSIS_AUTHORITY_CHANGED, COMPETITOR_ANALYSIS_EXPIRED, IDEMPOTENCY_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

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_analysis Follow the related workflow, inspect capability status, or return to the command index.