← Protocols
Copper
Custody·Multi-chain · EVM · Bitcoin

Copper

01Description

Institutional digital-asset custody and prime-services platform best known for ClearLoop — an off-exchange settlement network that delegates collateral to integrated exchanges without funds leaving Copper's custody.

02Best for
  • 01off-exchange settlement (ClearLoop)
  • 02institutional cold/warm custody
  • 03hedge-fund and asset-manager workflows
  • 04MPC-secured multi-venue trading
  • 05EU/UK regulated custody
04Environment variables
VariableScopeDescription
COPPER_API_KEYServerCopper API key issued per organization from the Prime portal.
COPPER_API_SECRETServerHMAC-SHA256 secret used to sign each request; never exposed to the client.
COPPER_BASE_URLServer`https://api.copper.co` for production or the sandbox host issued for your tenant.
05Prompt snippet
Use Copper for institutional custody and ClearLoop off-exchange settlement. There is no public client SDK — call the REST API directly with `Authorization`, `X-Timestamp`, and `X-Signature` headers where the signature is HMAC-SHA256 over `timestamp + method + path + body`. Key endpoints: `POST /platform/portfolios/{id}/accounts/{id}/transactions` to initiate withdrawals, `POST /platform/clearloop/delegations` to delegate collateral to an integrated exchange, `POST /platform/clearloop/recalls` to recall, and `GET /platform/portfolios` to enumerate vaults. ClearLoop delegations require an active venue connection and counterparty agreement before they will be accepted.
06Gotchas
  • ClearLoop delegations require pre-onboarded exchange connections and a tri-party agreement — you cannot delegate to an arbitrary venue at runtime.
  • Withdrawals are constrained to whitelisted destinations governed by a quorum approval policy; adding a new address is an out-of-band operation, not an API call.
  • Some Copper services are limited by jurisdiction (e.g., Copper Securities is FCA-regulated in the UK; certain US persons are restricted) — gate availability per client domicile.
  • API requests use HMAC signatures with strict timestamp tolerance; serverless cold-starts with skewed clocks will produce intermittent 401s.
  • Sandbox and production are isolated tenants — portfolio IDs, account IDs, and ClearLoop venue IDs are not portable between them.
  • Copper is closed-source: no public GitHub SDK; treat the OpenAPI spec as the source of truth and pin a generated client per release.
07Alternatives