> For the complete documentation index, see [llms.txt](https://docs.decrypt0.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decrypt0.com/documentation/readme.md).

# Welcome

#### Continuous Trust Infrastructure for Web3 & Financial Systems

Welcome to Decrypt0’s technical and operational framework.

This document explains:

* Why traditional Web3 security fails after audits
* How Decrypt0 converts security into measurable trust
* The architecture behind AGNI (AI + Human hybrid security model)
* The modular structure of the AGNI platform
* Regulatory and MiCA readiness positioning
* The role and philosophy of the $AGNI ecosystem token

This is not marketing material.\
It is the operational blueprint behind Decrypt0.

### Jump right in

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-bolt">:bolt:</i></h4></td><td><h3>The Trust Gap in Web3 Infrastructure</h3></td><td></td><td></td><td><a href="/documentation/decrypt0-core/quickstart.md">The Trust Gap in Web3 Infrastructure</a></td></tr><tr><td><h4><i class="fa-leaf">:leaf:</i></h4></td><td><h2>AGNI Platform</h2></td><td></td><td></td><td><a href="/documentation/agni/about-agni-platform.md">About AGNI Platform</a></td></tr><tr><td><h4><i class="fa-globe-pointer">:globe-pointer:</i></h4></td><td><h2>AGNI Modules</h2></td><td></td><td></td><td><a href="/documentation/agni/agni-modules.md">AGNI Modules</a></td></tr><tr><td><h4><i class="fa-octagon-check">:octagon-check:</i></h4></td><td><h2>Security &#x26; Standards</h2></td><td></td><td></td><td><a href="/documentation/agni/security-and-standards.md">Security &amp; Standards</a></td></tr><tr><td><h4><i class="fa-chart-line-up">:chart-line-up:</i></h4></td><td><h2>Regulatory &#x26; Readiness</h2></td><td></td><td></td><td><a href="/documentation/agni/regulatory-readiness.md">Regulatory Readiness</a></td></tr><tr><td><h4><i class="fa-dollar-sign">:dollar-sign:</i></h4></td><td><h2>$AGNI Token</h2></td><td></td><td></td><td><a href="/documentation/agni/usdagni-token.md">$AGNI Token</a></td></tr><tr><td><h4><i class="fa-handshake">:handshake:</i></h4></td><td><h2>Partners &#x26; Engagements</h2></td><td></td><td></td><td><a href="/documentation/agni/partners-and-engagement.md">Partners &amp; Engagement</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.decrypt0.com/documentation/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.