# Build Read-Only Features

Build read-only Autonomi features when you only need to retrieve data that has already been stored and paid for.

This guide compares the SDK, CLI, and direct Rust ways to build read-only retrieval features so you can choose the right read-only architecture for your application.

## Why this matters

Read-only features are simpler than upload-enabled ones.

If your application only reads data that has already been written to the network:

* you do not need ANT
* you do not need gas
* you do not need a wallet
* you do not need upload permissions

That can make retrieval-only tools, dashboards, content browsers, and other read-heavy features much easier to build and operate.

## Prerequisites

* A known public address to retrieve, or a `DataMap` for private data
* One of these routes:
  * SDKs through `antd`
  * the `ant` CLI
  * native Rust with `ant-core`

If you do not already have an address or `DataMap`, create one first by following [Store and Retrieve Data with the SDKs](/developers/sdk/install/how-to-guides/store-and-retrieve-data.md) or by storing data through the CLI or direct Rust.

## Steps

### 1. Choose the interface you want to use

With the SDK:

* [Build with the SDKs](/developers/sdk/install.md)
* [Start the Local Daemon](/developers/sdk/install/start-the-local-daemon.md)
* [Retrieve Data from the Network](/developers/sdk/install/retrieve-data-from-the-network.md)

With the CLI:

* [Use the CLI](/developers/cli/use-the-cli.md)

With Direct Rust:

* [Build Directly in Rust](/developers/developing-in-rust/build-directly-in-rust.md)

### 2. Retrieve public or private data

For public data, you need a public address.

For private data, you need the `DataMap` or equivalent private retrieval material.

With the SDK, `antd` can run without `AUTONOMI_WALLET_KEY` when you only need retrieval.

Public retrieval through the daemon:

```bash
curl http://localhost:8082/v1/data/public/<address>
```

Private retrieval through the daemon:

```bash
curl "http://localhost:8082/v1/data/private?data_map=<hex_encoded_datamap>"
```

The private retrieval response is JSON with the content returned as base64 in the `data` field.

With the CLI, public and private file retrieval use `ant file download` with either a public address or a local `.datamap` file:

```bash
ant --bootstrap 1.2.3.4:12000 file download <public_address> -o downloaded.bin
ant --bootstrap 1.2.3.4:12000 file download --datamap my_data.bin.datamap -o downloaded.bin
```

For native Rust, use the retrieval APIs in `ant-core` after connecting to the network client.

### 3. Keep wallet setup out of your architecture unless you also upload

If your application only reads data that has already been stored, it does not need:

* `AUTONOMI_WALLET_KEY`
* `SECRET_KEY`
* token approvals
* upload payment flows

That means you can keep the architecture focused on retrieval and content handling instead of wallet management.

## Verify it worked

Your read-only feature is configured correctly when it can retrieve the expected content from a known public address or private `DataMap` without any wallet setup.

## Common errors

**404 Not Found**: Check the address.

**Trying to use private retrieval without a DataMap**: Private content still requires the retrieval metadata even though the content has already been paid for.

## Next steps

* [Store and Retrieve Data with the SDKs](/developers/sdk/install/how-to-guides/store-and-retrieve-data.md)
* [Payment Model](/developers/core-concepts/payment-model.md)
* [Use the CLI](/developers/cli/use-the-cli.md)


---

# Agent Instructions: 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:

```
GET https://docs.autonomi.com/developers/guides/build-read-only-features.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.