# Canada OSFI FRFI Who We Regulate Portfolio Status Monitor (`plym-actor-factory/ca-osfi-frfi-who-we-regulate-portfolio-status-monitor`) Actor

Watch Canada OSFI federally regulated financial institutions and emit typed APPEARED/DROPPED/FI\_\*\_CHANGED/REPRESENTATIVE\_CHANGED events from the official monthly Who we regulate CSV. Not ISED federal corp twin; not a national dump billed as rows.

- **URL**: https://apify.com/plym-actor-factory/ca-osfi-frfi-who-we-regulate-portfolio-status-monitor.md
- **Developed by:** [Daniel Witney](https://apify.com/plym-actor-factory) (community)
- **Categories:** AI, Automation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 osfi frfi status event delivereds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Canada OSFI FRFI Who We Regulate Portfolio Status Event Monitor

Watch a **book of Canada OSFI federally regulated financial institutions (FRFIs)** and emit typed status events when an institution **appears, drops, or changes FI group / industry / type / representative / address / trade name** on the official monthly *Who we regulate* register.

### Source

- Official monthly CSV (open.canada): [Who we regulate — financial institutions (English)](https://open.canada.ca/data/en/dataset/b27ec3ef-7338-4e76-a6fd-128339a92df5)
- Direct resource: `who_we_regulate_fi_eng.csv` (no API key)
- Durable key: `Company Name` × `FI Industry Name` (Company Name alone is near-unique; two name collisions are disambiguated by industry)
- Watchlist accepts plain names (`Royal Bank of Canada`) or composites (`Natixis|Foreign Bank Branches - Lending`)
- **Honest monthly lag** — open.canada publishes on a monthly cadence (P1M). This Actor is a snapshot-diff monitor, not a real-time OSFI feed.

### Events (PPE)

| Event | Meaning |
|-------|---------|
| `APPEARED` | FRFI present after previously missing |
| `DROPPED` | FRFI absent after previously present |
| `FI_GROUP_CHANGED` | FI Group Name change |
| `FI_INDUSTRY_CHANGED` | FI Industry Name change |
| `FI_TYPE_CHANGED` | FI Type Name change |
| `REPRESENTATIVE_CHANGED` | Representative name change (attributes group) |
| `ADDRESS_CHANGED` | Address / city / province / postal change (attributes group) |
| `TRADE_NAME_CHANGED` | Canadian trade company name change (attributes group) |

Non-billable: `RUN_STATUS` (including `FIXTURE_HEALTH`). First observation stores baseline with **no** charge.

### Not this Actor

- **Not** ISED / Corporations Canada federal corporation twin
- **Not** provincial insurance / credit-union twin
- **Not** a national OSFI dump billed as rows
- **Not** a real-time OSFI API (monthly CSV lag only)

### Pricing

- `osfi-frfi-status-event-delivered` @ **$0.02** / unique delivered event
- `apify-actor-start` @ **$0.00005**

### Input

```json
{
  "companyNames": ["Royal Bank of Canada", "Toronto-Dominion Bank (The)", "Bank of Nova Scotia (The)"],
  "sourceMode": "live",
  "signalGroups": ["directory", "status", "attributes"],
  "maxRunSeconds": 180
}
```

`sourceMode=fixture` (default) is Store/CI health — no network, `RUN_STATUS` / `FIXTURE_HEALTH` only unless `emitFixtureDemoEvents=true`.

### Who this is for

- Bank / insurer / trust KYB and counterparty risk desks watching a named FRFI book
- Fintech compliance teams monitoring OSFI membership for partners and sponsors
- Credit / custody onboarding workflows that need membership and classification change events (not full-register dumps)

# Actor input Schema

## `companyNames` (type: `array`):

Canada OSFI federally regulated financial institution company names to monitor against the official monthly Who we regulate CSV (e.g. Royal Bank of Canada). Optional Name|FI Industry composites disambiguate the rare duplicate names. Invalid entries skipped with no charge. Not a national OSFI dump bill.

## `frfiIds` (type: `array`):

Optional alias for companyNames — same durable FRFI identifiers, merged into the watchlist.

## `signalGroups` (type: `array`):

Which change groups to evaluate: directory (APPEARED/DROPPED), status (FI\_GROUP\_CHANGED/FI\_INDUSTRY\_CHANGED/FI\_TYPE\_CHANGED), attributes (REPRESENTATIVE\_CHANGED/ADDRESS\_CHANGED/TRADE\_NAME\_CHANGED). Default: directory+status.

## `maxRunSeconds` (type: `integer`):

Wall-clock budget (CSV download + parse + watchlist diff).

## `maxEvents` (type: `integer`):

Stop after this many unique change events are delivered (does not include RUN\_STATUS).

## `resumeFromCheckpoint` (type: `boolean`):

If true, resume FRFI snapshots and seen event\_uids from the default Key-Value Store.

## `sourceMode` (type: `string`):

fixture = Store/CI health default (no network; RUN\_STATUS only unless emitFixtureDemoEvents=true). live = official OSFI monthly who\_we\_regulate\_fi\_eng.csv (no API key; monthly publish lag).

## `emitFixtureDemoEvents` (type: `boolean`):

When sourceMode=fixture, if true push fabricated change events from local fixtures. Default false so Store daily auto-tests never emit fake OSFI events or charge osfi-frfi-status-event-delivered.

## `maxTotalChargeUsd` (type: `number`):

Optional soft budget hint for delivered change events.

## `asOfHint` (type: `string`):

Optional as\_of label for events / RUN\_STATUS. Defaults to Last-Modified date from the CSV response when present.

## `osfiRegisterCsvUrl` (type: `string`):

Optional override for the official open.canada Who we regulate financial institutions English CSV URL.

## Actor input object example

```json
{
  "companyNames": [
    "Royal Bank of Canada",
    "Toronto-Dominion Bank",
    "Bank of Nova Scotia",
    "Canadian Imperial Bank of Commerce"
  ],
  "signalGroups": [
    "directory",
    "status"
  ],
  "maxRunSeconds": 180,
  "maxEvents": 500,
  "resumeFromCheckpoint": true,
  "sourceMode": "fixture",
  "emitFixtureDemoEvents": false
}
```

# Actor output Schema

## `OUTPUT` (type: `string`):

JSON summary: delivered, charged, runStatus, checkpoint, stats, OSFI FRFI coverage limits

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("plym-actor-factory/ca-osfi-frfi-who-we-regulate-portfolio-status-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("plym-actor-factory/ca-osfi-frfi-who-we-regulate-portfolio-status-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call plym-actor-factory/ca-osfi-frfi-who-we-regulate-portfolio-status-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,plym-actor-factory/ca-osfi-frfi-who-we-regulate-portfolio-status-monitor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/a3idjA6bSKQvSunfO/builds/QdM50wCICqgMT3Mv2/openapi.json