> For the complete documentation index, see [llms.txt](https://docs.useshadowpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.useshadowpay.com/api-reference/accounts-and-balances.md).

# Accounts & Balances

Endpoints for reading account details and balances for the authenticated ShadowPay account.

***

## Get the authenticated account

```
GET /v1/accounts/me
```

### Response

```json
{
  "account_id": "acct_8f2b1c",
  "handle": "@yourname",
  "type": "personal",
  "public_key": "8f2b1cXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
  "kyc_status": "verified",
  "created_at": "2026-01-14T09:00:00Z"
}
```

| Field        | Type     | Description                                        |
| ------------ | -------- | -------------------------------------------------- |
| `account_id` | `string` | ShadowPay's internal account identifier            |
| `handle`     | `string` | The account's `@handle`                            |
| `type`       | `string` | `personal`, `business`, or `agent`                 |
| `public_key` | `string` | The account's Solana address                       |
| `kyc_status` | `string` | `unverified`, `pending`, `verified`, or `enhanced` |
| `created_at` | `string` | ISO 8601 timestamp                                 |

***

## Get balances

```
GET /v1/accounts/me/balances
```

Returns your decrypted balance for each held asset. This endpoint requires your request to include a client-side decryption proof, since ShadowPay's servers cannot decrypt your balance themselves.

### Request

```json
{
  "decryption_proof": "base64-encoded proof generated client-side"
}
```

### Response

```json
{
  "balances": [
    { "asset": "USDC", "amount": "1245.30" },
    { "asset": "SOL", "amount": "0.42" }
  ]
}
```

If no `decryption_proof` is supplied, the endpoint returns only whether the account holds a non-zero balance per asset, without an amount, since ShadowPay cannot read the encrypted value itself.

***

## List agent accounts

```
GET /v1/accounts/me/agents
```

Returns every agent account namespaced under the authenticated account.

### Response

```json
{
  "agents": [
    {
      "account_id": "acct_9d3a2f",
      "handle": "@yourname/research-bot",
      "public_key": "9d3a2fXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
      "status": "active",
      "spend_policy_id": "policy_4471"
    }
  ]
}
```

See [Agents & Spend Policies](/api-reference/agents-and-spend-policies.md) to create, update, or inspect an agent's spend policy.

***

## Error responses

| Status | Code                       | Description                                                               |
| ------ | -------------------------- | ------------------------------------------------------------------------- |
| `401`  | `unauthorized`             | Missing or invalid API key                                                |
| `403`  | `kyc_required`             | Account has not completed required identity verification                  |
| `422`  | `decryption_proof_invalid` | Supplied decryption proof does not match the account's balance ciphertext |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.useshadowpay.com/api-reference/accounts-and-balances.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.