💸 Cybersecurity Funding Leads

Cybersecurity funding leads straight from SEC Form D, the notice a company files with the SEC within 15 days of the first sale in a Regulation D private placement. One qualified_funding_lead row per Form D filing that matches this cut, with the issuer's legal name, CIK, city and state, industry group, total offering, amount sold, first-sale date, exemptions and the EDGAR link — the facts a fund, banker, vendor or recruiter needs to act the same week.

How this cut is defined. Form D industry group is a technology group (Computers, Telecommunications, Other Technology) AND the issuer's legal name contains a security / identity / trust / threat term. Form D has no cybersecurity group, so this is a name-pattern cut: every row carries sector_rule saying so. This is a thin cut — measured on the 2026-09-16 filing date: 0 leads from 14 technology-group filings (none carried a security term that day); a zero-row run bills only the start fee.

Why Form D and not news. The previous version of this actor read startup-news feeds and resolved company domains; those feeds are bot-walled or carry no sector tags, so it returned 0–1 leads per run. Form D is the primary source: the issuer files it, the SEC publishes it, and the actor reads the daily EDGAR index and each filing's XML directly. Pooled investment funds (VC/PE/hedge vehicles raising their own capital) are never delivered as leads.

Output is one qualified_funding_lead row per result; billing is pay-per-event, the value event being one qualified funding lead (a $0.02 start fee per run, then $0.05 per qualified funding lead). Source: www.sec.gov.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out.

📊 Sample Output

No sample rows: the Store-example run on this build (run A9YxLc0uW1WkY5hwQ on 0.1.13, 2026-09-18) returned 0 rows and finished with GENUINE_EMPTY: 0 Cybersecurity leads — 14 Form D filings read for the date(s), 14 dropped by the sector rule; engine: NORMAL: emitted=14; dates_complete=2/2. billable=0. The feeds it reads carried nothing that qualified on that day; a run that delivers nothing bills no value event. The record shape is documented from the dataset schema under What you get — no row is invented.

✅ What you get

One qualified_funding_lead per SEC Form D filing that matches the sector rule; every field is as filed on EDGAR.

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_type (string) —
• sector (string/null) —
• sector_rule (string/null) —
• issuer_name (string/null) —
• cik (string/null) —
• accession_number (string/null) —
• form_type (string/null) —
• filed_date (string/null) —
• industry_group (string/null) —
• industry_type (string/null) —
• entity_type (string/null) —
• jurisdiction_of_incorporation (string/null) —
• year_of_incorporation (integer/string/null) —
• issuer_city (string/null) —
• issuer_state_or_country (string/null) —
• issuer_postal_code (string/null) —
• issuer_phone (string/null) —
• revenue_range (string/null) —
• federal_exemptions (array/null) —
• security_types (array/null) —
• total_offering_amount (integer/number/null) —
• total_amount_sold (integer/number/null) —
• total_remaining (integer/number/null) —
• investor_count (integer/null) —
• minimum_investment (integer/number/null) —
• date_of_first_sale (string/null) —
• yet_to_sell (boolean/null) —
• is_amendment (boolean/null) —
• related_persons (array/null) —
• filing_index_url (string/null) —
• source_url (string/null) —
• observed_at (string/null) —

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "maxRecords": 10
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 0 × $0.05 qualified_funding_lead = $0.02 on the Free tier

2. A smaller, narrowed run

{
  "maxRecords": 5
}

Caps the run at 5 rows; same billing shape as the sample run above.

3. A full-size run

{
  "maxRecords": 40
}

The same input run on a schedule; each run is billed only for what it delivers.

🧾 JSON sample record

No dataset record to show for this actor type (see Sample Output).

🔧 How it works

Source. The actor reads www.sec.gov. Public pages and feeds only; nothing behind a login.

Transport. Plain HTTPS from the Apify platform, no proxy.

Terminal states. A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

Charging. Each qualified funding lead is charged at the moment it is pushed (qualified_funding_lead); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

Source. SEC EDGAR daily index (https://www.sec.gov/Archives/edgar/daily-index/…/form.YYYYMMDD.idx) for the latest complete filing date(s), then each Form D's primary_doc.xml under https://www.sec.gov/Archives/edgar/data/<CIK>/<accession>/. A fixed known-good index is fetched first as a canary; if EDGAR's shape or availability changes, the run fails loud and bills nothing.

Fair access. At most 2 requests per second with the SEC-required contact User-Agent (NexGenData FormDWatch/1.0 fleet2@nexgendata.com, overridable with secUserAgent). A full filing day is 150–300 Form D filings, so a run takes 2–4 minutes.

Filtering. The engine keeps filings whose industry group matches the cut, then the sector layer applies the name pattern (where the cut has one) and drops every pooled investment fund. filingDates controls how many complete EDGAR dates are read (1 = the latest); issuerStates, minTotalOfferingAmount and maxTotalOfferingAmount narrow further; includeAmendments adds Form D/A.

No repeats on a schedule. Filings are read by EDGAR filing date, so a daily schedule with filingDates: 1 delivers each filing once. There is no watch baseline to seed.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

⏰ Set it on a schedule

A single run is a snapshot. The value is the feed: open the actor in Apify Console → Schedules → Create new, add this actor with the input you want, and pick a cadence:

• Daily — 0 7 * * * (07:00 UTC): catch changes within a day.
• Weekly — 0 7 * * 1: a Monday digest.

Each run is independent; keep the same input on the schedule so the results stay comparable. Schedules can also POST results to a webhook (Console → Integrations).

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Qualified Funding Lead (qualified_funding_lead)	$0.05	$0.04	$0.04	$0.03

Worked at the live Free-tier price:

• 5 qualified funding leads: $0.02 start + 5 × $0.05 = $0.27
• 25 qualified funding leads: $0.02 start + 25 × $0.05 = $1.27
• 40 qualified funding leads: $0.02 start + 40 × $0.05 = $2.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: GENUINE_EMPTY: 0 Cybersecurity leads — 14 Form D filings read for the date(s), 14 dropped by the sector rule; engine: NORMAL: emitted=14; dates_complete=2/2. billable=0. maxRecords is a hard ceiling on what is delivered and billed, never a target.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by www.sec.gov. It collects only what the source publishes to any visitor, identifies itself, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (www.sec.gov) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxRecords (default 40). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other startup funding leads actors?
A: Same output shape and billing model; this one covers www.sec.gov. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Status says CAPPED → your cap (maxRecords) was reached → raise it for a bigger run.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

🔗 Related Actors

• AI Funding Leads — AI funding leads from SEC Form D: one row per new Form D filed by a technology-group issuer whose legal name carries an AI/ML/data term — issuer, CIK…
• Biotech Funding Leads — Biotech & health funding leads from SEC Form D: one row per new Form D filed by a Health Care-group issuer (Biotechnology, Pharmaceuticals, Other Hea…
• Climate-Tech Funding Leads — Climate & clean-energy funding leads from SEC Form D: one row per new Form D filed by an Energy Conservation, Environmental Services, Electric Utilit…
• European Startup Funding Tracker — Clean, structured European startup funding rounds from EU-Startups' public feed — one record per deal, extracted from feed fields only. The article p…
• Fintech Funding Leads — Fintech & financial-services funding leads from SEC Form D: one row per new Form D filed by a Commercial Banking, Insurance, Investment Banking or Ot…
• 💵 SEC Form D Funding Leads — New Raises Watch — SEC EDGAR Form D watch — new private placements and funding leads (issuer, amount, dates) with deltas on new and changed filings
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.