> ## Documentation Index
> Fetch the complete documentation index at: https://docs.handcash.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting started

> Start building against the HandCash BRC wallet (beta) — Desktop / Mobile, not Connect or WaaS

<Warning>
  **Beta — BRC wallet only.** These steps apply to apps that integrate with **HandCash Desktop or Mobile** over [BRC-100](https://brc.dev/100). They do **not** apply to Connect (`authToken` + `@handcash/sdk`) or Wallet API (`/v1/waas/*`).
</Warning>

## Prerequisites

1. **HandCash Desktop** (or Mobile) installed and unlocked with a funded wallet.
2. A web or native app that can reach the local BRC-100 bridge (Desktop) or a conforming wallet client.
3. Familiarity with BRC-100 method names (`createAction`, `listOutputs`, `internalizeAction`, …) from [brc.dev/100](https://brc.dev/100).

## Choose the right HandCash surface

| You need…                                                  | Use                                              |
| ---------------------------------------------------------- | ------------------------------------------------ |
| Existing HandCash **cloud** users authorize your app       | [Connect](/v3/getting-started)                   |
| Embedded wallets you create for **your** users (email)     | [Wallet API (WaaS)](/wallet-api/getting-started) |
| Talk to the user’s **self-custodial BRC wallet** on device | **This section (BRC wallet)**                    |

## First connection (Desktop)

On Desktop, HandCash runs a **local bridge** on loopback so apps can call BRC-100 methods with user permission:

* Primary: `https://127.0.0.1:2121`
* Fallback: `http://127.0.0.1:3321`

See **[Local bridge](/brc-wallet/local-bridge)** for discovery, origins,
permissions, structured errors, and TLS fallback.

Typical first call after the user has unlocked the wallet and approved your origin:

1. Discover the bridge with `POST /getVersion`.
2. Check `isAuthenticated`; call `waitForAuthentication` when needed.
3. Call wallet methods (e.g. balance via `getBalance`, payments via `createAction`).

Exact JSON shapes follow BRC-100; HandCash’s permission UI gates origins and method scopes.

You can also open [App Lab](https://brc-cloud.bcryderman.workers.dev/app-lab) with Desktop unlocked and run each method from the browser.

## Choose an interaction

| You want to…                                                          | Page                                              |
| --------------------------------------------------------------------- | ------------------------------------------------- |
| Connect, read balance, send BSV, stage or sign, receive, list history | [Payments and actions](/brc-wallet/payments)      |
| Read inventory, mint, transfer, or receive 1Sat items                 | [Collectables](/brc-wallet/items)                 |
| Read balances, mint, transfer, or receive BSV-21 tokens               | [Tokens](/brc-wallet/tokens)                      |
| Derive keys, sign, encrypt, or handle certificates                    | [Signing and encryption](/brc-wallet/signing)     |
| Understand prompts, grants, scoped baskets, and error codes           | [Permissions and scopes](/brc-wallet/permissions) |
| See every method and its permission level                             | [Wallet interactions](/brc-wallet/interactions)   |

<Note>
  Mobile uses the same wallet core, but the loopback HTTP URLs on this page are a
  Desktop transport. Mobile app/deep-link transport is not yet a public contract.
</Note>

## Next

* **[Payments and actions](/brc-wallet/payments)** — the first calls most apps make
* **[Wallet interactions](/brc-wallet/interactions)** — complete capability and permission map
* **[Local bridge](/brc-wallet/local-bridge)** — ports, origins, and connecting from a web app
* **[Overview](/brc-wallet/overview)** — how this section relates to Connect and WaaS