> For the complete documentation index, see [llms.txt](https://docs.onta.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onta.network/basics/interactive-blocks/sentinel.md).
# Sentinel
Sentinel builds comprehensive compliance directly into the protocol, creating a foundation of trust for the entire Onta Network. This system enforces identity verification while preserving privacy through zero-knowledge technology.
Users complete a one-time verification process with trusted identity attesters, receiving verifiable credentials they control plus on-chain attestations that confirm their compliance status. The system monitors transactions at the protocol level, enabling verification, pattern detection, and risk control without compromising privacy.
Sentinel implements transparent transaction limits based on verification tier and jurisdiction, with protocol-level restrictions against sanctioned addresses while maintaining regulatory audibility. By building these compliance mechanisms directly into the infrastructure rather than relying on third parties, Sentinel creates an environment where trust is established through smart contracts, enabling global access while maintaining regulatory alignment.
---
# 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.onta.network/basics/interactive-blocks/sentinel.md?ask=&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.
