SEC Red Flag Monitor - Restatements and Insider Clusters

SEC Red Flag Monitor - Filing Review API

Find recent SEC filings worth an analyst’s attention for an identified public company. The report flags filing-type or item-code patterns, including late filings and executive changes, without concluding that wrongdoing or financial distress occurred.

Current price: $0.35 per ticker/CIK report (sec-red-flag-report). Review the Pricing tab and set a spending limit before starting the Actor.

Start with one ticker/CIK report

Replace the contact placeholder with a real email you are authorised to use before running. It is sent in SEC fair-access identification; keep the completed input private rather than publishing it as a shared example.

{
  "tickersOrCiks": [
    "AAPL"
  ],
  "secContactEmail": "your-contact@example.com",
  "lookbackDays": 90,
  "clusterWindowDays": 5,
  "minOwnershipFilingsForCluster": 3,
  "concurrency": 1
}

The sample demonstrates the input format, not current source coverage or a customer result. The placeholder is not a production identity.

Review the source evidence

Verify the resolved entity in disambiguation, then read metrics.filingsInspected and the original filings behind highlights. An ownership-filing cluster counts filings; it does not establish insider buying, transaction direction or intent.

The input supports up to 25 ticker/CIK entries. A bounded recent-filings check is not a complete company history. Short or failed source responses are not a clean risk assessment, and the score is not a probability of misconduct or a trading/credit recommendation. The Actor creates no watchlist schedule or alerts automatically.

Delivery, billing and retries

The Actor reserves budget for a report before source work, then attempts to save the dataset row before charging its named report event. Delivered error or no-match rows are still billed, including API_ERROR output, so a source failure should not be treated as a valid assessment.

Saving and charging are separate operations rather than an atomic transaction, so failed confirmation makes RUN_SUMMARY flag uncertainty and stop further report work. Inspect the dataset and platform charge history before retrying, because another run can produce another fee. These are Actor event fees; check current platform terms and plan charges separately.

Practical guide and support

Follow Triage a company’s SEC filing evidence for field interpretation and a review workflow. Existing output illustrations or historical owner tests are not customer case studies or evidence of current complete coverage.

Use the Issues tab with a sanitized input for support. Keep real contact details and private dependency lists out of public reports.