Skip to main content
configure_competitor_refresh Schedule owned-corpus lookups for an approved revision, with cadence and member limit. First cycle is due now; no paid supplier requests or monitoring enrollment.
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 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

cadence and memberLimit are required explicit choices. Initial configuration is due immediately; this does not guarantee a completion time. Updating the same revision preserves its existing due position and unpauses the schedule.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • schedule (object / null, required).
  • latest_cycle (object / null, required).
Types, allowed values, limits and nested fields:
Download input schema · Download output schema

Errors and retries

This write is annotated idempotent without a caller-supplied idempotency key. Reconcile saved state after an uncertain response, then use the same inputs for the same intended operation. Do not add an unsupported key. 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_refresh Follow the related workflow. See capability status for availability or the command index for another operation.