BroLabel is API-first crypto infrastructure for teams launching embedded wallets, card products, fiat integrations, and operational reconciliation. BroSettlement focuses on wallet, ledger, and settlement operations.

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.

Who is BroSettlement built for?

BroSettlement is built for iGaming operators, iGaming platform providers, crypto-native teams, and crypto PSPs that need embedded wallets, payout control, WebSocket events, and reconciliation before predictable volume.

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.

Developers

Build with
BroLabel.

API-first infrastructure. Ed25519 authentication. Sandbox-ready with testnet tokens. Ship crypto products in days, not months.

Open Sandbox →Read API Docs

REST + WebSocketEd25519 authSandbox pre-fundedOpenAPI spec

api.brolabel.io · sandbox

# Create a wallet in seconds
POST  /v1/wallets
Authorization:  Ed25519 {signature}

{
  "blockchain": "ETH",
  "label": "my-first-wallet"
}

// Response 201
{
  "id": "w_9f3k2...",
  "address": "0x1a2b3c...",
  "blockchain": "ETH",
  "status": "active"
}

Quick Start

Live in 3 steps.

🔐

Generate Ed25519 key pair

Create your Ed25519 key pair in the admin console. Download the public key — BroLabel stores it, your private key never leaves your server.

# Generate key pair
openssl genpkey -algorithm ed25519 \
  -out private_key.pem
openssl pkey -in private_key.pem \
  -pubout -out public_key.pem

💼

Create your first wallet

Call POST /v1/wallets with blockchain and label. Wallet is provisioned in milliseconds — ready to receive deposits immediately.

curl -X POST \
  https://api.brolabel.io/v1/wallets \
  -H "Authorization: Ed25519 {sig}"\
  -d '{ "blockchain": "ETH" }'

⚡

Subscribe to events

Connect to the WebSocket endpoint. Receive real-time events for deposits, withdrawals, confirmations, and AML alerts — no polling required.

wss://api.brolabel.io/v1/events
// Streams in real time:
← "deposit.confirmed"  { amount, wallet_id }
← "withdrawal.completed"{ tx_hash, fee }
← "aml.flagged"       { wallet_id, reason }

Code Examples

Copy, paste, ship.

# Create a wallet
curl -X POST \
  https://api.brolabel.io/v1/wallets \
  -H "Authorization: Ed25519 {signature}" \
  -H "Content-Type: application/json"  \
  -d '{
    "blockchain": "ETH",
    "label": "user-wallet-001"
}'

API Highlights

Designed for production.

🔐

Ed25519 per-request signing

Every request signed with your Ed25519 private key — asymmetric, per-request. No shared secrets, no API keys in plaintext.

🛡️

IP whitelisting + replay protection

Lock down API access to your server IPs. Nonce-based replay protection ensures each signed request can only be used once.

⚡

REST + WebSocket

Synchronous REST for wallet and transaction operations. Real-time WebSocket for deposit confirmations, withdrawals, and AML alerts.

👤

5 RBAC roles

Owner, Admin, Operator, Reader, Service — enforce separation of duties at the API level. Map roles to your org structure.

🏖️

Sandbox with pre-funded testnet

Full sandbox environment with testnet tokens pre-loaded. Test every flow — deposits, withdrawals, fees, events — before going live.

SDKs & Tools

Everything you need to integrate.

📦

Official SDKs

Available

Python, Node.js, Go — idiomatic clients with full type safety and automatic Ed25519 signing.

📬

Postman Collection

Download

Pre-built Postman workspace with all API endpoints, example requests, and environment variables.

📄

OpenAPI Spec

Download

Full OpenAPI 3.1 specification. Auto-generate clients in any language using openapi-generator.

🔔

Webhook Testing

Sandbox

Built-in webhook tester in the sandbox console — inspect payloads, retry events, and debug your handlers.

Security First

The most secure API auth in the space.

Ed25519 asymmetric signing per request — no shared secrets, no long-lived tokens. Each request is cryptographically unique and can't be replayed.

Provider

Auth Method

Replay Protection

Shared Secrets

USBroLabel

Ed25519 asymmetric per-request

✓ Nonce-based

✓ None

Fireblocks

API key + JWT (1hr sessions)

Partial

✗ API key in headers

Utila

JWT token (hour-long sessions)

✗

✗ JWT bearer token

Safeheron

RSA + Hardware token required

✓

✗ Hardware dependency

Fystack

Shared secret HMAC

✗

✗ Shared secret

Operator proof

Operational outcomes from wallet, ledger, card, and settlement integrations.

Player wallets · payout policy · ledger

“We needed player deposit addresses, withdrawal policy, and reconciliation before our volume was predictable. BroSettlement gave us an API layer our product and finance teams could actually own.”

Wallet and card stack connected

“After a false start with outsourcing, the useful difference was operational clarity: wallet events, card controls, and the support path were all in one integration plan.”

Trading flow moved to MPC wallets

“We wanted wallet infrastructure rather than a closed custody dependency. BroLabel gave us DKG/MPC, policy controls, and event records we could fit under our trading flow.”

Get Started

Questions? Talk to an engineer.

Our integration team has shipped 40+ crypto products. Book a technical call and get answers to your specific architecture questions.

Book Technical Call Open Sandbox →

Build withBroLabel.