A search hit for a Form D filing is useful primary-source research evidence. It is not automatically a completed funding round, a final amount raised or a verified link to a company domain. A pipeline that converts every hit into a funded badge adds claims the collection did not establish.
The Actor at funding-round-tracker is currently titled SEC Form D Search Evidence. It returns identified SEC search hits with filing links and decision-support fields. Its stable URL remains useful, but consumers should read the current contract rather than infer behavior from the historical slug.
Make the query scope explicit
This is the installed public example. It searches a phrase within a declared lookback and limits collection. It is a proposed request, not a new list of filings retrieved for this article.
{
"queries": [
"artificial intelligence"
],
"sinceDays": 180,
"limit": 1,
"maxConcurrency": 1
}
The runtime validates types and bounds instead of quietly coercing malformed settings. Keep the submitted query and date window beside every imported filing identity. A broad phrase can match text beyond an issuer name; a hit for that phrase is not a corporate-domain match.
Require an identified document
A useful filing row needs an accession number and a direct filing URL. Deduplication uses the filing identity so overlapping queries do not turn one document into several supposed transactions. Rows lacking the required identity remain source-shape diagnostics rather than invented billable records.
Retain accession, CIK, filed date, source URL and the query evidence. Store them in a filing table first. A separate relationship can link a reviewer-approved issuer to your company record. That separation lets you correct an attribution mistake without rewriting the original source observation.
Keep the filing distinct from a financing claim
The SEC describes Form D as a notice of an exempt offering. A notice can be amended, and search metadata is not a complete account of offering proceeds, valuation, investors or a venture-stage label. Open the cited document when the business question requires those details, then record precisely which statement the document supports.
The installed decision layer makes this distinction visible through confidence risks, gaps and a recommended next action. Preserve those fields instead of retaining only the filer name. A research queue with explicit issuer verification is more useful than an apparently enriched CRM field whose meaning cannot be reconstructed.
Separate no match from unavailable collection
An empty successful query is a bounded no-match result. A failed source request cannot establish that no filing exists. The Actor returns free outcome rows for relevant diagnostics, while OUTPUT reconciles source success, candidate counts, merged duplicates, delivery and partial state.
Import filing evidence and run-level coverage together. A partial run can leave useful identified rows while some queries remain unmeasured. The Actor is stateless and can return the same current matches again on another run; keep destination keys based on filing identity and inspect uncertain delivery before repeating collection.
For a regression fixture, pass duplicate observations of one accession through the local deduplication function and verify that the filing remains one identity with query context. Add a hit without an accession and require a diagnostic. Those local checks validate transformation behavior only. They do not establish source availability or verify any company's financing history, and a later platform run can charge again for already known filing evidence.
Price and verification scope
FREE-tier event prices read on 24 October 2026 are $0.005 for apify-actor-start and $0.005 for result-found. Start-event count can depend on allocated memory; other account tiers have their own rates. Check the listing's current billable unit and the platform's run spending limit before executing an example. Input row or result caps are separate from Max total charge. A free diagnostic does not necessarily remove the platform start charge.
This article is pinned to public latest build 0.2.1 (f0CCbAPsWFaOPjLI6) at the recorded read time. Source, input and pricing were read from Apify; no new cloud build or run was started. The supplied example and any synthetic local checks do not establish current source facts, cloud delivery or customer outcomes.
Inspect the Actor's current contract and pricing.
AI-assisted writing. Source contracts and verification limits are documented above.
Top comments (0)