The first US federally-chartered crypto bank, offering institutional custody, settlement, staking, and protocol participation under OCC oversight with biometric quorum approvals and HSM-backed key infrastructure.
- 01US-regulated qualified custody
- 02bank-grade settlement
- 03institutional staking and governance
- 04tokenized RWA custody
- 05high-touch compliance / OCC oversight
| Variable | Scope | Description |
|---|---|---|
| ANCHORAGE_API_KEY | Server | Anchorage API key issued per organization; passed via the `Api-Access-Key` header. |
| ANCHORAGE_API_SECRET | Server | Ed25519 secret key (hex) used to sign each request; pairs with the API key's registered public key. |
| ANCHORAGE_BASE_URL | Server | `https://api.anchorage.com/v2` for production or `https://api.sandbox.anchorage.com/v2` for sandbox. |
Use Anchorage Digital's REST API for federally-chartered custody. Each request is authenticated with `Api-Access-Key` plus an Ed25519 signature over `timestamp + method + path + body` placed in `Api-Signature` and `Api-Timestamp`. Common endpoints: `POST /v2/transfers` to initiate a transfer (origin vault, destination address, asset, amount), `POST /v2/quotes` for trade quotes, `GET /v2/operations/{id}` to poll status, and `POST /v2/wallets/{walletId}/addresses` to allocate deposit addresses. There is no first-party JS SDK — generate a typed client from the OpenAPI spec or use the External Transfer API for high-volume automated withdrawals to allowlisted addresses.
- ⚑Withdrawals can only target trusted destinations on the organization's allowlist; adding a new address requires biometric quorum approval from authorized officers and is not API-driven.
- ⚑Operations are asynchronous and gated by quorum policy — `POST /v2/transfers` returns an operation ID that must be polled (or webhook-driven); never assume synchronous settlement.
- ⚑Each request must be signed with the organization's Ed25519 API secret; clock skew >30s or body whitespace differences will silently fail signature verification.
- ⚑Sandbox uses a separate base URL, separate API keys, and play-money assets — wallet IDs, asset IDs, and operation IDs are not portable across environments.
- ⚑As an OCC-chartered trust, Anchorage enforces KYC/KYB on the customer organization and may block specific assets or jurisdictions per its banking license; confirm asset support and travel-rule requirements before enabling withdrawals.
- ⚑There is no public client SDK — closed-source platform; integrators must maintain their own HTTP client and signature helper.