Complete institutional onboarding with Anchorage Digital; receive API credentials (client_id, client_secret or mTLS certificate) through the secure provisioning process
Authenticate: POST to the Anchorage auth endpoint with your credentials to receive an access token; Anchorage uses mutual TLS (mTLS) for production API access — configure client certificates on your HTTP client
Retrieve available vaults and accounts: GET /v2/accounts to enumerate your institution's account structure and capture account_id values
Generate a deposit address: POST /v2/accounts/{account_id}/addresses with {"asset_type": "<ASSET>", "network": "<NETWORK>"} to create a receiving address for the specified asset
Initiate an external transfer: POST /v2/transfers with {"source_account_id": "<id>", "destination_address": "<address>", "asset_type": "BTC", "quantity": "<amount>"} and capture transfer_id
Poll GET /v2/transfers/{transfer_id} until status is COMPLETED; Anchorage applies internal compliance and quorum approval checks before signing — monitor for PENDING_APPROVAL status which requires human action
Known gotchas
Anchorage is a federally chartered digital asset bank (OCC charter); all API integrations require signed legal agreements and compliance review — access is not self-serve
Anchorage applies multi-person authorization (quorum) to large transfers; the API will return PENDING_QUORUM_APPROVAL for transactions above institution-configured thresholds, with no programmatic approval path — designated signers must act via the Anchorage portal
Anchorage's External Transfer API was announced specifically for DeFi protocol payments; general custody withdrawal flows may use different endpoint structures — confirm with Anchorage technical support during integration
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp