# ESMA MiCA CASP Register: Authorised Crypto Providers (`accountable_eel/esma-mica-casp-register-check`) Actor Look up authorised EU crypto-asset service providers (CASPs) in the official ESMA MiCA register: licensing status, home states, passported EEA countries, services, and LEIs. - **URL**: https://apify.com/accountable_eel/esma-mica-casp-register-check.md - **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community) - **Categories:** Developer tools, Lead generation - **Features:** Limited permissions - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $4.00 / 1,000 casp register entry returneds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. 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 ## 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: ```bash curl "https://api.apify.com/v2/acts/accountable_eel~esma-mica-casp-register-check/run-sync-get-dataset-items?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 ```json { "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 | | | | \ | | | \ | | | | | | \ | \ | | \ | | | | | 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: ```json { "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): ```json { "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:** ```json { "queries": [ "Bitpanda", "Coinbase" ], "maxItems": 20 } ``` **Checking an entity by its 20-character Legal Entity Identifier (LEI):** ```json { "queries": [ "5493007WZ7IFULIL8G21", "984500F14CA4571AAC11", "549300ET4IUR6RCZOL84" ] } ``` **Listing authorized CASPs licensed in a specific EU Member State (e.g. Austria and Luxembourg):** ```json { "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. ```bash curl "https://api.apify.com/v2/acts/accountable_eel~esma-mica-casp-register-check/run-sync-get-dataset-items?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=`, 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=`, 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. # Actor input Schema ## `queries` (type: `array`): 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're only charged for the ones we actually find — a miss costs nothing. ## `homeMemberState` (type: `string`): Optional 2-letter EU Member State code to restrict results (e.g. "AT", "CY", "DE", "FR", "LU", "MT"). ## `serviceCode` (type: `string`): Optional service code or keyword filter (e.g. "custody", "trading platform", "exchange", "portfolio management"). ## `maxItems` (type: `integer`): Maximum matching CASP records to return per query (default 20, max 500). ## `csvUrl` (type: `string`): Optional custom URL if ESMA relocates or updates the CASPS.csv dataset path. Defaults to https://www.esma.europa.eu/sites/default/files/2024-12/CASPS.csv ## `testRun` (type: `boolean`): Turn this on to test your input on a small sample before running the full list. Turn it off to process everything. ## `onlyFound` (type: `boolean`): Only keep rows where something was actually found. Misses are always free, whether or not you show them here. ## `includeKeywords` (type: `array`): Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything. ## `excludeKeywords` (type: `array`): Optional. Drop any result that mentions one of these words. Leave empty to skip nothing. ## `maxResults` (type: `integer`): Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit. ## `columns` (type: `array`): Choose which pieces of information to include in each result row. All are included by default. ## `expandRows` (type: `boolean`): When on, each provider found gets its own row instead of being grouped under its crypto-asset service provider. You're still only charged once per crypto-asset service provider, no matter how many rows it produces. ## `maxConcurrency` (type: `integer`): Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady. ## `proxyConfiguration` (type: `object`): Apify Proxy config. This target is a free public API that needs no proxy — defaults to off, but you can turn one on if you prefer. ## Actor input object example ```json { "queries": [ "Bitpanda", "Coinbase" ], "homeMemberState": "", "serviceCode": "", "maxItems": 20, "csvUrl": "", "testRun": false, "onlyFound": false, "includeKeywords": [], "excludeKeywords": [], "columns": [ "matchedCount", "legalName", "commercialName", "lei", "leiCountry", "homeMemberState", "competentAuthority", "address", "website", "websitePlatform", "authorisationDate", "authorisationEndDate", "services", "servicesRaw", "passportMemberStates", "passportMemberStatesRaw", "legalBasis", "comments", "lastUpdate", "sourceUrl" ], "expandRows": true, "maxConcurrency": 5, "proxyConfiguration": { "useApifyProxy": false } } ``` # Actor output Schema ## `results` (type: `string`): No description # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "queries": [ "Bitpanda", "Coinbase" ], "includeKeywords": [], "excludeKeywords": [] }; // Run the Actor and wait for it to finish const run = await client.actor("accountable_eel/esma-mica-casp-register-check").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "queries": [ "Bitpanda", "Coinbase", ], "includeKeywords": [], "excludeKeywords": [], } # Run the Actor and wait for it to finish run = client.actor("accountable_eel/esma-mica-casp-register-check").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 '{ "queries": [ "Bitpanda", "Coinbase" ], "includeKeywords": [], "excludeKeywords": [] }' | apify call accountable_eel/esma-mica-casp-register-check --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/esma-mica-casp-register-check" } } } ``` 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 ` 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/2X8qEgEzDUi26rBB7/builds/dBKH2uScg4jLvLZg3/openapi.json