VASP Non-Compliant Check

Check whether a crypto-asset service provider is on ESMA's list of non-compliant entities under MiCA.

Pay by wallet (x402) vasp-non-compliant-check

Example

Input
{
  "entity_name": "Google"
}
Answer
{
  "note": "ESMA's non-compliant CASP register is not currently available or may not yet be published. This does not confirm compliance.",
  "matches": [],
  "data_available": false,
  "entity_name_searched": "Google",
  "on_non_compliant_list": false,
  "register_last_updated": null
}

Inputs

FieldTypeRequiredWhat it is
websitestringNoEntity website (optional)
entity_namestringYesCompany or entity name to check

Output fields

How reliably each field appears in a successful answer.

FieldTypeAppears
matchesarrayUsually (present for most inputs)
data_availablebooleanUsually (present for most inputs)
entity_name_searchedstringUsually (present for most inputs)
on_non_compliant_listbooleanUsually (present for most inputs)
register_last_updatedstringUsually (present for most inputs)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "vasp-non-compliant-check",
    "inputs": {
      "entity_name": "Google"
    },
    "max_price_cents": 2
  }'

Limitations

  • Output reflects ESMA Crypto-Asset Service Providers (CASP) Register at query time. Dependent on upstream API availability; may degrade if the provider rate-limits or is temporarily unavailable.

Bundled checks that include it