SEC Filing Document Manifest

Inventory bounded public documents in a confirmed EDGAR filing with canonical archive URLs, types, provenance, and optional hashes.

What this Actor gives you

Convert one confirmed filing into a reproducible inventory of primary documents, exhibits, XML, data files, and attachments.

Every Dataset item uses the SEC Complete Data Suite envelope and the primary record type secFilingDocument. 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 is a universal, bounded fallback when no narrower semantic capability matches. The AI receives stable records and explicit gaps instead of inventing a parser or guessing an archive path.

Good fits

• filing attachment discovery
• exhibit and XML inventory
• reproducible document pipelines

Agent selection contract

• Actor slug: sec-filing-document-manifest
• Capability ID: sec.filing.document.manifest
• Intent: list_filing_documents
• Primary Dataset record: secFilingDocument
• Accepted identifiers or inputs: accession+filerCik, accession+filingIndexUrl
• Source authority: SEC
• Hard limits: queries: 100, records: 10,000, sourceRequests: 1,000, 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. Typed records and compact output can keep raw SEC pages, archive markup, and discovery instructions out of 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 universal coverage role: Document bridge between the Filing Catalog and content extraction or form-specific parsers.

It works especially well with sec-edgar-filing-catalog, sec-document-content-extractor, sec-asset-backed-securities-normalizer. 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-annual-report",
      "accession": "0000320193-25-000079",
      "filerCik": "320193",
      "includeHeaderMetadata": false,
      "maxDocumentsPerFiling": 20
    }
  ],
  "maxResults": 3,
  "maxSourceRequests": 2,
  "maxDownloadBytes": 5242880,
  "outputSchemaVersion": "1.0",
  "outputMode": "full"
}

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

• semantic interpretation of document contents
• unconfirmed accessions or arbitrary URLs

Additional non-goals from the capability contract include:

• follow arbitrary user URLs
• parse filing prose
• extract XBRL facts
• provide investment advice
• invoke another 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.