# ESMA MiCA CASP LEI Portfolio Status Monitor (`plym-actor-factory/eu-esma-mica-casp-lei-portfolio-status-monitor`) Actor

Watch ESMA interim MiCA Crypto-Asset Service Provider LEIs; emit APPEARED/DROPPED/STATUS\_CHANGED and attribute events from the official weekly CASPS.csv. Not an EBA PSD2 twin; not CryptoAlpha; not a full CASP dump billed as rows.

- **URL**: https://apify.com/plym-actor-factory/eu-esma-mica-casp-lei-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 esma mica casp 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

## ESMA MiCA CASP LEI Portfolio Status Monitor

Watch a portfolio of **ESMA interim MiCA Crypto-Asset Service Provider (CASP) LEIs** against the official weekly `CASPS.csv`. Emit unique change events when authorisation membership or attributes change.

### Events

- `APPEARED` / `DROPPED` (directory membership vs published CASPS.csv)
- `STATUS_CHANGED` (`AUTHORISED` ↔ `WITHDRAWN` from `ac_authorisationEndDate` blank vs set; absence from CSV = WITHDRAWN)
- Attribute groups (optional): `SERVICES_CHANGED`, `NAME_CHANGED`, `COMMERCIAL_NAME_CHANGED`, `WEBSITE_CHANGED`, `AUTHORITY_CHANGED`, `HOME_MS_CHANGED`, `ADDRESS_CHANGED`
- Non-billable `RUN_STATUS` (`FIXTURE_HEALTH` / `MONITOR_IDLE` / `CATCHUP_COMPLETE` / `HEALTH_OK`)

### Coverage honesty

- Official ESMA interim MiCA register CSV only — **watchlist filter**; not a full CASP dump billed as rows
- Multi-service CSV rows aggregated by durable **LEI**
- `DROPPED` / `WITHDRAWN` = absent from current CASPS.csv (honest ESMA weekly republish lag)
- Explicitly **not** an EBA PSD2 payment-institution twin; **not** ESMA MiFID permissions twin; **not** CryptoAlpha / trading signals

### Pricing

PPE: `esma-mica-casp-status-event-delivered` @ **$0.02** + `apify-actor-start` @ **$0.00005**.\
Quiet books ≈ start fee only.

### Modes

`sourceMode=fixture` with `emitFixtureDemoEvents=false` → Store health path only (no fake events / no PPE charge).\
`sourceMode=live` → fetch official `CASPS.csv`.

### Input

- `leis` / `caspLeis` — ISO 17442 LEI watchlist (20 chars)
- `signalGroups` — `directory` | `status` | `attributes`
- `esmaCaspsCsvUrl` — optional CSV URL override

### Source

https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/markets-crypto-assets-regulation-mica\
CSV: `https://www.esma.europa.eu/sites/default/files/2024-12/CASPS.csv`

# Actor input Schema

## `leis` (type: `array`):

ISO 17442 Legal Entity Identifiers (20 chars) to monitor against the official ESMA interim MiCA CASPS.csv. Invalid entries skipped with no charge. Not a full CASP dump bill. Not an EBA PSD2 PI twin; not CryptoAlpha.

## `caspLeis` (type: `array`):

Optional alias for leis — same durable LEI keys, merged into the watchlist.

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

Which change groups to evaluate: directory (APPEARED/DROPPED), status (AUTHORISED↔WITHDRAWN), attributes (SERVICES/NAME/COMMERCIAL\_NAME/WEBSITE/AUTHORITY/HOME\_MS/ADDRESS). 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 LEI 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 ESMA interim MiCA CASPS.csv (no API key; weekly 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 MiCA CASP events or charge esma-mica-casp-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 when present.

## `esmaCaspsCsvUrl` (type: `string`):

Optional override for the official ESMA interim MiCA CASPS CSV URL (default sites/default/files/2024-12/CASPS.csv).

## Actor input object example

```json
{
  "leis": [
    "5493007WZ7IFULIL8G21",
    "5299005V5GBSN2A4C303",
    "529900LZM6X3GBFNLG10",
    "5299005I4LYIFW7GKB54",
    "529900HMYYJR2NHVZ124",
    "529900B4G0EGK7Z9KT45",
    "529900KTP3Y86BZKY754"
  ],
  "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, ESMA MiCA CASP 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/eu-esma-mica-casp-lei-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/eu-esma-mica-casp-lei-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/eu-esma-mica-casp-lei-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/eu-esma-mica-casp-lei-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/wOdeKghuSKIKE8IVH/builds/faLCIHhKucuIDg0ns/openapi.json