> 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/help/zkcross-faqs.md).

# zkCross FAQs

### Is zkCross a bridge?

No. zkCross is broader than a bridge. It is an execution infrastructure layer that includes routing, signing, deterministic enforcement, settlement verification and monitoring across multiple blockchain environments.

### Is zkCross custodial?

No. zkCross is built around a vault-based custody model where the vault remains the execution boundary. The infrastructure is designed to preserve non-custodial operation.

### Does zkCross rely on third-party bridges and routers as core infrastructure?

The goal of zkCross is to control the critical execution path internally rather than depend on third-party vendors as the primary infrastructure layer.

### What makes zkCross suitable for AI-driven applications?

AI systems can propose actions, but zkCross provides the control, signing, routing and verification framework that keeps those actions bounded and enforceable.

### Has zkCross been used in production?

Yes. zkCross has operated across multiple ecosystems and has already processed substantial on-chain volume and transaction count in live market conditions.

### What is Surf’s relationship to zkCross?

Surf is a consumer-facing product built on top of zkCross infrastructure. It uses the same vault, control, routing, signing and settlement foundation.


---

# 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/help/zkcross-faqs.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.