Start with coverage and source records
Check data coverage and freshness before using a result. Preserve the displayed mode, filing date, quote date, accession number, and source URL. Follow the original SEC filing for consequential conclusions because filings can be amended and the loaded dataset can be incomplete or delayed.
Use public, read-only routes
The company directory, screen definitions, research guides, and methodology explain the public research surface. The workspace, saved filters, and watchlist are user-controlled browser state. Do not create, delete, or disclose that state without explicit user instruction.
Keep classifications and estimates qualified
Transaction codes, role groupings, market snapshots, and company scores are aids for review. They do not establish intent, independence, expected returns, or material non-public information. Synthetic examples are not real filings. Missing values remain unavailable rather than becoming zero.
Respect operational boundaries
Do not scrape around rate limits, infer undisclosed personal information, or treat this site as affiliated with the SEC. Use the correction channel for reproducible issues and never submit credentials, private watchlists, or personal financial information.
Stable, linkable URL parameters
The homepage screener at / reads these query parameters and is safe to deep-link with a prefilled query: q (search text, up to 80 characters), type (purchases | sales | awards | all), role (all | ceo | cfo | director | officer | owner), days (7 | 30 | 90 | 365 | all), min (minimum trade value in dollars), cap (all | micro | small | mid | large), sector, plans (include | exclude), buyers (0 | 2 | 3), ownership (all | D | I), sort (filed | value | score | cap | price), order (asc | desc), page, size (25 | 50 | 100), and tickers (comma-separated). Unrecognized or out-of-range values fall back to defaults rather than erroring. Example: /?role=ceo&min=100000.
A static, machine-readable dataset of the worked transaction-code examples cited by the research guides is published at /data/form4-transaction-code-examples.json, with an asOf date and source filing on every row.