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

# Account access

> Confirm the active account, understand what it lets you do, and switch only to accounts your credential can reach.

The v3 tool list is resolved from the active account. Start every session with `get_status` and keep
what it returns: the account, your role, readiness, blockers and the accounts you can reach.

## What get\_status tells you

| Field                            | Use it to                                                                      |
| -------------------------------- | ------------------------------------------------------------------------------ |
| `account`                        | Know which account you act in: `customerId`, name, account type and your role. |
| `role`                           | See whether you have buyer, seller or organization tools.                      |
| `readiness`, `blockers`          | Learn what must be finished before buying or selling works.                    |
| `nextActions`                    | Pick the next step; many name the tool to call.                                |
| `reachableAccounts`              | See every other account this credential may switch to.                         |
| `canBuyAnywhere`, `destinations` | Check whether the account can transact and with how many ready sellers.        |

## Switching accounts

Switch only to a `customerId` that `get_status` returned:

```json switch_account theme={null}
{ "customerId": 1042 }
```

Pass `"home"` to return to the credential's home account. After a switch:

1. process the `notifications/tools/list_changed` notification and fetch `tools/list` again;
2. call `get_status` again to confirm which account is now active.

A person with both a buyer and a seller account (for example **Wrenfield Coffee Co. · Buyer** and
**Larkstone Media · Storefront**) moves between them the same way the account selector in the app does.

## What access does and does not mean

* **Every authenticated buyer and seller account can connect.** Individual tools still need the right
  role and permissions.
* **Seeing a tool is not permission to use it.** A write can still return `FORBIDDEN` for your role.
* **Organization accounts** hold members and billing. They offer navigation and shared tools, not the
  buyer or seller catalogs.
* **A connection is not access to every advertiser.** A seller relationship, an API key or a
  registered agent never implies access to advertisers you have not been granted.

<Tip>
  Store the active `customerId` with every checkpoint your application saves, and check it again
  when you resume. Resuming work in the wrong account is the most common integration bug.
</Tip>