Heretic documentation

Heretic measures one browser session and reports what the joined evidence supports. It compares browser claims with connection properties observed at the edge and work performed by the client. Heretic returns a categorical verdict with findings, coverage, and version provenance. It does not return a risk score or decide what your application should do.

​

Integration in one pass

1. Create a site in the dashboard.
2. Put its public hrtc_live_... site key in the browser collector.
3. Send the collector’s requestId to your backend through your existing application flow.
4. Keep an hrtc_sk_... verdict key on the server.
5. Read GET https://heretic.quest/v1/verdict/{requestId} from your server.

The request ID is the raw 32-character lowercase hexadecimal nonce. Successful ordinary collection returns it only after the tenant projection is committed.

​

The result

The tenant API returns:

• verdict and conclusive
• projected findings and all six family reports
• family coverage
• assessment provenance
• projected network classification
• optional versioned identity IDs and their components
• edge and timing fields

Use IDs, enums, booleans, versions, and provenance as program inputs. Treat summary, signal headline and detail, network descriptions, collector failure reasons, and coverage reasons as prose.

​

Current contracts

Start with the quickstart. Use the collector reference when you need to change endpoint discovery, timing, surface collection, or retention mode.