BroLabel is an API-first crypto infrastructure platform for crypto exchanges, neobanks, and fintech companies, offering embedded MPC wallets (BroSettlement), card issuing (BroCard), and a non-custodial wallet (BroWallet).

How many blockchains does BroSettlement support?

BroSettlement supports 10 blockchains including Ethereum, Bitcoin, TRON, BNB Chain, and Solana, with 8 assets supported in the current release.

Is BroLabel a Fireblocks alternative?

Yes. BroLabel is an API-first alternative to Fireblocks, Dfns, Utila, Blockdaemon, and Safeheron for companies that need embedded MPC custody with white-label integration.

How quickly can BroLabel be integrated?

A typical BroLabel integration takes 2 to 4 weeks. A developer sandbox is available with REST API and WebSocket documentation.

Security

API authentication

BroSettlement API authentication uses asymmetric Ed25519 keys. Your backend signs each request with a private key, and BroSettlement verifies it with the registered public key.

Required headers

Header	Description
`X-Bro-Api-Key`	API key identifier
`X-Bro-Timestamp`	ISO 8601 timestamp for replay protection
`X-Bro-Nonce`	Unique value per request
`X-Bro-Signature`	Base64-encoded Ed25519 signature

Signature payload

Build the signature payload from the request method, path, timestamp, nonce, and body hash.

text

METHOD
/v1/wallets
2026-06-25T09:00:00Z
8f7b8f24-4e6a-45d2-a944-4b11c4c7d2f8
sha256_body_hash

Security controls

Use Ed25519 key pairs for API authentication.
Store private keys in a secrets manager or HSM-backed service.
Rotate keys when access ownership changes.
Enable IP whitelisting for production API keys.
Enforce unique nonces for replay protection.
Keep timestamps within the accepted request window.
Use mandatory 2FA for all human users.

Example request

bash

curl https://api.brosettlement.com/v1/wallets \
  -H "X-Bro-Api-Key: api_key_123" \
  -H "X-Bro-Timestamp: 2026-06-25T09:00:00Z" \
  -H "X-Bro-Nonce: 8f7b8f24-4e6a-45d2-a944-4b11c4c7d2f8" \
  -H "X-Bro-Signature: base64_ed25519_signature" \
  -H "Content-Type: application/json" \
  -d '{"organizationId":"org_123","chain":"ETH","label":"Treasury wallet"}'

Common failures

Error	Cause	Fix
`invalid_signature`	Signature does not match the canonical request	Rebuild the payload and verify body hashing
`expired_timestamp`	Request timestamp is outside the allowed window	Sync server time with NTP
`duplicate_nonce`	Nonce was already used	Generate a unique nonce for each request
`ip_not_allowed`	Request came from an unlisted IP	Update the API key IP whitelist