Changelog

Faster Queries

Lower v3 query latency: query responses are smaller, so they arrive faster. Ranking and every field you use are unchanged.

Works on every indexing endpoint: S3, GCS, Azure, R2, Supabase, Backblaze, Dropbox, Google Drive, SharePoint, OneDrive, URL, YouTube, and text/file upload, across the bucket, directory, and single-file variants.

Mask PII before it’s embedded or stored: set mask_pii: true on any indexing request and Captain detects and masks personally identifiable information in the parsed content after parsing, before embedding. Nothing unmasked reaches the search index, the chunk text, the returned regions, or the stored figure crops. It’s opt-in and per-job; the flag defaults to false, so existing indexing is unchanged. See PII Masking.
Text: detected PII is replaced with entity tags: <PERSON>, <EMAIL_ADDRESS>, <US_SSN>, <PHONE_NUMBER>, <CREDIT_CARD>, and other high-value identifiers. Dates and generic numbers are intentionally left alone.
Images: for standalone image files and images embedded in PDFs, PII text visible in the pixels is covered with solid boxes, so both the stored, retrievable image and its visual embedding are redacted.
Regions: when you query with include.regions, the per-region text is masked too, so the layout view carries no raw PII either.

Figure crops on query results: v3 query responses now return a presigned image_url on each region, pointing at a cropped image of the figure it came from. PDF figures are cropped at index time and served with a 15-minute presigned URL, so you can show the exact chart or table a chunk was pulled from. Available on the document endpoints as well. See Advanced Search & Relations.