> For the complete documentation index, see [llms.txt](https://nucleus-ai.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nucleus-ai.gitbook.io/whitepaper/core-features/4.-core-platform-features/4.4-compliance-tools.md).

# 4.4 Compliance Tools

As regulations tighten globally, legal compliance has become a critical (and often overlooked) part of blockchain development. Nucleus AI solves this with automated compliance modules that activate at key moments in the deployment pipeline.

The compliance engine provides:

* KYC (Know Your Customer) workflows for builders and contributors
* AML (Anti-Money Laundering) checks for wallet activity and transactions
* Jurisdiction-based risk scoring for dApps with regional exposure
* Project metadata and wallet flagging based on global compliance databases

All of this happens in the background and requires no manual review. Projects can launch faster, remain compliant, and reduce the risk of regulatory flags down the road.


---

# 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://nucleus-ai.gitbook.io/whitepaper/core-features/4.-core-platform-features/4.4-compliance-tools.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.