# DamageBDD Accounts and Access

Use the application dashboard for signup and authentication, then check account, wallet and API permissions.

Canonical HTML: <https://damagebdd.com/accounts.html>



<a id="create-or-access-an-account"></a>

## Create or access an account

Open the [DamageBDD dashboard](https://run.damagebdd.com) and use the signup or
login methods offered by that deployment. Complete any verification required
there. The static documentation site does not create accounts, accept
credentials, request wallet signatures or generate invoices.


<a id="check-the-account-and-wallet-arrangement"></a>

## Check the account and wallet arrangement

The hosted account documentation describes a custodial Aeternity wallet.
External-wallet and Nostr identity integrations have separate permissions;
their presence in the wider stack does not mean every login method is enabled
on every dashboard. Confirm who controls the keys and what a signature or
wallet connection authorises.

Review the [service terms](tac.md), [token terms](token_tos.md) and
[payment/custody boundaries](payments.md) for the flow you intend to use.


<a id="use-the-api"></a>

## Use the API

For Python clients and automated agents, follow the
[keypair and Python testing quickstart](python-quickstart.md) for local
key generation, hosted authentication, funding and execution settlement.

The [manual](manual.md) explains how to obtain and use an `AUTH_TOKEN`.
Treat API credentials as secrets and grant access only to the required service.
The [usage guide](use.md) links the API reference and self-hosting path.