# ESMA MiCA Non-Compliant VASP Check

> ESMA MiCA Non-Compliant VASP Check is a paid API for AI agents from api.strale.io, paid per call via x402, $0.0216/call, status unknown (last checked 2026-09-15).

Checks whether a crypto-asset service provider (VASP) appears on ESMA's list of non-compliant entities under MiCA regulation

## Facts

- Endpoint: GET https://api.strale.io/x402/vasp-non-compliant-check
- Price: $0.0216/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-strale-io-3baffca4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ujmVn96n1z45WNBiULuko

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability api-strale-io-3baffca4
```

Example prompt: Can you check if 'Binance' is on ESMA's non-compliant entities list under MiCA regulation — their website is binance.com?

## When to prefer this

Use this endpoint when you need to verify whether a specific crypto-asset service provider has been flagged by ESMA for non-compliance under MiCA regulation — particularly useful for due diligence workflows, onboarding checks, or compliance screening of EU-regulated crypto entities. Prefer this over generic web searches when you need a structured, programmatic compliance flag rather than unstructured news results.

## Known failure modes

- Missing required entity_name parameter returns validation error
- Entity not found in ESMA list returns a clean non-flagged result (not an error)
- Ambiguous company names may return false negatives if the exact name doesn't match the ESMA listing
- Service unavailable or ESMA data source unreachable returns 5xx error
- Payment failure via x402 returns 402 Payment Required

## How this service works

Check if a crypto-asset service provider is on ESMA's non-compliant entities list under MiCA regulation. Flags entities that have been identified for regulatory infringement.

## Output

Returns whether the named entity appears on ESMA's MiCA non-compliant entities list, including a flag indicating regulatory infringement status and any relevant compliance details found for the queried company name and optional website.

## Example request

```json
{
 "input": {
  "type": "http",
  "method": "GET",
  "queryParams": {
   "website": "binance.com",
   "entity_name": "Binance"
  }
 }
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "entity_name"
     ],
     "properties": {
      "website": {
       "type": "string",
       "description": "Entity website (optional)"
      },
      "entity_name": {
       "type": "string",
       "description": "Company or entity name to check"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-strale-io-3baffca4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.strale.io](https://www.zero.xyz/host/api.strale.io/llms.txt)