Documentation

Find the next useful step.

Choose a path by what you need to do, then open exact technical detail only when the workflow requires it.

Browse documentation

Choose a path

Product use, evidence review or developer integration.

Begin with the outcome you need rather than the internal subsystem name.

Start an investigation

Set up an account and workspace, confirm authorization and prepare a first bounded plan.

Review results and sources

Understand findings, confidence, original sources, reports and the relationship map.

Build with the API

Create a scoped server-side key, complete the v2 quick start and inspect exact route details.

Product quick start

Four steps to a reviewable investigation.

The shortest safe path keeps authorization, planning and source review explicit.

  1. 1. Confirm authority

    Use only public clues you may lawfully investigate.

  2. 2. Prepare coverage

    Review compatible data sources, gaps and the credit estimate.

  3. 3. Start deliberately

    Confirm the bounded plan before any research work begins.

  4. 4. Review sources

    Check confidence and original source references before drawing a conclusion.

Browse guides

Open one documentation group.

Sections stay collapsed until you need them, keeping this page useful as an orientation surface.

Start · 3 guides
Workspaces · 2 guides
Investigations · 3 guides
Evidence · 4 guides
API · 3 guides
Account · 4 guides
Exact developer contract references

Public API v2 route, request, response, lifecycle, error and governance detail is generated from the deterministic product and OpenAPI contracts.