> For the complete documentation index, see [llms.txt](https://zkcross-network-1.gitbook.io/learn.zkcross.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zkcross-network-1.gitbook.io/learn.zkcross.network/welcome/vision.md). # Vision zkCross aims to become the execution fabric that powers the next generation of DeFi, embedded finance and AI-native capital systems. The long-term direction is simple. Users should not need to think in chains, bridges, gas assets, signing complexity or protocol-specific execution semantics. Developers should not need to reconstruct the same cross-chain stack every time they want to ship a serious product. AI systems should not need discretionary control over funds in order to create useful outcomes. zkCross makes this possible by turning fragmented blockchain environments into a unified execution layer with deterministic boundaries. The result is an infrastructure model where: * Liquidity can be accessed across ecosystems * Execution can remain non-custodial * Automation can remain rule-bound * Settlement can be verified * Ecosystems can ship faster --- # 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://zkcross-network-1.gitbook.io/learn.zkcross.network/welcome/vision.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.