> 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/builders-and-ecosystems/for-blockchains.md).

# For Blockchains

zkCross is designed for blockchains that want to activate DeFi, liquidity movement and AI-ready execution without rebuilding critical infrastructure internally.

A blockchain integration with zkCross can enable:

* cross-chain liquidity access
* execution rails for DeFi applications
* deterministic control over automated flows
* secure signing and authorisation patterns
* fiat and wallet abstraction layers where relevant
* a faster path to user-facing products built on top of production-tested infrastructure

For ecosystems, zkCross can function as a DeFi infrastructure partner rather than only as an app developer. The value is not just a launch. The value is a reusable execution layer that helps the ecosystem support more products over time.


---

# 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/builders-and-ecosystems/for-blockchains.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.