> 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/integration-model.md).

# Integration Model

An integration with zkCross can take different forms depending on the deployment surface.

For ecosystems, it may mean shipping new DeFi rails or cross-chain liquidity functionality.

For applications, it may mean embedding vaults, routing, automation or execution controls into an existing product.

For AI-native systems, it may mean using zkCross as the execution and control layer beneath a planning or intelligence interface.

In each case, the value proposition stays consistent:

* the custody boundary remains clear
* execution remains constrained
* signing remains permissioned
* settlement remains verifiable
* monitoring remains continuous

That consistency is what allows zkCross to serve both infrastructure partners and downstream product builders.