Add an asset to a monitor: an official domain to watch for conflicting registrations, a mark text for trademark office filings, or a brand keyword for app store listings. This is confirmed work: confirm true records that the user approved the exact type, value, config and reference choice, because the first scan is scheduled as soon as the asset exists and archiving (dashboard-only) only stops future scans, it does not undo a scan that already completed. Required config per type: domain needs config.brand, trademark needs config.offices (subset of US, EM, WO; classes optional, Nice 1-45), app needs config.stores (subset of google_play, app_store). Domain assets also need an explicit reference choice (capture, upload or skip); trademark and app accept an optional upload staged with prepare_asset_upload. A capture always goes through preview_domain: its capture_token makes the stored baseline exactly the render the user approved, and the response includes that screenshot as image content; when the preview rendered nothing (captured false), skip is the remaining choice and reference_stored stays false. site_result carries the probe outcome recorded at preview time. For domain assets, the response's match_scope reports the matching scope: 'distinctive' names are matched across TLDs while 'generic' common terms are only watched on the asset's own suffix. next_scan_at reports when the first scan is due, or null while the monitor is paused. Errors name the cause: invalid input, plan limit reached, or a duplicate already watched by the monitor.