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

# Welcome to CapyData

​

<figure><img src="https://images.gitbook.com/__img/dpr=2,width=760,onerror=redirect,format=auto,signature=1970244517/https%3A%2F%2Fcapydata.vercel.app%2Fcapybara.png" alt=""><figcaption></figcaption></figure>

#### What is CapyData? <a href="#what-is-capydata" id="what-is-capydata"></a>

**CapyData** is a decentralized data marketplace built on the **Sui blockchain**. It allows users to securely monetize their datasets or purchase high-quality data for AI, research, and analytics without relying on centralized intermediaries.Unlike traditional cloud storage or data brokers, CapyData ensures that **you remain in control**. Files are encrypted on your device before they ever touch the internet, and access is managed strictly through ownership of digital assets (NFTs).

**Core Mission**

Our mission is to power Web3-native AI and data workflows by combining:

1. **Privacy:** Client-side encryption (SEAL).
2. **Permanence:** Decentralized storage (Walrus).
3. **Ownership:** Move-based NFTs for access control.

**Key Features**

| Feature                       | Description                                                                                           |
| ----------------------------- | ----------------------------------------------------------------------------------------------------- |
| **🔐 Client-Side Encryption** | Files are encrypted in your browser using SEAL technology. We (the platform) never see your raw data. |
| **☁️ Decentralized Storage**  | Encrypted data blobs are stored on **Walrus**, ensuring high availability and censorship resistance.  |
| **💎 NFT Access Control**     | Buying a dataset mints a unique NFT. This NFT is your key to decrypt and download the file.           |
| **🤝 Trustless Verification** | Decryption is only authorized after on-chain verification of your purchase.                           |

**🔗 Quick Links**

| Resource                                                                                                                         | Description                        |
| -------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- |
| [**Live App** ](https://capydata.wal.app/)                                                                                       | The official marketplace interface |
| [**GitHub** ](https://github.com/khoanna/decentralized-data-marketplace)                                                         | Open source repositories           |
| [**Contract** ](https://suiscan.xyz/testnet/object/0xf6417d0eb9778dfbde6955aae22572bc0ef135a9e78149e53be137adb74efe17/contracts) | Verified Move Modules              |

**Note:** CapyData is currently live on **Sui Testnet** and **Walrus Testnet**. Please use the faucet to get test tokens before trading.<br>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://capydata.gitbook.io/capydata-docs/welcome-to-capydata.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 `build a script that syncs our docs to a CMS` 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.