> For the complete documentation index, see [llms.txt](https://ozarus.gitbook.io/ozarus-anglais/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ozarus.gitbook.io/ozarus-anglais/getting-started/publish-your-docs.md).

# The Problem: Web3's Security Crisis

The decentralized finance ecosystem has exploded with innovation — but also with risk. Every day,\
thousands of new tokens flood networks like Solana and Ethereum. Among these, only a tiny fraction\
have real utility or honest intent.

Most users are left to analyze smart contracts manually 🧾, rely on Twitter threads, or enter Telegram\
groups full of misinformation. Even advanced users must dig through obscure contract properties to\
detect threats like stealth taxes, honeypots, or minting loopholes.

In many cases, users discover the truth only *after* they’ve lost funds 💸.

What’s worse: many tools that offer token scanning are paywalled, slow, outdated, or technically\
inaccessible to the average user.

This is where Ozarus steps in — to automate, simplify, and empower. 🚀

<figure><img src="/files/ARqkxkP6iTTCDdmUOZLx" alt=""><figcaption></figcaption></figure>

The rapid growth of DeFi, NFTs, and onchain assets has created a fertile ground for scams and rug\
pulls. Key challenges include:

1. **Complex or inaccessible tools:** Analysis platforms are often paid or too technical.
2. **Late threat detection:** Risks are often identified after funds are lost.
3. **Lack of standardized risk scoring:** Evaluating a token remains subjective.
4. **Fragmented information:** Data is scattered across various explorers and channels.


---

# 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://ozarus.gitbook.io/ozarus-anglais/getting-started/publish-your-docs.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.
