# Apibeary - automated market-signal scouts Apibeary reads public market paperwork (SEC filings, congressional disclosures, contract awards, Fed language) and publishes bullish/bearish flags with a conviction score and a sourced reason. Disclosures: https://apibeary.com/disclosures Terms: https://apibeary.com/terms Privacy: https://apibeary.com/privacy Direction (BULLISH/BEARISH) classifies the event, not the price. It is not a forecast, and no scout's direction has been validated as predictive. Confidence is a heuristic conviction score, not a calibrated probability. On a single filing it is the scout's own 1-5 grade; on a row that rolls several filings together it is their SUM and has no ceiling, so it can read above 5. The stored number is published as it stands — never clamped, never hidden. Informational only - not investment advice. Free public feed (SEC Form 4 insider trades + congressional STOCK Act disclosures): Feed: https://apibeary.com/f/ JSON: https://apibeary.com/feed/public.json RSS: https://apibeary.com/feed/public.rss Corrections: https://apibeary.com/corrections Every row on that feed links to its own source document on EDGAR or to the filed congressional disclosure. Free to quote, cite, and reference with attribution to apibeary.com. Informational only — not investment advice. Signals describe observed filings, not recommendations. Dates are rendered as filed. An insider row leads with the TRADE date the Form 4 reports; a congressional row carries both the member's trade date and the date the disclosure was filed, which are rarely the same day. Neither is the day the information became public in general. ## How to use this feed Cadence. The whole tier is rebuilt once a night, at 21:15 ET, into prebuilt files. Polling more often than daily returns the same bytes. Send the ETag back as If-None-Match and an unchanged feed answers 304 with no body, which costs you and us almost nothing; every page and both feed documents carry one. Rate. There is a per-IP limit, set where a polite crawler never meets it. Walking the whole archive at a human pace is expected and welcome - that is what the archive indexes are for. URLs. https://apibeary.com/f/ today, both scouts https://apibeary.com/f// every published day for one scout, by month https://apibeary.com/f// one day's rows for one scout https://apibeary.com/f// one signal, permanently https://apibeary.com/corrections every correction and void, in full is "sibyl" (SEC Form 4) or "pelosi" (congressional STOCK Act). A row in public.json carries these keys: id integer, stable, the permalink's last segment scout "sibyl" or "pelosi" ticker the symbol as filed issuer_name the company's EDGAR registrant title; ABSENT when the SEC company book does not list the ticker - never guessed direction BULLISH or BEARISH, classifying the event confidence the stored conviction score, unclamped dates labelled date pairs - "Trade date", "Filed"/"Disclosed", "Flagged" - each already a YYYY-MM-DD string flagged_day the day this feed published the row is_backfill 1 when the row reached the feed after the fact reason the sentence, described below facts labelled field pairs; congressional rows carry the member, chamber, account, amount band and disclosure lag here source_url the filing itself, on EDGAR or the congressional discloser's site source_label what that document is permalink the path under /f/ accession the EDGAR accession number, on insider rows A row without a source document is not published at all, so source_url is always present and always absolute. Reasons. A reason is one sentence followed by bracketed clauses. The clauses are facts read off the filing - a 10b5-1 plan, an exercise-and-sell, a catch-up disclosure - or notes we appended when we corrected ourselves. Clauses we cannot recognise are dropped rather than published. Corrections. /corrections carries two kinds of entry. CORRECTED means the row is still published and its text now carries a dated note saying what changed. VOIDED means we withdrew the row: it appears on /corrections with its full retraction and appears nowhere under /f/. Both are published in full, and the original wording is kept in our own audit log.