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

# Guides

- [Configuration](https://docs.zama.org/protocol/sdk/guides/configuration.md): How to configure the SDK with createConfig — chains, relayers, provider, signer, and storage.
- [Authentication](https://docs.zama.org/protocol/sdk/guides/authentication.md): How to authenticate with the relayer using a backend proxy or a direct API key.
- [Relayer API keys](https://docs.zama.org/protocol/sdk/guides/relayer-api-keys.md): How to obtain, configure, and securely manage your Zama Relayer API key.
- [Shield tokens](https://docs.zama.org/protocol/sdk/guides/shield-tokens.md): How to convert public ERC-20 tokens into their confidential form.
- [Transfer privately](https://docs.zama.org/protocol/sdk/guides/transfer-privately.md): How to send confidential tokens so the amount stays hidden on-chain.
- [Unshield tokens](https://docs.zama.org/protocol/sdk/guides/unshield-tokens.md): Convert confidential tokens back to public ERC-20 by unshielding them.
- [Check balances](https://docs.zama.org/protocol/sdk/guides/check-balances.md): Decrypt and read confidential token balances using the SDK and React hooks.
- [Decrypt values from event logs](https://docs.zama.org/protocol/sdk/guides/decrypt-from-event-logs.md): Decrypt an FHE encrypted value pulled straight off an event log — the common server-side pattern for indexers, wallet history, and bridges.
- [Handle errors](https://docs.zama.org/protocol/sdk/guides/handle-errors.md): Catch, match, and recover from SDK errors in your application.
- [Node.js backend](https://docs.zama.org/protocol/sdk/guides/node-js-backend.md): How to use the SDK in a Node.js server environment with worker threads and per-request isolation.
- [Web extensions](https://docs.zama.org/protocol/sdk/guides/web-extensions.md): How to use the SDK in MV3 Chrome extensions with persistent permit storage.
- [Local development](https://docs.zama.org/protocol/sdk/guides/local-development.md): How to use the cleartext relayer for local Hardhat nodes and custom chain deployments without a KMS or gateway.
- [Next.js SSR](https://docs.zama.org/protocol/sdk/guides/nextjs-ssr.md): How to use the SDK with Next.js and server-side rendering frameworks.
- [Operator approvals](https://docs.zama.org/protocol/sdk/guides/operator-approvals.md): How to approve another address to act on your confidential tokens.
- [Delegated decryption](https://docs.zama.org/protocol/sdk/guides/delegated-decryption.md): Grant another address the right to decrypt confidential balances, then read those balances as a delegate.
- [Encrypt & decrypt](https://docs.zama.org/protocol/sdk/guides/encrypt-decrypt.md): How to encrypt values and decrypt FHE encrypted values for custom confidential smart contracts that are not wrapped ERC-20 tokens.


---

# 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://docs.zama.org/protocol/sdk/guides.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.