Correct the questions, set the rescan cadence
update_competitor_scanCorrect a scan still in draft, and set the cadence of one already armed. questions is where the measurement is won: send the questions to KEEP, with the wording you want asked. A question of the scan left out of the list is removed, and the amount announced by estimated_cost_minor follows, so this is also how the person spends less. Nothing is charged until start_competitor_scan, so rewriting costs nothing; a scan already measured keeps its questions (409) and a new one asks something else. rescan_cadence sets how often an armed scan runs again: "weekly" or "monthly" sets it, null stops it. Weekly widens the list faster and spends as often; monthly follows the pace a corpus of third-party pages moves at. Each pass widens the list rather than refreshing it, because two checks of the same question do not cite the same pages, and what one check found the next one keeps. SPENDS on every pass, the same amount as the first one, so name it to the person before setting a cadence. It states a STATE and replays safely both ways: setting the cadence already in place moves nothing, and stopping it leaves the accumulated list intact.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| questions | No | The questions to KEEP, in the order to ask them. A sent list REPLACES the questions of the scan: one left out is removed. Draft only. | |
| rescan_cadence | No | How often the scan runs again: "weekly", "monthly", or null to stop it. | |
| competitor_scan_id | Yes | The UUID of the competitor scan: call list_competitor_scans to find it. |