🇸🇬 MAS Financial Institutions Directory Change Watch

Compliance and onboarding teams need to know the moment a Singapore financial institution is licensed, delisted, or has its licence category changed. The MAS directory publishes state, not change. This turns it into an auditable delta feed keyed on the source-native MAS entity id.

What you get

• institution_delta — one event per unique change, deduplicated by change_id: added_to_directory, removed_from_directory, licence_category_changed, profile_changed
• Optional before/after snapshots on every change (includeBeforeAfter, on by default)
• Coverage of all five public MAS sectors: Banking, Capital Markets, Financial Advisory, Insurance, Payments
• A removal grace window (removalGraceRuns) so a paging hiccup is not reported as a delisting
• source_check per run and a source_receipt that is always emitted and never billed

Use cases by team

• Compliance & regulatory teams: Evidence, with dates, that an institution held a given MAS licence category when you onboarded it.
• Onboarding / KYC: Catch a counterparty's delisting or licence-category change before it becomes an incident.
• Capital-markets & financial-data teams: Maintain a licensed-entity reference set that updates itself with an audit trail.
• RegTech vendors: License a bounded, deterministic Singapore licensing feed instead of scraping the directory yourself.

Example inputs

Seed a Payments-sector watch

{
  "sector": "Payments",
  "watchMode": true,
  "baselineId": "sg-payments"
}

Watch named institutions only

{
  "sector": "Banking",
  "watchMode": true,
  "nameContains": [
    "Example Bank"
  ],
  "nameMatchMode": "any",
  "baselineId": "sg-banking-named"
}

Licence-category changes only, with detail enrichment

{
  "sector": "Capital Markets",
  "watchMode": true,
  "changeTypes": [
    "licence_category_changed"
  ],
  "includeDetail": true,
  "baselineId": "sg-cm-licences"
}

📊 Sample Output

{
  "record_type": "institution_delta",
  "change_id": "mas-payments-1042-licence-20260725",
  "change_type": "licence_category_changed",
  "sector": "Payments",
  "mas_entity_id": "1042",
  "institution_name": "Example Payments Pte Ltd",
  "before": {
    "licence_category": "Standard Payment Institution"
  },
  "after": {
    "licence_category": "Major Payment Institution"
  },
  "removal_grace_runs_elapsed": 0,
  "source_url": "https://eservices.mas.gov.sg/fid/institution?sector=Payments",
  "observed_at": "2026-07-25T00:00:00Z"
}

How it works

Pick a sector (required) and optionally narrow by institution id, name, or licence category. It enumerates the public, logged-out MAS Financial Institutions Directory (eservices.mas.gov.sg/fid) with bounded pagination and bounded retries under a descriptive User-Agent. Each institution is keyed by its source-native MAS entity id — the leading token of its directory detail URL — within the selected sector, so identity is read from the source and never inferred. Detail URLs are discovered from same-origin directory links and validated against the published path contract rather than constructed by string-building. The first run seeds a private baseline and emits no alerts; later runs emit only institution_delta events, deduplicated by change_id.

Pricing

Event	Price (FREE tier)
Actor start (apify-actor-start)	$0.02 flat, once per run
Institution delta (institution_delta) — primary	$0.08
Source check (source_check)	$0.10, once per run

Pay-per-event on a four-tier ladder (FREE → GOLD, with Platinum/Diamond floored at the Gold rate). Primary event institution_delta: $0.08 / $0.072 / $0.064 / $0.0536. source_check: $0.10 / $0.09 / $0.08 / $0.067. Worked example — a watch run on FREE with 5 licensing changes: $0.02 start + $0.10 source check + 5 × $0.08 = $0.52. Seed runs and genuine-zero runs charge the start + source check only; receipts are never billed. Priced at the top of this family because a missed licence change is a compliance incident, not a lost lead. New to Apify? Start free.

Run it — API, CLI, MCP

API:

curl -X POST "https://api.apify.com/v2/acts/nexgenwatch~mas-register-watch/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" -d @input.json

CLI:

$apify call nexgenwatch/mas-register-watch -i @input.json

MCP: expose nexgenwatch/mas-register-watch through Apify's MCP server, select it as a tool, and pass the same input object.

Related actors — App Intelligence cluster

Actor	What it does
EU TED Tender & Award Watch	Watch EU-wide public procurement: tenders, awards, incumbent changes.
UK Find a Tender Watch	Watch UK tenders, award results and incumbent changes.
CanadaBuys Tender Watch	Watch Government of Canada tender opportunities and awards.
AusTender Award Watch	Watch Australian federal contract awards and incumbents.
GeBIZ Tender & Award Watch	Watch Singapore GeBIZ tenders open, change, close and award.

Compliance & honest limits

• Public, logged-out MAS directory only — no API key, cookie, or login, and no access control is defeated.
• Identified, moderate automation: descriptive User-Agent, bounded pagination, bounded retries with backoff.
• One sector per run — the five public sectors are Banking, Capital Markets, Financial Advisory, Insurance and Payments.
• The first run seeds a private baseline and emits zero deltas by design.
• A removal is reported only after removalGraceRuns has elapsed, so transient paging gaps do not read as delistings.
• This is a change feed over the public directory — it is not legal or regulatory advice, and it does not replace your own licence verification.

FAQ

Which sectors are covered?

All five public MAS sectors: Banking, Capital Markets, Financial Advisory, Insurance, and Payments. sector is the one required input; run one actor per sector to cover several.

How is an institution identified across runs?

By its source-native MAS entity id — the leading token of its directory detail URL — scoped to the selected sector. Identity is read from the source, never inferred from a name, so a rename is a profile_changed event rather than a delete-plus-add.

What change types can I subscribe to?

added_to_directory, removed_from_directory, licence_category_changed, and profile_changed. Set changeTypes to narrow. Precedence per institution per run is add, then remove, then licence category, then profile.

How do you avoid false delistings?

A removal must survive removalGraceRuns before it is emitted, and each delta carries the elapsed grace count so you can audit the call.

Am I billed on a quiet run?

The $0.02 start plus the $0.10 source check. institution_delta is the primary unit, so a stable sector costs almost nothing to watch.

Why is the per-change price the highest in the family?

Because the cost of missing one is highest. A missed licence-category change is a compliance exposure, not a missed sales lead.

Does it enrich from the detail pages?

Only if you set includeDetail: true. It is off by default to keep runs bounded, and detail URLs are discovered from same-origin links, never string-built.

Troubleshooting

• First run emitted nothing? Expected — it seeds the baseline. Re-run with the same baselineId and deltas begin.
• Everything came back as added? The baseline was re-seeded: check baselineId, and whether resetBaseline was set.
• sector rejected? It must be one of Banking, Capital Markets, Financial Advisory, Insurance, Payments — exactly as the directory spells them.
• Name filter matching nothing? nameContains is substring-based; try nameMatchMode: "any" and a shorter fragment.
• Expected a delisting that has not arrived? It is inside the removalGraceRuns window. Lower it for faster, less certain removal calls.

About

Part of the NexGenData registry- and procurement-watch family — one honest, deterministic contract across public official registers. Built by NexGenData. Questions or need a custom feed? Open an issue on the Actor page.