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

# Set up your account

> From first sign-in to a configured test environment.

This page walks through the dashboard end-to-end — what's auto-provisioned, where to find things, and the manual steps you need to run before you can ship code against Tally.

If you just want to make your first payment as fast as possible, the [Quickstart](/quickstart) is a more compressed path.

## 1. Sign in

Go to [tallyforagents.com/login](https://www.tallyforagents.com/login). Authentication is handled by Privy — you can use a passkey, email, or whatever auth method we have enabled.

On first sign-in, Tally auto-provisions:

* A **Tally account** named after your email (you can rename later from the dashboard).
* An ownership membership tying you to the account.
* A single test-mode **wallet** on Base Sepolia, called "Main Wallet."

You'll land on `/{your-slug}/overview`. The slug is derived from your account name and stays stable.

## 2. Tour the dashboard

The sidebar is the canonical navigation. Every page lives at `/{slug}/{tab}`.

| Tab              | What's there                                                                                   |
| ---------------- | ---------------------------------------------------------------------------------------------- |
| **Overview**     | Balance chart, top wallets, top agents, recent activity. Your operational at-a-glance.         |
| **Wallets**      | The wallets in your account. Detail pages show balances, grants, recent transactions.          |
| **Agents**       | Every registered agent. Detail pages show grants, recent activity, permission history.         |
| **Transactions** | Every payment — outbound and inbound — with filters by status, direction, agent, and search.   |
| **Webhooks**     | Endpoints subscribed to events from this account. Detail pages show delivery logs with replay. |
| **API keys**     | Active keys with rotation and revoke affordances. Test and live keys are separate.             |

The **mode badge** in the sidebar shows whether you're viewing test-mode or live-mode resources. Today every session is in test mode — see [Test mode and live mode](/test-mode).

## 3. Fund your test wallet

Until your wallet has USDC, nothing useful happens. Get testnet USDC from [Circle's faucet](https://faucet.circle.com):

1. Copy your Main Wallet's address from the dashboard (Wallets → Main Wallet → copy address).
2. Paste it into the faucet, select **Base Sepolia**, request USDC.
3. Refresh the wallet detail page. Balance updates within seconds.

The inbound watcher runs on every dashboard load, so anything sent to the wallet gets attributed automatically.

## 4. Create an API key

API keys authenticate your server to Tally. From **API keys → New key**:

1. Confirm you're in test mode (sidebar badge).
2. Click **New key**. Copy the key — `tly_test_…` — exactly once. We don't show it again.
3. Store it in your secret manager. For local development, `.env.local` is fine:

   ```bash theme={null}
   TALLY_API_KEY=tly_test_…
   ```

The key is account-scoped and mode-scoped. A `tly_test_` key can only see test-mode resources; same for live.

When you eventually need to rotate the key, the dashboard has a **Rotate** action that mints a new key while keeping the old one valid for 24 hours, so your fleet can roll over without downtime. See [API keys](/api-keys) for the full lifecycle.

## 5. (Optional) Set up a webhook endpoint

If you're building anything that reacts to payments confirming or USDC arriving, register a webhook now so the wire-up is tested before you need it in anger.

From **Webhooks → New endpoint**:

1. Enter the URL events should POST to. For local development, use [ngrok](https://ngrok.com) or similar to expose a local server.
2. Pick the events you want. Start with `payment.confirmed` and `payment.failed` if you're not sure.
3. Copy the **signing secret** (`whsec_test_…`) — also shown exactly once.

See [Webhooks](/webhooks) for the signature verification pattern, retry semantics, and the SDK helper.

## 6. (Optional) Invite team members

If you're not working solo, **Account settings → Members** lets you invite collaborators with one of four roles:

* `owner` — full access.
* `admin` — full access except ownership transfer and account closure.
* `developer` — manage API keys, agents, and webhooks.
* `viewer` — read-only.

See [Accounts](/accounts) for what each role can do.

## You're done

After steps 1-4 you can write code against Tally. After 5 you can react to events. After 6 you can collaborate.

Where to go next:

* [Quickstart](/quickstart) — first payment in code.
* [How Tally works](/overview) — the mental model, end to end.
* [Concepts](/wallets) — deep dives, starting with Wallets.