> 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.3-ai-audit-engine.md).

# 4.3 AI Audit Engine

Security is non-negotiable in Web3. Even small bugs can lead to major exploits or project failures. To solve this, Nucleus AI integrates an AI-powered audit engine that performs contract analysis in real time.

When a contract is generated or imported:

* The AI scans the code for known vulnerabilities, backdoors, and attack vectors
* It flags any unsafe or non-standard permissions
* It generates a safety report with scores and plain-language explanations
* Suggestions are given for optimization and risk mitigation

This eliminates the need to wait days or pay thousands for third-party audits. While community or third-party review is still encouraged, this built-in tool ensures that no project goes live without a basic, AI-verified safety check.


---

# 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.3-ai-audit-engine.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.