> For the complete documentation index, see [llms.txt](https://hub.moonexe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.moonexe.com/home/es/acerca-de-moonexe/licencias-y-cumplimiento.md).

# Licencias y cumplimiento

El marco regulatorio bajo el que opera MoonExe.

## Money Services Business (MSB)

MoonExe opera bajo el marco de **Money Services Business (MSB)** de FinCEN (la Red de Control de Delitos Financieros de EE. UU.). MoonExe también cuenta con un **Certificate of Fact of Good Standing** (certificado de buena reputación).

{% hint style="success" %}
**Las mismas reglas y los mismos estándares de cumplimiento.** Visa, Mastercard y PayPal también operan bajo el marco de licencia MSB de FinCEN.
{% endhint %}

## Regulación de las stablecoins

En Estados Unidos, la **GENIUS Act** establece estándares para las stablecoins y crea un marco regulatorio federal para las stablecoins en USD, lo que refuerza la confianza del mercado en ellas.

{% hint style="warning" %}
Los nuevos productos, como la tarjeta, los servicios de ventanilla fiduciaria y la entrada en nuevos mercados, dependen de la aprobación de socios, de las condiciones comerciales y de los reguladores.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hub.moonexe.com/home/es/acerca-de-moonexe/licencias-y-cumplimiento.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.