get_filing_correspondence

ai.serff/ca-rate-filings · Verify this server

**Use this to see the REGULATORY POSITION history of a filing — the whole CDI ↔ carrier dialogue plus filer contact info — in order. NOT for the filing's content, rates, or forms.** Content questions live in `get_filing_summary` (actuarial narrative), `get_filing_source_file_link` (raw PDFs for human download), and `search_filing_embeds` (paragraph-level body search). Right questions this answers: - "Show me the full objection thread on FARM-134879410" — every letter, in order - "Who filed this and who reviewed it at CDI" - "What did the carrier say in response to CDI's second objection" - "Give me the paper trail so I can audit how this filing progressed" Fetches every chunk in `correspondence_embeds` for the given SERFF, grouped by `source_file` (one entry per attachment) and ordered by `chunk_index` within each file. Covers three attachment types: - **correspondence_attachment_*.pdf** — the objection thread (CDI questions + carrier responses + follow-ups) - **supporting_document_attachment_*.pdf** — actuarial memos, exhibits, transmittal letters (filer contact / authorship signals) - **<SERFF>.pdf** — SERFF's top-level cover page with filing-person contact block Everything comes back as readable text so the caller can quote it verbatim to the user. Group by `source_file` prefix client-side if you only want, e.g., the objection thread (`correspondence_attachment_*`). For a one-call summary that ALSO includes filing metadata, extracted summary, references, and lineage alongside the correspondence, use `get_filing_dossier`. **Right surface for**: - "Show me the objection thread on this filing" — after a search or when the user hands you a SERFF id and asks what CDI said. - "Pull the carrier's full response to CDI's second-round questions" — you get everything, in order; extract the passage you need. - Auditing/review workflows where a regulator wants the full paper trail on one filing. **Right combination**: pair with `search_correspondence_embeds` — that surface finds candidate filings semantically; this one pulls the whole thread once you've picked one worth reading end-to-end. **Coverage**: not every filing has correspondence. Only filings that received at least one objection round from the DOI (or the carrier uploaded a proactive supplemental letter under the same `correspondence_attachment_` prefix) will have chunks. A filing with no exchange returns `{ files: [], chunk_count: 0 }` — not an error. Returns `{ serff, files: [{ source_file, chunks: [{ chunk_index, text, emails, email_domains, page_date }] }], file_count, chunk_count }`. Each chunk's text is capped at 2000 chars.