> For the complete documentation index, see [llms.txt](https://docs.maple.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maple.finance/legal/kyc.md).

# KYC

Maple performs Know-Your-Customer checks on all Lenders and Borrowers across the platform. These checks include:

i) The collection of documentation and information to identify the user. In case of an Entity, the Ultimate Beneficial Owners and Directors are identified as well.

ii) Accreditation checks on Lenders.

iii) PEP and Sanction scans for all users.

iv) As a condition precedent to deposit, all lender wallets are scanned for risk factors using TRM Labs. Lender wallets that hit on risks (including interaction with high risk counterparty wallets) are blocked.

Once onboarded, this gives users access to all the different pools on the Maple platform.


---

# 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.maple.finance/legal/kyc.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.
