bron.org valid

Bron

Self-custodial crypto wallet powered by MPC (multi-party computation) and threshold cryptography. No seed phrases, social recovery, policy engine, and DeFi access. Built for individuals, teams, and businesses managing crypto on-chain.

For agents: Self-custodial MPC crypto wallet for individuals and businesses, with developer API docs covering authentication, API keys and rate limits.

mpc walletself-custodycrypto wallet apithreshold cryptographydefi access

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T09:31:07.501Z. Cached copy · Source on bron.org

# Bron

> Self-custodial crypto wallet powered by MPC (multi-party computation) and threshold cryptography. No seed phrases, social recovery, policy engine, and DeFi access. Built for individuals, teams, and businesses managing crypto on-chain.

Bron is a non-custodial wallet — users hold their own keys. The wallet uses CGGMP21 threshold signatures distributed across user-controlled devices, eliminating seed phrases as a single point of failure. Recovery uses social guardians instead of paper backups.

## Key pages

- [Home](https://bron.org/): product overview, features, pricing, testimonials
- [Membership](https://bron.org/membership): Personal tiers set by Qualifying Balance and Business plans, fees and feature comparison
- [Insights](https://bron.org/insights): engineering and product updates
- [FAQ](https://bron.org/faq): frequently asked questions about security, recovery, supported chains, pricing
- [Media Kit](https://bron.org/media-kit): brand assets and press materials
- [Request Demo](https://bron.org/request-demo): contact form for product demos and team onboarding

## Features

- [Impossible](https://bron.org/impossible): the problem Bron solves
- [Secure and Private by Design](https://bron.org/secure-by-design): MPC architecture, biometric signing, hidden accounts, DeFi permission safety
- [Crypto Meets Fiat](https://bron.org/crypto-meets-fiat): compliant fiat on- and off-ramps via a licensed provider
- [Cross-Chain Swap](https://bron.org/cross-chain-swap): intent-based swaps across networks
- [Digital Inheritance](https://bron.org/digital-inheritance): policy-driven succession for crypto holdings
- [Multi-Role Access and Reporting](https://bron.org/multi-role): collaborative wallets with role-based permissions, transaction history and exports
- [Earn & Stake](https://bron.org/staking): T-Bill yield via mTBILL (issued by Midas) and one-tap delegation via P2P.org validators
- [NFTs Done Right](https://bron.org/nfts-done-right): native NFT display and self-custody
- [The Wallet Agents Deserve](https://bron.org/ai-agents): self-custodial wallet for AI agents — native MCP server, CLI, and API
- [Bron for Business](https://bron.org/business): self-custodial treasury for companies — account per legal entity, role-based approvals, audit-ready reporting

## Insights articles

- [Beyond Profile Pictures: Why NFTs Are the Biggest Story in Crypto](https://bron.org/insights/20260511-nfts-beyond-pfp)
- [Real Yield: Why Crypto Staking Delivers What Government Bonds Can't](https://bron.org/insights/20260508-real-yield-staking)
- [A POA you do not recall issuing](https://bron.org/insights/20260505-poa-you-didnt-issue)
- [Why We're Open-Sourcing the MPC Behind Bron](https://bron.org/insights/20260416-open-sourcing-mpc)
- [Knowledge Is Power: Financial Clarity in a Decentralized World](https://bron.org/insights/20260328-financial-clarity)
- [Crypto is a Naked Sauna](https://bron.org/insights/20260307-crypto-naked-sauna)
- [Why DeFi Needs Its Supermar
…

Related sites

Other listed sites in Crypto and Web3. See the whole category →

Machine-readable: GET /v1/resolve?q=bron.org · GET /v1/domain/bron.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for bron.org:
1. POST https://agentwebmap.com/v1/sites/bron.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://bron.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/bron.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/bron.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.