> ## Documentation Index
> Fetch the complete documentation index at: https://docs.heretic.quest/llms.txt
> Use this file to discover all available pages before exploring further.

# Heretic documentation

> Collect browser and connection evidence, retrieve the settled assessment from your server, and understand every structured result field.

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.

<Columns cols={3}>
  <Card title="Run the quickstart" href="/quickstart" icon="play">
    Add the browser collector, pass its request ID to your server, and read the settled projection.
  </Card>

  <Card title="Understand the measurement" href="/concepts/how-heretic-measures" icon="ruler">
    Follow the browser-to-edge request sequence and the six evidence families.
  </Card>

  <Card title="Read the verdict contract" href="/concepts/verdicts-and-coverage" icon="brackets-curly">
    Learn the five verdicts, four finding tiers, and three coverage states.
  </Card>
</Columns>

## Integration in one pass

1. Create a site in the [dashboard](https://heretic.quest/dashboard/keys).
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

| Contract                   | Version |
| -------------------------- | ------: |
| Tenant verdict API         |     `1` |
| Assessment schema          |    `10` |
| Ruleset revision           |     `6` |
| Collector measured payload |     `3` |
| Nested compute probe       |     `2` |
| Identity                   |     `2` |
| Edge NDJSON record         |     `4` |

Start with the [quickstart](/quickstart). Use the [collector reference](/integration/collector) when you need to change endpoint discovery, timing, surface collection, or retention mode.


## Related topics

- [How Heretic measures](/concepts/how-heretic-measures.md)
- [Collector reference](/integration/collector.md)
- [Verdicts and coverage](/concepts/verdicts-and-coverage.md)
- [Troubleshooting](/troubleshooting.md)
- [Quickstart](/quickstart.md)