Start in your Braith account.
The same public prompt works for everyone. Your coding tool runs braith connect; you approve the matching code in your Braith account. Credentials are sent separately to that tool.
Pro is £59/month total. Free is available without a card. Connecting does not activate paid billing.
One supported setup workflow.
The published packages are braith and @braith/sdk. Follow the public setup instructions.
npm install @braith/sdk@0.2.0
npx braith@0.3.0 connect
# Instrument your app and review the changes.
npx braith@0.3.0 validate
npx braith@0.3.0 push
npx braith@0.3.0 test
npx braith@0.3.0 release <build-id>Read the generated .braith/SETUP.md and replace the sample configuration with a static app context catalogue and supported activity capture in review mode. Predefined core outcomes are extra context. Renew expired setup access with connect. The temporary management key expires after 30 minutes.
Review before publishing and binding a release. Use the same build ID in the SDK. Use release default explicitly only when build IDs are unavailable. Deploy through your normal process, then verify real production events.
Keep credentials and evidence in the right place.
Use the server SDK for authoritative payment, entitlement and persisted-state events. Browser signals cannot prove a payment. Pass one attempt ID through each task and keep server and management keys out of browser code.
The CLI stores setup credentials in an ignored local file. Never print or commit them. Do not send private form contents, emails, access tokens or full webhook payloads to Braith.
Choose a result your app can observe. A success message or a missing event alone does not establish the customer’s result.
Read the API before calling it.
Download the OpenAPI 3.1 specification for enrollment, manifest publishing, release binding, event ingestion and isolated integration checks. These document existing authenticated endpoints; they do not expose private customer data.
Read per-event results, not just the HTTP status. Correct invalid requests, stop on expired credentials, respect rate limits and use bounded retries. Do not repeat integration tests in an unbounded loop or let telemetry block a customer action.
No public MCP server or incident-reading API is currently offered. Billing, deletion and key rotation remain customer-controlled account actions.
Report what actually worked.
Separate local code changes, validation, manifest publishing, release binding, isolated tests and real production events. A passing integration test is not proof that the deployed app is connected.
For a compact machine-readable reference, use the Markdown guide and documentation index. For a worked SDK call, see Next.js setup.