# Braith

> Continual review of sampled web-app activity for likely customer problems, including flows without configured outcomes. Browser and Node SDKs; generic coding-agent setup; explicit customer control of billing.

Use Braith to review supported customer activity for contradictions and friction. Core configured outcomes add stronger context for important results such as paid access and usable exports. Keep an error tracker alongside it. Missing telemetry alone is not proof of failure. Capture is sampled and bounded, not automatic session replay or complete visibility into every interaction.

## Integrate
- [Coding-agent guide](https://app.braith.dev/docs/agents.md): supported CLI commands, owner-approved account linking, event trust, release binding, limits and honest verification. Read this before changing an app.
- [Generic setup prompt](https://app.braith.dev/setup.txt): identical for everyone, without a name, project ID, credential or expiry. Account linking happens separately.
- [Human-readable integration guide](https://app.braith.dev/docs/agents): the same supported workflow in the website documentation.
- [OpenAPI 3.1 specification](https://app.braith.dev/openapi.json): existing authenticated integration and ingestion endpoints; not an incident-management API.
- [Next.js guide](https://app.braith.dev/docs/nextjs): setup with the generic prompt and SDK example.
- [Published CLI](https://www.npmjs.com/package/braith): braith@0.3.0.
- [Published SDK](https://www.npmjs.com/package/@braith/sdk): @braith/sdk@0.2.0 browser and Node integration.

## Evaluate
- [How it works](https://app.braith.dev/how-it-works): result boundaries, correlation and evidence.
- [Pricing](https://app.braith.dev/pricing): Free, Starter, Pro (£59/month total), Growth; no automatic overages.
- [Braith and Sentry](https://app.braith.dev/compare/sentry): capabilities and when to use both.
- [Free customer-flow test generator](https://app.braith.dev/tools/user-flow-tests): browser-only test cases, no account required.

## Free browser tools
- [Developer tool directory](https://app.braith.dev/tools): JSON, CSV, HTTP, webhook signatures, tokens, URLs, timestamps, text and HAR recordings. No signup or input uploads; no public tool-processing API.
- [JSON diff](https://app.braith.dev/tools/json-diff): compare expected and actual response values.
- [CSV validator](https://app.braith.dev/tools/csv-validator): check quoting, row widths and headers.
- [HAR viewer](https://app.braith.dev/tools/har-viewer): inspect recorded requests without replaying them.
- [HAR sanitiser](https://app.braith.dev/tools/har-sanitizer): make a minimal copy; origins and timings still require review.
- [Stripe signature debugger](https://app.braith.dev/tools/stripe-signature-verifier): raw-body HMAC comparison and separate freshness check; not a replacement for production SDK verification.

## Troubleshoot
- [Payment succeeded but no access](https://app.braith.dev/guides/stripe-payment-succeeded-no-access)
- [Export completed but file empty](https://app.braith.dev/guides/export-success-empty-file)
- [Silent failures](https://app.braith.dev/guides/silent-failures)
- [All guides](https://app.braith.dev/resources): webhook processing, incorrect API results, downloads, session cookies, invitations, saved changes, background jobs and HAR debugging.
- [Support](https://app.braith.dev/support)

## Access boundaries
Run braith connect and wait for the customer to approve its matching code in their signed-in Braith account. Credentials are delivered separately to the CLI, never embedded in the prompt. Do not invent keys, publish secrets, activate billing or deploy their app automatically. There is currently no public MCP server or incident-reading API. Native mobile SDKs and automatic session replay are not offered.