Skip to main content
A summary saves reading time only if the reader can trust it. When every claim links to the text it came from, a reviewer can check a figure in one click instead of rereading the document.

​
Pattern

  1. Generate a summary of a document or of retrieved context.
  2. Call POST /v1/attributions with the document, the summarization prompt as question, and the summary as answer.
  3. Make each returned answer range a hover or click target.
  4. On click, scroll the document pane to the source range and highlight it.

​
UX that works

  • Keep the summary readable. Link the facts, such as numbers, names, dates, and claims, and leave the rest as plain text.
  • Show the evidence in place. A side-by-side document pane, or a popover with the source text, keeps the reader in flow.
  • Use confidence for emphasis, not as a verdict. Sort or style links by strength. confidence says how strongly a phrase is tied to its source, not whether the summary is right.
  • Highlight with the original offsets. Keep the exact document string you sent, so source ranges line up with what you render.

​
Where it fits

  • Financial filings and earnings summaries
  • Contract, policy, and compliance review
  • Support-ticket and call-transcript summaries
  • Research notes and literature digests
  • Analyst-report roundups

​
Implementation

Use the rendering approach from the inline citations cookbook. For PDFs, the PDF attribution cookbook shows how to highlight the source on the original page.