> For the complete documentation index, see [llms.txt](https://ungate.gitbook.io/ungate-wukong/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ungate.gitbook.io/ungate-wukong/introduction/overview.md).
# Overview
📌 What is Ungate Wukong?
Ungate Wukong is the Trust Layer for Agents, enabling verifiable, autonomous execution using EigenLayer AVS technology. It provides decentralized hosting and verification for AI agents, ensuring execution integrity, agent sovereignty, and proof-backed decision-making.
📌 Why is Ungate Wukong Necessary?
Web3 is shifting towards autonomous agents, but it lacks verifiability and transparency. Without proof, agents can:
• Operate as black boxes with no way to confirm true autonomy.
• Lack accountability since there’s no on-chain reputation system.
• Retain developer control over wallets, leading to liability risks for financial and legal activities.
Ungate Wukong solves these problems by introducing a decentralized execution verification system that ensures every agent is cryptographically provable, sovereign, and tamper-proof.
---
# 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://ungate.gitbook.io/ungate-wukong/introduction/overview.md?ask=&goal=
```
`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.