ESMA MiCA CASP Register: Authorised Crypto Providers

Look up authorized EU crypto-asset service providers (CASPs) under the Markets in Crypto-Assets Regulation (MiCA) in seconds. Enter crypto firm brand names, legal entity names, 20-character Legal Entity Identifiers (LEIs), or EU Member State codes and receive verified statutory authorization records: licensing status, Home Member State, national competent authority (NCA), permitted crypto services (custody, exchange, trading platforms, transfer services), passported EEA member states, and official websites. Data is sourced directly from the official European Securities and Markets Authority (ESMA) central register.

Who uses it: Crypto compliance and AML officers verifying counterparty regulatory status under EU MiCA rules, fintech and Web3 product teams screening partner licensing, banks and payment processors executing crypto counterparty due diligence, institutional investors auditing regulated crypto custody providers, and legal counsel tracking cross-border passporting notifications across the European Economic Area.

A miss is free. If no entry matches in the ESMA register file, it returns a row with "found": false and is never charged. A miss means "not found in the register file", not "unauthorised": the file is published periodically and may lag national registers.

How to use

1. In the Apify Console. Open the actor page and click Start — the queries field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~esma-mica-casp-register-check/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"queries":["Bitpanda","Coinbase"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

Input

{
  "queries": [
    "Bitpanda",
    "Coinbase"
  ]
}

One crypto-asset service provider brand name, legal entity name, 20-character LEI, or 2-letter EU Member State code per line (e.g. "Bitpanda", "Coinbase", "5493007WZ7IFULIL8G21", "AT", or "ALL"). Accepted formats: Bitpanda, Coinbase, 5493007WZ7IFULIL8G21, Revolut, AT.

You can supply company names (such as "Bitpanda" or "Coinbase"), trading brands (such as "Kraken" or "Revolut"), exact 20-character LEIs (such as "5493007WZ7IFULIL8G21"), or 2-letter EU Member State codes (such as "AT", "CY", "DE", "FR", "LU", "MT"). You can also enter ALL or * to browse all registered providers up to maxItems.

How matching works

The actor matches query terms against the official ESMA central register using precision matching:

• Exact LEI: 20-character alphanumeric strings match the official ISO 17442 Legal Entity Identifier exactly.
• Home Member State: 2-letter uppercase country codes (e.g. "CY", "AT", "DE") match all CASPs authorized in that EU/EEA Home Member State.
• Commercial & Legal Name: Substring and prefix matching on commercial trading brands and registered legal entity names.
• Wildcard ("ALL" or "*"): Matches all authorized entities currently registered in the database up to maxItems.

Unmatched queries return a free "found": false row rather than guessing.

Output

One row per authorized crypto-asset service provider returned, for example:

query	found	status	matchedCount	legalName	commercialName	lei	leiCountry	homeMemberState	competentAuthority	address	website	websitePlatform	authorisationDate	authorisationEndDate	services	servicesRaw	passportMemberStates	passportMemberStatesRaw	legalBasis	comments	lastUpdate	sourceUrl	scrapedAt
Bitpanda	true	OK				<legal entity identifier (lei)>			<national competent authority (nca)>						<authorised mica services (list)>	<authorised services (raw)>		<passported states (raw)>					1970-01-01T00:00:00.000Z

Missing values are represented as null, never 0 or empty strings. All records represent corporate and institutional entities; no personal data of private individuals is processed or exposed.

Sample output record:

{
  "query": "Bitpanda",
  "found": true,
  "status": "OK",
  "matchedCount": 3,
  "legalName": "Bitpanda GmbH",
  "commercialName": "Bitpanda",
  "lei": "5493007WZ7IFULIL8G21",
  "leiCountry": "AT",
  "homeMemberState": "AT",
  "competentAuthority": "Austrian Financial Market Authority (FMA)",
  "address": "Stella-Klein-Löw-Weg 17, 1020 Vienna, Austria",
  "website": "https://www.bitpanda.com",
  "websitePlatform": null,
  "authorisationDate": "09/04/2025",
  "authorisationEndDate": null,
  "services": [
    "a. providing custody and administration of crypto-assets on behalf of clients",
    "c. exchange of crypto-assets for funds",
    "d. exchange of crypto-assets for other crypto-assets",
    "e. execution of orders for crypto-assets on behalf of clients",
    "f. placing of crypto-assets",
    "g. reception and transmission of orders for crypto-assets on behalf of clients",
    "j. providing transfer services for crypto-assets on behalf of clients"
  ],
  "servicesRaw": "a. providing custody and administration of crypto-assets on behalf of clients | c. exchange of crypto-assets for funds | d. exchange of crypto-assets for other crypto-assets | e. execution of orders for crypto-assets on behalf of clients | f. placing of crypto-assets | g. reception and transmission of orders for crypto-assets on behalf of clients | j. providing transfer services for crypto-assets on behalf of clients",
  "passportMemberStates": [
    "AT", "BE", "BG", "CY", "CZ", "DE", "DK", "EE", "ES", "FI", "FR", "GR", "HR", "HU", "IE", "IS", "IT", "LI", "LT", "LU", "LV", "MT", "NL", "NO", "PL", "PT", "RO", "SE", "SI", "SK"
  ],
  "passportMemberStatesRaw": "AT|BE|BG|CY|CZ|DE|DK|EE|ES|FI|FR|GR|HR|HU|IE|IS|IT|LI|LT|LU|LV|MT|NL|NO|PL|PT|RO|SE|SI|SK",
  "legalBasis": "Article 63 - CASP authorisation",
  "comments": null,
  "lastUpdate": "18/04/2025",
  "sourceUrl": "https://www.esma.europa.eu/sites/default/files/2024-12/CASPS.csv",
  "scrapedAt": "2026-11-01T08:00:00.000Z"
}

Sample not-found record (never charged):

{
  "query": "UnregulatedCryptoPlatformX",
  "found": false,
  "status": "NOT_FOUND",
  "message": "Not found in the ESMA CASP register file: no entry matches \"UnregulatedCryptoPlatformX\". This does not show the entity is unauthorised; the file may be out of date or list it under another name.",
  "scrapedAt": "2026-11-01T08:00:00.000Z"
}

Pricing

Billed per crypto-asset service provider record returned: $8.00 per 1,000 at standard rate ($0.008 per row), down to $5.00 per 1,000 on GOLD plans ($0.005 per row). A miss costs nothing.

• CASP register entry returned: $8 per 1,000 providers

Plus a $0.00005 start fee per run. Each event above is billed independently, only when it actually returns data — misses (found:false) are never charged.

Limits and reliability

• Dataset scope: Covers all authorized Crypto-Asset Service Providers (CASPs) notified to ESMA under Title V (Articles 60 and 63) of the EU Markets in Crypto-Assets Regulation (Regulation EU 2023/1114).
• Official updates: The central register is updated periodically as National Competent Authorities (such as BaFin in Germany, AMF in France, FMA in Austria, CySEC in Cyprus, and CSSF in Luxembourg) grant or withdraw CASP licenses.
• Configurable source path: If ESMA updates or changes the publication path of the register file, you can pass a custom URL in the csvUrl input field without needing a code patch.

Example runs

Paste any of these configurations into the Input tab and click Start. All runs are keyless and require no proxy configuration.

Verifying two major European crypto platforms:

{
  "queries": [
    "Bitpanda",
    "Coinbase"
  ],
  "maxItems": 20
}

Checking an entity by its 20-character Legal Entity Identifier (LEI):

{
  "queries": [
    "5493007WZ7IFULIL8G21",
    "984500F14CA4571AAC11",
    "549300ET4IUR6RCZOL84"
  ]
}

Listing authorized CASPs licensed in a specific EU Member State (e.g. Austria and Luxembourg):

{
  "queries": [
    "AT",
    "LU"
  ],
  "maxItems": 50
}

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~esma-mica-casp-register-check/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"queries":["Bitpanda","Coinbase"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~esma-mica-casp-register-check/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"queries":["Bitpanda","Coinbase"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~esma-mica-casp-register-check/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"queries":["{{crypto-asset service provider}}"]}, mapping the row's crypto-asset service provider into the queries array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "mica casp register" — the agent will find and run this actor.