> For the complete documentation index, see [llms.txt](https://yieldparrotfinance.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://yieldparrotfinance.gitbook.io/docs/extra-info/audits.md).

# Audits

### **Safety is priority  #1 for us!**

We will repeat this every time and we will like to give our community as much security as possible. All Audits will be published here. \
\
Second audit by HashEx coming really soon! Strongly recommended by our partners of Apeswap to ensure high security. Stay tuned!

## Check our first Audit by Techrate

[Link to GitHub](<https://github.com/TechRate/Smart-Contract-Audits/blob/main/Lory%20Token.pdf >)

As we expected the Audit was successfully approved in all aspects by TechRate. \
\
As we promised, we have already submitted our second Audit and waiting to be finished. As soon as we have any notice about it we will be published here and on our Telegram group the results.


---

# 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://yieldparrotfinance.gitbook.io/docs/extra-info/audits.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.
