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

# RPC API

The node exposes public read endpoints and selected write endpoints.

## Common Read Endpoints

```
GET /health
GET /chain/height
GET /mempool/size
GET /blocks/:height
GET /blocks/:height/raw
GET /blocks/hash/:hash
GET /blocks/latest
GET /blocks/:height/transactions
GET /blocks/:height/private_tx_hashes
GET /blocks/range/:from/:to
GET /blocks/range/:from/:to/raw
GET /blocks/range/:from/:to/private_tx_hashes
GET /transactions/:hash
GET /private/tx/:hash
```

## Transaction Submission

```
POST /private/tx
POST /transactions
```

Wallets should submit locally built transaction payloads. Public RPC endpoints must not receive wallet seed phrases, scan keys, or spend keys.

## Explorer Use

The public explorer can use read endpoints for block height, latest blocks, block details, transaction hashes, mempool size, private transaction hashes, and private transaction body availability. It should not turn wallet scan keys or addresses into public account-history pages.

## Wallet Use

Wallets may read block and private transaction data to reconstruct local wallet state. Ownership detection happens in the wallet with local account material, not by asking an RPC server to reveal a user's balance.

## CLI Helpers

```sh
zoka rpc-list --network mainnet
zoka rpc-status --network mainnet
zoka rpc-height --network mainnet
zoka rpc-sync --network mainnet --limit 512
```


---

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

```
GET https://zokanetwork.gitbook.io/zokanetwork/developers/rpc-api.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.