> For the complete documentation index, see [llms.txt](https://docs.vortexfinance.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vortexfinance.co/compliance-and-partner-model.md).

# Compliance & Partner Model

Compliance in Vortex is managed through licensed local partners. They conduct KYC/KYB checks, hold fiat accounts in their jurisdictions, and handle reporting according to local rules. This ensures that every corridor operates within its legal framework.

Vortex itself does not run KYC or KYB. By relying on partners with the required licenses, onboarding is faster and duplication is avoided. Users see a single, unified service while each partner remains responsible for its own market.

### Current Partners

* **BRLA Digital Ltda (Brazil)** – [Website](https://avenia.io/) – [Terms of Service](https://app.avenia.io/Avenia-TC.pdf) 
* **ANCLAP (Argentina)** – [Website](https://www.anclap.com/) 
* **Monerium EMI ehf. (Europe)** – [Website](https://monerium.com/) – [Terms of Service](https://monerium.com/policies/personal-terms-of-service-2025-05-20/) 
* **MyKobo sp. z.o.o. (Europe)** – [Website](https://mykobo.io/) – [Terms of Service](https://terms.mykobo.co/) 


---

# 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://docs.vortexfinance.co/compliance-and-partner-model.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.