> For the complete documentation index, see [llms.txt](https://docs.abachi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abachi.io/abachi-core/what-is-abachi-core/accreditation-and-kyc.md).

# Accreditation & KYC

Permissioned pools and KYC requirements are already a reality. We see this with the Aave Arc approach. Abachi wants to extend this support as credentialing and verification can be tokenized and shared across partners if all of them are using the Abachi SDK with on-chain proofs available.

This is what the current flow for Aave Arc looks like on the left side. \
\
On the right side is what Abachi hopes to accomplish. \
\
**Some features**:\
\
KYC/AML rules will in most cases already be available on the front-end app. Abachi SDK will allow the front-end app to tokenize these against entity IDs (tenantIDs, businessIDs etc.). Once tokenized, they can then be shared across with partners and carry through properties which can be extended. These include expiry of the KYC token, accreditation level, risk profile, jurisdictional compliance rules etc. The possibilities are endless to essentially tokenize compliance on a per entity.

 

![](https://documents.lucid.app/documents/a4ae3aad-9ea2-44d6-a27d-82bf663a422c/pages/0_0?a=794\&x=-64\&y=-7\&w=1848\&h=1024\&store=1\&accept=image%2F*\&auth=LCA%20d3bccefdd7402fb2fe08347188abb6e726cef854-ts%3D1638842005)

As such more services can also be powered by partners. Abachi core will also provide integrations with third party services so e.g. if you do not have a KYC provider, you can use the Abachi service to tap into BlockPass and others. Any relevant data stays with the front-end partner, a tokenized proof of that data is tokenized and shared. 

![](https://documents.lucid.app/documents/a4ae3aad-9ea2-44d6-a27d-82bf663a422c/pages/0_0?a=794\&x=136\&y=1115\&w=1408\&h=1001\&store=1\&accept=image%2F*\&auth=LCA%2075de1918751b2408864f237419ca63bb5c594f8f-ts%3D1638842005)


---

# 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://docs.abachi.io/abachi-core/what-is-abachi-core/accreditation-and-kyc.md?ask=<question>&goal=<endgoal>
```

`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.