Documentation Index
Fetch the complete documentation index at: https://developer.bron.org/llms.txt
Use this file to discover all available pages before exploring further.
Install
Install directly from the GitHub repository:requirements.txt:
Authenticate
Need a JWK keypair? Install the Bron CLI and run
bron config init --name default --workspace <workspaceId> --key-file ~/.config/bron/keys/me.jwk --generate-key — it generates the JWK, stores it at 0600, prints the public half to paste into the Bron UI, and registers the profile. Same key file works directly with the SDK via BRON_API_KEY_FILE.Authorization: ApiKey <jwt>. No token caching, no revocation flow.
Quickstart
All public API methods are async — useawait (or asyncio.run(...)) and close with await client.aclose().
Subscriptions (WebSocket)
Live subscriptions are not yet exposed in the Python SDK; they are available today in the Golang SDK and will land here in a subsequent release. The wire protocol is identical (a subscription is “GET extended” — same query, server replays the historical match then streams live updates of the same response shape).Errors
Non-2xx responses raise aBronAPIError whose attributes mirror the API envelope (code, trace, details):
e.code (stable identifier) — never on the human message. Quote e.trace in any user-facing report.
Configuration
TheBronClient constructor accepts:
api_key— private JWK as a JSON string (required).workspace_id— workspace ID (required).base_url— API base URL (defaults tohttps://api.bron.org).proxy—http://[user:pass@]host:portfor outbound requests through a corporate proxy. StandardHTTPS_PROXY/HTTP_PROXYenv vars are honored too.
Where to next
API reference
Endpoints, request/response shapes, OpenAPI spec.
CLI overview
bron binary — same auth, same data path, no client code.Errors & exit codes
Error envelope shape, stable codes, retry strategy.
Authentication & profiles
Keypair lifecycle, env-var overrides, proxy setup, rotation.
