Aller au contenu

Données ouvertes

Bibliothèque

Jeux de données ouverts, entièrement documentés — interrogeables ici, et lisibles par n’importe quel LLM.

Les titres et les descriptions proviennent des sources de données, en anglais.

  • SEC 8-K material-event velocity (agent-curated)

    SEC 8-K material-event velocity (monthly)

    Monthly enrichment panel scoring how actively ~58 SEC-registered US and Canadian companies disclose material events. Each run fetches the keyless SEC EDGAR submissions JSON per company (ticker->CIK resolved from the SEC's own company_tickers_exchange.json) and classifies every 8-K's item codes into a documented 8-category taxonomy over the trailing 12 complete months. Per (company, month): 8-K counts by category, has_earnings_8k (item 2.02) and has_exec_change_8k (item 5.02) flags, event_intensity_score = 100 * (0.60 * min-max(n_8k) + 0.40 * min-max(n_governance + n_financial)) normalized within each month, a deterministic intensity_rank, and spike_flag when n_8k >= 2 with z >= 2.0 against the company's own 12-month baseline; every row carries its CIK and the exact source_url it was built from, the panel is dense and zero-filled, and foreign private issuers (6-K/40-F, no 8-K) keep structural zeros flagged by is_8k_filer. Who joins this: a quant desk joins monthly per-ticker event intensity to returns on ticker + month for event studies, and an IR/comms team benchmarks disclosure cadence against peers on company_name (primary key (as_of, month, company_name); join keys ticker, company_name, month, country_code ISO alpha-3). Caveats: category counts are item-code occurrences (a \"2.02,9.01\" filing counts once as financial and once as exhibits); intensity scores are within-month relative and not comparable across months; private companies and tickers absent from the SEC file are excluded. No filing text is stored.

    • sec
    • signals
    • finance
    • monthly
    lignes
    696
    Qualité
    100
    Mis à jour
    27 sept. 2026
    À jour
    Licence
    Usage commercial OK

Utiliser votre propre clé d’IA

Une fois l’allocation gratuite du jour épuisée, les fonctions d’IA peuvent passer par votre propre compte fournisseur.

Conservée uniquement dans cet onglet (effacée à sa fermeture) et envoyée avec chaque requête d’IA. Nos serveurs l’utilisent pour cette requête et ne la stockent ni ne la journalisent jamais.