Skip to content
BRON

Public information

Developer documentation

Build integrations and agents against BRON's litigation record without losing the access, provenance, and human-approval boundaries that make the record trustworthy.

Last updated August 29, 2026.

Choose a surface

  • Public API reference covers authentication, scopes, rate limits, REST endpoints, webhooks, and graph synchronization.
  • Verified MCP substrate covers the attested read contract, the available tools, and the human-gated proposal boundary for outside agents.

Start with the credential boundary

A BRON API key acts as its owner and can reach attorney-grade material unless it was minted in the narrower client-safe class. Treat every key like a password, grant the least scope required, and use a matter allow-list whenever an integration should be confined to one engagement.

Machine-readable API shape

A deployment publishes its OpenAPI description at GET /api/v1/openapi.json. It describes request and response shapes without exposing firm data; the human-readable reference explains the authorization and failure semantics around those shapes.