get · monitors:read

List monitors

Every keyword monitor in the project, oldest first.

Read onlyIdempotent

REST

get/api/v1/monitors
curl "https://herculradar.com/api/v1/monitors" \
  --header "Authorization: Bearer hr_live_…"

MCP

Tool name list_monitors. It takes the same input and returns the same { data, meta } envelope as REST, because both call the same function.

List what is currently being watched: keywords, aliases, sources and whether each monitor is active.

Response

{
  "data": {
    "monitors": [
      {
        "id": "2c1a9f77-1b31-4d6a-9d2e-0f6a2b3c4d5e",
        "name": "Acme",
        "keywords": [
          "Acme",
          "acme.dev",
          "@acmehq"
        ],
        "exclude_keywords": [
          "acme corp cartoon"
        ],
        "sources": [
          "x",
          "reddit",
          "youtube"
        ],
        "group_name": "my_brand",
        "active": true,
        "scan_interval_minutes": 15,
        "last_scanned_at": "2026-09-01T09:20:00.000Z"
      }
    ]
  },
  "meta": {
    "capability": "list_monitors",
    "requestId": "req_9f2b4a8c1d0e",
    "idempotencyReplayed": false,
    "docs": "https://herculradar.com/docs/reference/list_monitors"
  }
}

Authorization

Requires the monitors:read scope. A credential without it gets 403 FORBIDDEN. Resources in projects the credential cannot reach answer 404 NOT_FOUND rather than 403, so ids cannot be probed across tenants.