SEC Comment Letter Threads

Normalize manifest-confirmed public SEC filing-review correspondence as chronological, evidence-bound messages with explicit partial gaps.

What this Actor gives you

Turn confirmed UPLOAD and CORRESP filings into ordered message records and conservative threads without inventing issues from incomplete text.

Every Dataset item uses the SEC Complete Data Suite envelope and the primary record type secCommentLetterMessage. Stable IDs, explicit coverage, source/evidence references, parser versions, warnings, and structured SUMMARY/ERRORS outputs make the result practical for both agent pipelines and human review.

Why an AI agent chooses this

It turns one SEC domain into a narrow, versioned record contract. The AI can reason over facts, deltas, and evidence without spending context on form-specific parsing instructions.

Good fits

• SEC filing-review history
• comment-letter message tracking
• issuer response chronology

Agent selection contract

• Actor slug: sec-comment-letter-thread-normalizer
• Capability ID: sec.comment.letter.thread
• Intent: get_comment_letter_threads
• Primary Dataset record: secCommentLetterMessage
• Accepted identifiers or inputs: entityCik, fileNumber+filerCik, accession+filerCik
• Source authority: SEC
• Hard limits: queries: 20, records: 200, sourceRequests: 400, downloadBytes: 52,428,800

Choose this Actor when the requested outcome matches the capability and record type above. The contract is deterministic: unknown source values, incompatible schema majors, ambiguity, truncation, and partial source failures remain visible instead of being silently guessed away.

Context and token efficiency

This Actor makes no LLM, embedding, or vector-search call and therefore spends zero model tokens internally. Task-specific records and bounded evidence can replace raw filings plus parser prompts in downstream model context.

For Suite-level selection, an AI client can use the compact agent-catalog.json instead of loading this or the other Actor READMEs. Under that documented baseline, README-selection tokens are avoided by construction.

No fixed percentage is promised: actual downstream token savings depend on the client model, tokenizer, source document, output mode, and requested evidence.

Part of the SEC Complete Data Suite

The SEC Complete Data Suite separates universal coverage, specialized normalization, and deterministic aggregation into focused Actors. This Actor provides the specialized normalization role: Filing-review semantics layer and direct input to Regulatory Risk and disclosure workflows.

It works especially well with sec-document-content-extractor, sec-regulatory-risk-aggregator, sec-disclosure-risk-feed-aggregator. Suite Actors exchange documented record envelopes and exact identifiers; they do not hide sibling runs or surprise network costs. A client or the sec-ai-query-planner decides which steps to execute.

Example input

{
  "queries": [
    {
      "requestId": "apple-2015-corresp",
      "queryMode": "accession",
      "accession": "0001193125-15-115893",
      "filerCik": "0000320193",
      "forms": [
        "CORRESP"
      ],
      "maxMessages": 1
    }
  ],
  "maxResults": 1,
  "maxIssues": 10,
  "maxSourceRequests": 12,
  "maxDownloadBytes": 1000000
}

The executable input schema remains the authority for modes, filters, defaults, cursor rules, and maximum values.

Runtime and cost controls

The hard limits above are enforceable ceilings, not usage targets. Actual runtime and platform cost depend on selected inputs, source requests, downloaded bytes, result volume, and the Apify run configuration. Start with the bounded example, lower maxResults and byte/request limits where the schema permits, and inspect SUMMARY plus ERRORS before expanding a run. There is no hidden model-token charge inside this Actor.

Not the right tool for

• private SEC correspondence
• automatic issue extraction, legal conclusions, or inferred regulator sentiment

Additional non-goals from the capability contract include:

• reconstruct private or redacted correspondence
• claim an issue is resolved without explicit SEC evidence
• provide legal, investment, or filing advice
• call a sibling Actor

Trust, provenance, and limits

• It uses only its inventoried public SEC sources.
• Inputs, requests, bytes, records, retries, redirects, and cursor scope are bounded by the executable contract.
• Derived records retain exact input record IDs and evidence IDs where the capability performs normalization or aggregation.
• This independent community Actor is not affiliated with or endorsed by the U.S. Securities and Exchange Commission.
• The output is public-source data processing, not legal, compliance, accounting, voting, or investment advice.

Reproducible support report

For a diagnosable issue, retain the Actor slug, run ID, sanitized input, SUMMARY, ERRORS, and the first unexpected record ID. Never include an API token, secret, private filing, or unrelated Dataset contents.

Publication status

The Actor API and canonical Apify Store page are authoritative for current availability, active build, and pricing. This README deliberately does not duplicate mutable lifecycle or price claims.