Klarefi Documentation

Turn applicant documents and answers into structured, evidence-backed facts you can act on.

Klarefi

Klarefi helps regulated teams complete cases before they reach human review. You send applicant answers and documents, Klarefi resolves the facts a workflow needs, and every fact is linked back to evidence.

The case is the record you read for current state. Hosted Intake, operator review, webhooks, and handoff packages all use the same case.

From input to review

Core Objects

  • Case - one intake packet moving from submission to review. Read it from the API any time for current state.
  • Session - a signed applicant-facing intake flow for a case.
  • Fact - a structured value the workflow needs, such as incident_date.
  • Evidence - the source quote or document span that supports a fact.
  • Event - a webhook signal that case state changed.
  • Package - a review-ready handoff view for a case.

Primary Integration

Start with Hosted Intake. Your backend creates a session, redirects the applicant to Klarefi, and reads the completed case when the intake is ready.

Hosted Intake covers the applicant-facing flow: form steps, uploads, follow-up questions, submission, webhooks, and the cited case package operators review.

Use These Docs With AI

Start Building

What To Rely On

  • Read the case when you need current state. Treat webhooks as notifications.
  • Every document-derived fact should carry evidence.
  • Facts without enough support route to follow-up or human review.
  • Use the case package as the operator handoff.

On this page