List matches
list_matchesRead-only
List matches: conflicting domain registrations, trademark filings or app listings found by the monitors. Results are filtered to exactly one status (default inbox) and ordered by assessed risk, worst first. Combine status with min_risk/max_risk or verdict to answer questions like "watched matches with risk above 5". update_matches triages the results by their ids or the same filters.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | Match kind: domain, trademark or app. | |
| page | No | Page number, 1-based. Page size is 50. | |
| since | No | ISO 8601 date or datetime; only matches detected or with activity on/after this time. E.g. "2026-04-20" or a full timestamp for "this week". | |
| status | No | Triage bucket: inbox (needs review), watching (no action needed now, record refreshes on schedule), in_takedown (an open takedown is in progress; record refreshes on schedule), resolved, dismissed. Defaults to inbox. | |
| subject | No | Substring match on the subject (the conflicting domain, mark or app name). At least 3 characters. | |
| verdict | No | Verdict bucket derived from the assessed risk: violation, warning, clear or inconclusive (assessed but unscorable). | |
| max_risk | No | Only matches whose assessed risk is at most this value, on the 0-10 scale. | |
| min_risk | No | Only matches whose assessed risk is at least this value, on the 0-10 scale. Unscored matches are excluded. | |
| monitor_id | No | Restrict to one monitor. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | Yes | ||
| total | Yes | ||
| matches | Yes | ||
| page_size | Yes |