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

# Authentication

> How Bloom API keys work — format, limits, and revocation.

The Bloom API uses Bearer-token authentication. Pass your key on every request:

```
Authorization: Bearer blm_sol_live_<key-body>
```

## Key format

Keys take the form `blm_<chain>_live_<base58-random>`, for example:

```
blm_sol_live_5KJp9c2xQ7AHvRLFB3qrTn8mWdUksyPqE6hJzXvCdNj
```

* `blm_sol_live_` — Solana key prefix. EVM keys use the `blm_<chain>_live_`
  prefix for the relevant chain.
* The dashboard only ever displays a masked form such as `blm_sol_live_…wXyz`
  (the last four characters of the key body).

<Warning>
  Your key is shown **once only**, at creation time, and is not stored in
  plaintext. Copy it immediately. If you lose it, revoke it and create a new one.
</Warning>

## Limits and revocation

* You may have up to **5 active keys per chain**. Revoked keys do not count
  toward this limit.
* Revoke a key at any time from **Manage API Keys** in Bloom Manager.

## Account and wallet binding

Keys are bound to your Bloom account. Every wallet address referenced in a
request must belong to that account, or the request is rejected with
`WALLET_NOT_OWNED` (`400`). Requests are rate-limited **per user** — all of your
keys share one budget.