> For the complete documentation index, see [llms.txt](https://docs.zdrive.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zdrive.io/readme.md).

# Overview

ZDrive is a private AI inference platform where your data never leaves your device. You encrypt locally, send only ciphertext to the network, and rely on hardware-enforced isolation — Intel TDX Trusted Execution Environments — to ensure even the operator cannot read your inputs or outputs.

The platform combines three core guarantees:

* **Client-side encryption** — your encryption key is derived from your wallet signature and never leaves your browser
* **On-chain attestation** — you can cryptographically verify the TEE and model running your inference
* **Permanent decentralized storage** — encrypted results persist on Arweave forever, owned by you alone

## Who uses ZDrive?

Developers building agents that handle sensitive data, researchers working with private datasets, enterprises shipping LLM-powered features without surrendering data governance, and anyone running inference at scale without trusting a third party with raw inputs.

The business model is transparent: pay-as-you-go credits for inference, optional vault uploads to Arweave. Anonymous users get a limited free tier. Connected wallets unlock a modest free quota. Paid tiers access the full model stack and bypass datacenter restrictions.

## Core stack

| Layer          | Technology                                |
| -------------- | ----------------------------------------- |
| AI Inference   | Chutes.ai (Intel TDX TEE, Bittensor SN64) |
| Storage        | Arweave via Irys node2                    |
| Encryption     | AES-256-GCM (client-side, browser)        |
| Identity       | Base Wallet (ERC-1271)                    |
| Credits        | ZDriveXCreditsV2 on Base (UUPS proxy)     |
| Infrastructure | Cloudflare Workers + KV                   |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zdrive.io/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.