# BroSettlement public documentation

> BroSettlement is API-first embedded MPC wallet, ledger, and settlement infrastructure for stablecoin-heavy B2B products.

Canonical documentation: https://www.brolabel.io/en/api-reference/brosettlement
API overview: https://www.brolabel.io/en/api-reference/api-overview
API conventions: https://www.brolabel.io/en/api-reference/api-conventions
Create a transaction: https://www.brolabel.io/en/api-reference/create-transaction
Disaster recovery: https://www.brolabel.io/en/api-reference/disaster-recovery
WebSocket events: https://www.brolabel.io/en/api-reference/events
Product: https://www.brolabel.io/en/brosettlement
Contact: https://www.brolabel.io/en/contact
Agent skills: https://www.brolabel.io/en/api-reference/agent-skills
Digital asset custody report (EN): https://www.brolabel.io/en/reports/digital-asset-custody-infrastructure-report-2026
Звіт про зберігання цифрових активів (UK): https://www.brolabel.io/uk/reports/digital-asset-custody-infrastructure-report-2026

## Agent skills

- BroSettlement Agent Skills repository: https://github.com/BroLabel/brosettlement-agent-skills

The public repository contains the `brosettlement-onboarding`, `brosettlement-api`, and `brosettlement-disaster-recovery` skill folders. Install all three as sibling directories. Onboarding delegates signed API calls, current Swagger inspection, and remote status verification to the API skill. Disaster Recovery provides a separate client-controlled Share B + Share C break-glass workflow for one native TRX or standard TRC-20 transfer. Its optional token-contract parameter selects TRC-20; otherwise it uses native TRX. It does not use BroSettlement API or Console.

Independent B+C recovery is intended for every blockchain supported by BroSettlement. The currently public recovery tooling covers native TRX and standard TRC-20 transfers on TRON mainnet or Nile. Asset-access recovery does not automatically restore the BroSettlement API, operating journal, event stream, or a client application.

## Product boundary

BroSettlement provides embedded wallets, DKG-generated 2-of-3 MPC signing with a client-run Co-Signer, transaction lifecycle events, blockchain broadcast and observation, and an append-only ledger for reconciliation.

It is not an OTC desk, exchange, consumer wallet, fiat rail, KYC/KYB provider, Travel Rule provider, or fully managed custodian. Clients own their product experience, business logic, regulatory analysis, compliance stack, fiat integrations, and client-side signing policy.

## Billing and trial month

Paid BroSettlement plans require no upfront payment and use monthly postpayment. If a customer continues after the first month, that first month is payable after it ends under the selected plan. Subsequent monthly payments also cover the preceding period.

If a customer cancels within the first month, payment for that period is not required at that point. Resuming use of the same account later requires payment for the previous unpaid period. Do not describe this as an unconditionally free first month. The Free plan remains a separate no-cost testnet plan.

Current plans and trial terms: https://www.brolabel.io/en/brosettlement#trial-terms

## Integration model

1. Create an organization and least-privilege service account.
2. Register an Ed25519 public key; keep the private key secret.
3. Sign requests with an API key ID, timestamp, unique nonce, and Ed25519 signature.
4. Create organization-scoped wallets or deposit addresses.
5. Consume lifecycle events idempotently.
6. Run a client-controlled Co-Signer for withdrawal signing policy.
7. Reconcile operational events against immutable ledger entries.

## Current API contract

- Production Swagger UI (default): https://brosettlement-api.brolabel.io/swagger-integration
- Production OpenAPI JSON: https://brosettlement-api.brolabel.io/swagger-integration-json
- API version: 1.0
- Production REST prefix (default): https://brosettlement-api.brolabel.io/api/v1
- Production WebSocket: wss://brosettlement-api.brolabel.io/v1/ws

The public API reference documents Assets, Ledger Accounts, Wallets, Balances, Transactions, MPC, MPC Co-Signer, Audit Logs, authentication, pagination, idempotency, errors, and WebSocket connectivity.

## Availability notice

Endpoint names, payloads, scopes, and error models follow the current [Swagger documentation](https://brosettlement-api.brolabel.io/swagger-integration). Confirm networks, limits, SLAs, pricing, and credentials before launch.