---
title: "Get a policy-gated account deposit address"
method: GET
path: "/accounts/{id}/deposit-address"
tags: ["agent"]
---

# Get a policy-gated account deposit address

`GET /accounts/{id}/deposit-address`

## Request

- Base URL: `https://api.catena.com/v1/agent-api`
- URL: `https://api.catena.com/v1/agent-api/accounts/{id}/deposit-address`
- Auth: HTTP bearer

## Path parameters

- `id` string, required

## Query parameters

- `network` 'base' | 'arc' | 'tempo', required
- `asset` string, required

## Response `200`

Account deposit address

- object
  - `accountId` string, required
  - `address` string, required
  - `liquidationAddressId` string
  - `source` 'wallet' | 'liquidation', required

## Other responses

- `400`: Missing or unsupported network or asset
- `403`: Account not accessible under this policy
- `404`: Readable account not found
- `409`: Catena has closed the network to new work (`onchain_network_closed`), including addresses already issued on it. The closure has no known end and sends no `Retry-After`: do not retry on this network. `details.network` names it, and `details.alternatives` lists the account's open networks to ask for instead, empty when there are none. Also refused when the agent's policy cannot be read (`policy_unreadable`) until an admin saves its full configuration or, for a temporary override, revokes it and grants a new one; nothing changed, and GET /policy shows it with `invalidReason`
- `503`: Banking services are temporarily unavailable (`temporarily_unavailable`, with the service in `details`), or the banking provider did not answer (`temporarily_unavailable` without `details`). An address already created is still returned; send the request again after the `Retry-After` seconds

---

[API](https://skmtc.dev/catena/apis/catena-agent-api.md) - [All operations](https://skmtc.dev/catena/apis/catena-agent-api/llms.txt) - [OpenAPI document](https://skmtc.dev/catena/apis/catena-agent-api/revisions/9b72e32d21f1?raw)