Bank Enforcement Action Tracker — OCC / FDIC / Fed enforcement API

A bank enforcement action API that merges US federal bank & credit-union enforcement actions into ONE normalized, entity-resolved feed. It tags every action by type (Cease & Desist, Civil Money Penalty, BSA/AML, Fair Lending, Prompt Corrective Action, Written Agreement, Removal/Prohibition, Termination) and by severity, resolves the institution to its FDIC certificate (CERT), and can emit only the new actions since your last run. The raw orders are public but scattered across regulators — this actor builds the transform layer.

Who it's for

• AML / BSA & compliance teams monitoring enforcement risk across banks.
• Bank & fintech risk / vendor-due-diligence analysts screening counterparties.
• KYB / onboarding platforms enriching institutions with enforcement history.
• Bank & regulatory lawyers, journalists, and researchers tracking actions.
• AI agents needing a "bank enforcement action" lookup tool.

What it does

Pulls enforcement actions from the enabled regulators, normalizes each to a unified record, classifies action type + severity (a monetary penalty floors severity to critical), best-effort resolves the institution to an FDIC CERT via the keyless FDIC BankFind API, dedups on a stable action id, and sorts by severity then date. Use monitor mode on a schedule for a new-action alert.

Regulators

• FRB — Federal Reserve Board enforcement actions (enforcementactions.csv). Live: 2,884 actions back to 1989, refreshed as the Fed publishes.
• OCC — Office of the Comptroller of the Currency. Currently unavailable upstream: since roughly 2026-07, OCC's EASearch application answers 302 → /EASearch/404.htm on every data route, including the JSON export this actor reads. It is still attempted on every run, so the feed recovers by itself the moment OCC restores the route. Until then OCC appears in each row's sources_failed and its actions are absent, which is a different fact from "OCC had none".
• FDIC — used for entity resolution (institution name → CERT / state / city).
• NCUA / CFPB — config blocks are scaffolded and ship disabled; they turn on as each regulator's keyless machine-readable feed is verified.

How to read sources_ok / sources_failed

Every row carries both. A regulator listed in sources_failed was not consulted successfully, so the absence of one of its actions proves nothing. If every requested regulator fails, the run fails loudly and bills nothing rather than returning an empty dataset that looks like an answer. Asking for only a regulator this build cannot serve also fails, rather than quietly answering with a different regulator's actions.

sinceDate must be YYYY-MM-DD

sinceDate is compared against each action's ISO date, so a value in any other format does not error — it string-sorts, and the wrong answer is invisible in the output. The run reports SUCCESS and bills either way.

Accepted: 2024-01-15 (canonical), and 2024-1-15, which is zero-padded for you. Anything else fails the run before anything is fetched, and bills nothing — it is never guessed at. Slash forms are rejected on purpose: 05/06/2025 is ambiguous between US (May 6) and EU (June 5) order, and guessing trades a loud, fixable error for a silent one-month window shift.

Measured against this actor's own code over 12 test actions spanning 2019–2026, where sinceDate: "2024-01-01" should return 6:

You send	Old behaviour	Why
01/15/2024	12 of 12 — the whole feed, labelled as a filtered answer	"0…" sorts below every "2024-…", so nothing is dropped
Jan 2024	0 of 12 — reads as "no enforcement actions since then"	"J" sorts above every "2…", so everything is dropped
2024-1-1	4 of 12 — silently loses every month 01–09	"2024-01-15" sorts below "2024-1-1"

All three now fail with a message naming the field, echoing your value, and listing the accepted format. Leave sinceDate empty for no lower bound.

Example input

{
  "regulators": ["FRB", "OCC"],
  "sinceDate": "2024-01-01",
  "actionTypes": ["Civil Money Penalty", "BSA/AML"],
  "institutionName": "",
  "state": "",
  "resolveEntities": true,
  "maxResults": 500,
  "monitor": false
}

Output (per action)

institution_name, regulator, institution_id, id_type, fdic_cert, fdic_matched_name, action_type, severity, severity_rank, penalty_amount, action_date, title, url, source_system, docket_number, location, subject_matters[], termination_date, action_id, sources_ok[], sources_failed[].

Use as an MCP tool

Available to AI agents via mcp.apify.com as a "bank enforcement action tracker" tool — filters in, classified + entity-resolved enforcement records out. The field-level descriptions make it a clean, chainable tool for agent workflows.

FAQ

Which regulators are covered? Federal Reserve enforcement actions today, with FDIC-based entity resolution. OCC is wired and attempted every run but its export is broken upstream (see Regulators). NCUA and CFPB are scaffolded for a future release. How is severity decided? Heuristic: monetary penalties and Cease & Desist / PCA rank highest, written agreements medium, terminations low; any real penalty floors severity to critical. Can I track only new actions? Yes — monitor: true on a schedule. Is it keyless? Yes — the Fed CSV and FDIC BankFind need no key or account. How do you resolve institutions? Fuzzy name match against FDIC BankFind, gated by name-token overlap and (when available) state agreement.

Source

Federal Reserve enforcement actions (federalreserve.gov/supervisionreg/files/enforcementactions.csv) + FDIC BankFind institutions API (banks.data.fdic.gov), with the OCC EASearch export (apps.occ.gov/EASearch) attempted on every run. Official, keyless, no anti-bot.

Pricing (Pay Per Result)

Billed per enforcement-action record returned. Empty searches cost nothing.