> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/eu-level/q-and-a/esma-qa-2143-tied-agents.md). # Tied agents under MiCA | | | | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Authority** | ESMA | | **Q\&A ID** | ESMA\_QA\_2143 | | **Status** | Answer Published | | **Published** | 12 September 2024 | | **Legal basis** | [Article 59](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-59.md) [MiCA](https://github.com/jakesenfti/micawtf/blob/main/mica/README.md); [Article 60](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-60.md) [MiCA](https://github.com/jakesenfti/micawtf/blob/main/mica/README.md) | | **Source** | [ESMA Q\&A](https://www.esma.europa.eu/publications-data/questions-answers/2143) | ### Question May crypto-asset service providers (CASPs) designate persons or entities to provide crypto-asset services on their behalf as agents (similarly to the tied agent regime under MiFID II), where such person or entity is not an authorised CASP? *** ### Answer **Answer provided by the European Commission** [Article 59](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-59.md) of MiCA stipulates that a person shall not provide crypto-asset services, within the EU, unless that person is either authorised as CASP, or a certain financial entity fulfilling the notification criteria according to [Article 60](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-60.md) of MiCA. There is no provision in MiCA that would allow a CASP to designate agents (third parties) for the purposes of receiving orders from clients or potential clients and transmitting them or providing advice in respect of crypto-assets and services offered by that CASP. MiCA therefore, does not provide a regulatory framework for agents acting on behalf of CASPs. Consequently, a CASP cannot designate agents in order to provide crypto-asset services on behalf of the CASP concerned. If a CASP appoints an agent, the agent needs to be a CASP itself. \*\* Disclaimer: \*\* The answers clarify provisions already contained in the applicable legislation. They do not extend in any way the rights and obligations deriving from such legislation nor do they introduce any additional requirements for the concerned operators and competent authorities. The answers are merely intended to assist natural or legal persons, including competent authorities and Union institutions and bodies in clarifying the application or implementation of the relevant legal provisions. Only the Court of Justice of the European Union is competent to authoritatively interpret Union law. The views expressed in the internal Commission Decision cannot prejudge the position that the European Commission might take before the Union and national courts. *** **Source:** [ESMA original document](https://www.esma.europa.eu/publications-data/questions-answers/2143) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.mica.wtf/eu-level/q-and-a/esma-qa-2143-tied-agents.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.