Tracker tools

Create daily or weekly trackers, confirm their per-run cost before activation, run them manually, read stored results, and permanently remove inactive trackers through eight MCP tools.

Tracker lifecycle

A tracker saves ordinary rankings, compare, citations, and sentiment inputs on a daily or weekly cadence. Your agent can create and review the draft for free before any recurring calls begin.

The draft returns estimatedCostMicroPerRun. Activation requires that exact value as maxCostMicroPerRun, so the current maximum is explicitly accepted before the schedule starts. If the estimate changes, activation is rejected until the new amount is reviewed and confirmed. Recurring calls continue until the tracker is paused.

The eight tools

  • cite42_tracker_create: create a free draft with a name, cadence, and saved primitive inputs. It does not schedule calls.
  • cite42_tracker_update: replace the configuration for free. Any edit returns it to draft so the updated recurring maximum must be confirmed before scheduling resumes.
  • cite42_tracker_activate: activate or resume recurring runs after confirming the latest per-run maximum.
  • cite42_tracker_pause: stop future scheduled calls for free while keeping configuration and run history.
  • cite42_tracker_delete: permanently remove a draft or paused tracker and its run history. Active trackers must be paused first, and deletion waits until no run is queued or running. Financial usage records are retained.
  • cite42_tracker_run: queue one manual run from the saved inputs. A stable request token prevents a retry from creating a duplicate run.
  • cite42_trackers: list tracker status, cadence, configuration, estimate, accepted maximum, and next/last run times for free.
  • cite42_tracker_report: read bounded stored run history, including per-primitive results, changes, statuses, sampled times, and costs, for free. It returns the latest 8 runs by default and accepts up to 20 per call.

Billing & confirmation

Creating, updating, activating, pausing, deleting, listing, and reading stored tracker history cost 0 credits. Each scheduled or manual run bills the saved primitive calls at their normal per-model rates. Activation itself is free, but it authorizes those future billed calls until pause; that is why cite42_tracker_activate requires the current estimate to be confirmed exactly.

Use cite42_pricing for the current rate table and cite42_trackers to re-read a tracker’s estimate before activating it.

Example prompts

Ask in plain language; your agent coordinates the lifecycle tools:

# create and review a draft without starting calls
Create a weekly Cite42 tracker for our rankings, competitor comparison, citations, and sentiment. Show me its credits-per-run estimate, but do not activate it.

# explicit confirmation before recurring billing
Re-read that tracker's current estimate and ask me to approve the exact maximum before you activate its recurring runs.

# free stored-history read
Show me the last 10 runs for our weekly visibility tracker and summarize the biggest ranking, citation, and sentiment changes.