Reg Monitoring

Search regulatory updates from financial regulators across 20 jurisdictions — news, enforcement actions, consultations, policy statements, guidance, final rules, speeches and warnings, from 2011 to today. Filter by regulator, jurisdiction, topic, sector, firm type, content type, urgency, importance and date. Use published_after to answer "what changed recently"; use significance_min (4+) to cut routine noise. Returns compact records with a canonical regmonitoring.com URL for each — cite it. Call regmonitoring_get_update for the full text and analysis of any single result.

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Free-text search over title and summary. All words must appear (case-insensitive). Omit to browse by filters alone."
    },
    "jurisdictions": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Lowercase jurisdiction codes, e.g. [\"uk\",\"us\",\"eu\"]. Call regmonitoring_get_taxonomy for the valid list — guessing \"UK\" or \"United Kingdom\" returns nothing."
    },
    "regulators": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Lowercase regulator codes, e.g. [\"fca\",\"sec\",\"esma\"]. See regmonitoring_get_taxonomy."
    },
    "content_types": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "news",
          "policy_statement",
          "consultation",
          "enforcement",
          "guidance",
          "speech",
          "warning",
          "regulatory_notice",
          "report",
          "final_rule"
        ]
      },
      "description": "Kind of document."
    },
    "topics": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "AML / Financial Crime",
          "Consumer Protection / Conduct",
          "Prudential / Capital Requirements",
          "Operational Resilience / Outsourcing",
          "ESG / Sustainability",
          "Technology & Cyber",
          "Market Abuse / Surveillance",
          "Reporting & Disclosure",
          "Authorisation & Licensing",
          "Senior Managers / Governance",
          "General"
        ]
      },
      "description": "Regulatory themes. Values are exact, e.g. \"AML / Financial Crime\"."
    },
    "sectors": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "Banking & Credit",
          "Investment Management",
          "Wealth & Private Banking",
          "Insurance & Pensions",
          "Capital Markets & Trading",
          "Payments & E-Money",
          "Crypto & Digital Assets",
          "Consumer Credit",
          "Mortgage & Lending",
          "General"
        ]
      },
      "description": "Industry segments."
    },
    "firm_types": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "Asset Manager",
          "Broker Dealer",
          "Wealth Manager",
          "Hedge Fund",
          "Bank",
          "Fintech",
          "Crypto Exchange",
          "Insurance",
          "Family Office",
          "Payment Provider",
          "Credit Union",
          "All Firms"
        ]
      },
      "description": "Types of firm affected. Records tagged \"All Firms\" are cross-cutting and match every firm-type filter, so filtering by \"Asset Manager\" also returns updates that apply to everyone."
    },
    "urgency": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "critical",
          "high",
          "medium",
          "low"
        ]
      },
      "description": "Urgency. NOTE: about 35% of records have no urgency set, and filtering on this excludes all of them. Prefer significance_min unless urgency is specifically what you want."
    },
    "significance_min": {
      "type": "integer",
      "minimum": 1,
      "maximum": 5,
      "description": "Minimum importance, 1 (routine) to 5 (major). Every record is scored, so this is the most reliable way to cut noise. 4+ is \"worth a compliance officer's attention\"."
    },
    "published_after": {
      "type": "string",
      "description": "ISO date (YYYY-MM-DD), inclusive. This is how you answer \"what changed this week\" — no separate tool is needed."
    },
    "published_before": {
      "type": "string",
      "description": "ISO date (YYYY-MM-DD), inclusive."
    },
    "has_analysis": {
      "type": "boolean",
      "description": "Only records carrying AI analysis (about 89% of the corpus)."
    },
    "sort": {
      "type": "string",
      "enum": [
        "newest",
        "oldest",
        "significance",
        "relevance"
      ],
      "description": "Default \"newest\". \"relevance\" ranks by query match and falls back to newest when no query is given."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "description": "Results to return, default 20, max 100."
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Skip this many results, for paging."
    }
  },
  "additionalProperties": false
}

Full detail for one regulatory update, by id or slug: the AI analysis (executive summary, what changed, who is affected, actions required, key dates, compliance impact, citations), any deadline, any enforcement penalty data, and related records. Call this after regmonitoring_search_updates when you need to judge what an update actually requires. Check the analysis `depth` field: "deep" means real structured analysis, "rationale" means only a short classification note. Set include_source_text to read the original document text.

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Record id, as returned by regmonitoring_search_updates."
    },
    "slug": {
      "type": "string",
      "description": "URL slug, the last path segment of a regmonitoring.com/updates/... link. Use this or id; id is faster."
    },
    "include_source_text": {
      "type": "boolean",
      "description": "Include the full scraped text of the source document. Off by default because it can run to tens of thousands of characters. Present on ~72% of records; ask for it when the analysis is not enough to judge impact."
    }
  },
  "additionalProperties": false
}

Regulatory deadlines with dates: consultation response dates, compliance deadlines, and rule effective dates, filterable by date range, status, firm type, jurisdiction and regulator. This is the tool for "what is coming up for my firm" and for building a compliance calendar. Status is derived at query time, never stored, so it is always current; buckets do not overlap (within_90 excludes anything already within 30 days). Set high_confidence_only when the answer will be planned against.

{
  "type": "object",
  "properties": {
    "from": {
      "type": "string",
      "description": "Earliest deadline date, YYYY-MM-DD, inclusive."
    },
    "to": {
      "type": "string",
      "description": "Latest deadline date, YYYY-MM-DD, inclusive."
    },
    "status": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "within_30",
          "within_90",
          "future",
          "passed"
        ]
      },
      "description": "Derived from the date at query time, never stored. \"within_90\" means within 90 days but not within 30 — the buckets do not overlap. Omit this and pass from/to for a plain date range."
    },
    "deadline_types": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "response_due",
          "compliance_deadline",
          "effective_date",
          "expiry",
          "other"
        ]
      },
      "description": "response_due = consultation closes; compliance_deadline = firms must have complied; effective_date = rule takes effect."
    },
    "jurisdictions": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Lowercase jurisdiction codes. See regmonitoring_get_taxonomy."
    },
    "regulators": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Lowercase regulator codes. See regmonitoring_get_taxonomy."
    },
    "firm_types": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "Asset Manager",
          "Broker Dealer",
          "Wealth Manager",
          "Hedge Fund",
          "Bank",
          "Fintech",
          "Crypto Exchange",
          "Insurance",
          "Family Office",
          "Payment Provider",
          "Credit Union",
          "All Firms"
        ]
      },
      "description": "Records tagged \"All Firms\" are cross-cutting and match every firm-type filter."
    },
    "content_types": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "news",
          "policy_statement",
          "consultation",
          "enforcement",
          "guidance",
          "speech",
          "warning",
          "regulatory_notice",
          "report",
          "final_rule"
        ]
      },
      "description": "Kind of document the deadline came from."
    },
    "high_confidence_only": {
      "type": "boolean",
      "description": "Only deadlines extracted with high confidence. Worth setting when the answer will be planned against — a wrong date is worse than no date."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "description": "Default 50, max 100."
    },
    "offset": {
      "type": "integer",
      "minimum": 0
    }
  },
  "additionalProperties": false
}

Enforcement actions across regulators and jurisdictions, with structured penalty data where it has been parsed: entity penalised, amount, currency, breach categories, and whether the penalty is final. Use for "what has this regulator fined firms for", "has this firm been penalised", or precedent research on a breach type. IMPORTANT: only about a quarter of enforcement records have a parsed penalty amount — extraction requires full source text, which many records lack. Do NOT answer "what are the largest fines" from sort=largest_penalty alone: it ranks only the parsed subset. Check the `note` field, which reports how many actions were excluded. Amounts are never converted between currencies.

{
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "Case-insensitive substring of the penalised firm or individual name."
    },
    "jurisdictions": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Lowercase jurisdiction codes."
    },
    "regulators": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Lowercase regulator codes."
    },
    "min_penalty": {
      "type": "number",
      "description": "Minimum penalty amount, in the currency of the record — amounts are NOT converted between currencies, so combine this with `currency` if you need comparable figures."
    },
    "currency": {
      "type": "string",
      "description": "ISO code, e.g. \"GBP\", \"USD\", \"EUR\"."
    },
    "final_only": {
      "type": "boolean",
      "description": "Only penalties recorded as final, excluding proposed or under appeal."
    },
    "published_after": {
      "type": "string",
      "description": "YYYY-MM-DD, inclusive."
    },
    "published_before": {
      "type": "string",
      "description": "YYYY-MM-DD, inclusive."
    },
    "with_penalty_amount_only": {
      "type": "boolean",
      "description": "Only records carrying a structured penalty amount. IMPORTANT: this is a small minority of enforcement records — most enforcement actions are indexed without a parsed figure. Leaving this false returns the full enforcement picture; setting it true returns only what is quantified."
    },
    "sort": {
      "type": "string",
      "enum": [
        "newest",
        "oldest",
        "largest_penalty"
      ],
      "description": "Default \"newest\". \"largest_penalty\" excludes records with no amount."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "description": "Default 20, max 100."
    },
    "offset": {
      "type": "integer",
      "minimum": 0
    }
  },
  "additionalProperties": false
}

Every valid filter value with the number of records carrying it: jurisdiction and regulator codes with their full names, content types, topics, sectors, firm types, urgency levels and deadline types. CALL THIS FIRST if you are unsure of any filter value. Values are exact and case-sensitive — "uk" not "UK", "AML / Financial Crime" not "AML" — and a wrong value returns zero results rather than an error, which is indistinguishable from the data genuinely being empty.

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Coverage statistics for the regmonitoring.com regulatory corpus: how many updates are indexed, the date range they span, how many regulators and jurisdictions are represented, and how many records carry AI analysis, a deadline, a penalty amount or an urgency rating. Call this before making claims about what the corpus does or does not contain — most records have no penalty amount, so an empty enforcement result usually means the data is absent rather than that no enforcement occurred.

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

The Reg Monitoring monthly briefing: an editor-written round-up of the most important financial services regulatory updates of one month, grouped by region (North America; UK and Europe; Asia-Pacific, Middle East and Africa), with a one-line overview per region and the deadlines in the 60 days after it was sent. Use for "what happened in regulation last month" or "catch me up", where a curated summary beats a raw search. Omit `month` for the latest issue. The response includes how to receive the briefing by email each month.

{
  "type": "object",
  "properties": {
    "month": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}$",
      "description": "The month the issue covers, as YYYY-MM (e.g. \"2026-10\"). Omit for the latest issue. Each issue covers the previous calendar month."
    }
  },
  "additionalProperties": false
}