🔔 ESMA Money Market Funds Register Check

One mmf_check verdict per queried fund — resolve a money market fund against the official ESMA MMF register, keyless and logged-out.

Difference: A verification CHECK, not a dump. Submit fund names and get one definitive verdict each — FOUND (an authorised MMF exists) with its LEI, type, domicile, authorisation status, competent authority, manager and legal framework as evidence; or NOT_FOUND / AMBIGUOUS / SERVICE_FAULT. Distinct from a bulk register export: this answers "is this an authorised MMF, and what are its authorisation facts?" per query.

Output is one mmf_check row per result; billing is pay-per-event, the value event being one mmf check (a $0.02 start fee per run, then $0.05 per mmf check). Source: registers.esma.europa.eu.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

Real rows from run db2FyPtEfN9NcTg0S on build 0.1.5 (2026-09-18), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

input	query	verdict	fund_name	lei	fund_type
LBBW Geldmarktfonds	LBBW Geldmarktfonds	FOUND	LBBW Geldmarktfonds	529900ZW1ATTQKW48E60	Standard VNAV
DANONE MONETAIRE	DANONE MONETAIRE	FOUND	DANONE MONETAIRE	969500LJH58TDSRNXM82	Standard VNAV
ZZZ Notareal Fund 999	ZZZ Notareal Fund 999	NOT_FOUND

The run finished with the status message: PARTIAL: 2 resolved (1 not-found, 0 ambiguous, 0 service-fault, 0 unparseable) of 3 | answers billable=2 | mmf_check charged=2

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_type (string) — e.g. mmf_check
• input (string/null) — e.g. LBBW Geldmarktfonds
• query (string/null) — e.g. LBBW Geldmarktfonds
• source (string/null) — e.g. https://registers.esma.europa.eu/solr/esma_registers_mmf04/select
• verdict (string/null) — e.g. FOUND
• fund_name (string/null) — e.g. LBBW Geldmarktfonds
• lei (string/null) — e.g. 529900ZW1ATTQKW48E60
• fund_type (string/null) — e.g. Standard VNAV
• domicile (string/null) — e.g. GERMANY
• auth_status (string/null) — e.g. Authorised
• competent_authority (string/null) — e.g. Federal Financial Supervisory Authority (BaFin)
• manager_name (string/null) — e.g. LBBW Asset Management Investmentgesellschaft mbH
• legal_framework (string/null) — e.g. UCITS
• is_passported (string/null) — e.g. Passported
• candidates (string/null) — null in every sample row
• unbilled_reason (string/null) — e.g. not_found: no authorised MMF with this exact name in the ESMA register

✅ What you get

What you get

One verdict per query. Only a completed official answer — a FOUND resolution — is billed. NOT_FOUND, AMBIGUOUS, and service-fault are distinguished, emitted, and never billed; a run that resolves nothing fails loud and charges nothing.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "queries": [
    "LBBW Geldmarktfonds",
    "DANONE MONETAIRE",
    "ZZZ Notareal Fund 999"
  ]
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 2 × $0.05 mmf_check = $0.12 on the Free tier — every delivered row was billed.

This actor takes no size cap or filter beyond the input above, so the Store example is the one input to run; put it on a schedule to keep the data current.

🧾 JSON sample record

One real record from run db2FyPtEfN9NcTg0S, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_type": "mmf_check",
  "input": "LBBW Geldmarktfonds",
  "query": "LBBW Geldmarktfonds",
  "source": "https://registers.esma.europa.eu/solr/esma_registers_mmf04/select",
  "verdict": "FOUND",
  "fund_name": "LBBW Geldmarktfonds",
  "lei": "529900ZW1ATTQKW48E60",
  "fund_type": "Standard VNAV",
  "domicile": "GERMANY",
  "auth_status": "Authorised",
  "competent_authority": "Federal Financial Supervisory Authority (BaFin)",
  "manager_name": "LBBW Asset Management Investmentgesellschaft mbH",
  "legal_framework": "UCITS",
  "is_passported": "Passported",
  "candidates": null,
  "unbilled_reason": null
}

🔧 How it works

Source. The actor reads registers.esma.europa.eu — endpoints: https://registers.esma.europa.eu/solr/esma_registers_mmf04/select. Public pages and feeds only; nothing behind a login.

Transport. Plain HTTPS from the Apify platform, no proxy. Every request carries an identified contact User-Agent.

Charging. Each mmf check is charged at the moment it is pushed (mmf_check); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

🔧 How it works

How it behaves

Each fund name is resolved against the official ESMA MMF Solr register by exact registered name; on no exact match, a wildcard search distinguishes AMBIGUOUS (several funds) from NOT_FOUND. robots is honoured (the ESMA registers host publishes no valid robots.txt; treated as permitted). Bounded per run.

Source

https://registers.esma.europa.eu/solr/esma_registers_mmf04/select

Attribution

Source: ESMA registers — registers.esma.europa.eu (Money Market Funds register). Reuse per the ESMA legal notice.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
MMF check (mmf_check)	$0.05	$0.045	$0.04	$0.0335

Worked at the live Free-tier price:

• 3 mmf checks: $0.02 start + 3 × $0.05 = $0.17
• 25 mmf checks: $0.02 start + 25 × $0.05 = $1.27
• 100 mmf checks: $0.02 start + 100 × $0.05 = $5.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 4096 MB.

Yield on the sample run: PARTIAL: 2 resolved (1 not-found, 0 ambiguous, 0 service-fault, 0 unparseable) of 3 | answers billable=2 | mmf_check charged=2.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by registers.esma.europa.eu. It collects only what the source publishes to any visitor, identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (registers.esma.europa.eu) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other NexGen Watch actors actors?
A: Same output shape and billing model; this one covers registers.esma.europa.eu. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Fewer rows than expected → the source had fewer items in scope → widen the input.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

🔗 Related Actors

• Lithuania Company Financial Statements Scraper — Scrape official Lithuanian company financial statements (Registrų centras JAR via data.gov.lt): balance-sheet and profit-statement lines with the rep…
• Lithuania Company Register Scraper — Scrape the official Lithuanian company register (Registrų centras JAR via data.gov.lt): company code, legal name, address, registration and deregistr…
• Missouri Active Alcohol Licenses — One record per associated-person row on each active Missouri alcohol licence (licence number + type, licensee, DBA name, premise address, county, and…
• Netherlands ANBI Register — One structured anbi_record per ANBI decision from the Netherlands Tax Administration's official weekly open-data file — keyless, logged-out, CC0
• Netherlands ANBI Status Check — One anbi_status_check verdict per queried body — resolve an RSIN or organisation name against the current official Belastingdienst ANBI file, keyless…
• NOAA GHCN-Daily Observations — Structured daily climate observations from the U.S. NOAA/NCEI Global Historical Climatology Network - Daily (GHCN-Daily), read directly from the offi…
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of more than 300 public data actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.