Public-record market data, as an API
A congressional stock trading API with the source filing on every event
The Gemral Edge API is a read-only REST API over public-record market data: congressional periodic transaction reports, federal contract awards and pre-award notices, SEC filings such as Form 4, 8-K, 13D and 13F, Federal Register actions, lobbying disclosures and off-exchange short volume. Every event carries a link to the original filing, a stable identifier, the time Gemral published it and, where the source provides one, the time the filing became public, so backtests can be run without look-ahead bias.
Where do teams use an API key?
- Trading models: poll for new congressional trades, defense contracts or insider clusters and feed them into a scoring model.
- Data warehouses: export new events each night as CSV or JSONL with cursor paging into Snowflake, BigQuery or Postgres.
- Backtest notebooks: pull history and test whether a signal led price using the point-in-time timestamps.
- Spreadsheets: refresh a watchlist in Excel or Google Sheets with Power Query or Apps Script.
- Team alerts: receive signed webhooks in Slack or Discord natively, or route them to Teams, email or a CRM through Zapier or Make.
- Your own product: show the data to your own users inside your app or newsletter, with attribution, under the data license.
How do webhooks and limits work?
Webhooks are delivered by a server job every few minutes, signed with an HMAC over a timestamp and the raw body, retried with backoff and never redirected. Every authenticated response carries rate-limit headers. Keys are stored only as a hash, shown once, and can be rotated with a grace period so running jobs do not break.
How can an institution evaluate it?
Organizations can request a 60-day evaluation trial with a company email; a person reviews each request. The plan can be paid by card or by invoice through ACH, wire or card on Net 30 terms. The data license allows internal use and in-product display with attribution, and does not allow reselling the raw data as a dataset, feed or API. Service status is published live and support is by email. The data is informational and is not investment advice.
Which resources does one endpoint return?
The API has a single GET endpoint and a resource parameter. The main resources are: feed, the latest verified events with cursor paging and since and before filters; leaderboard, members of Congress ranked by estimated return over a week, a month, a year or all time; signals and screen, tickers where several independent event types converge in the same window; exposure and beneficiaries, which companies are tied to a contract award or a ticker; impact and explain, how a past event of the same kind was followed by price moves; policy, Federal Register actions by document number or free text; actor, the profile of a lawmaker, insider or fund; forecast, track-record and receipts, the probability forecasts and their scored history; and chart-patterns, crypto chart pattern detections with entry, stop and target levels by symbol and timeframe. The full list of parameters is in the public OpenAPI 3.1 document and the API reference page.
How is the data kept free of look-ahead bias?
Public records arrive late and sometimes change. A congressional trade can be disclosed weeks after the trade date, a contract notice can be amended, and an SEC filing can be corrected. Each event therefore keeps the date of the underlying action, the date the source made it public and the time Gemral published it. A backtest that only uses an event after its public date sees the market the way a reader at that time could have seen it. When the same trade appears in two sources, for example a House Clerk filing and a secondary tracker, the records are merged into one event so that counts and returns are not doubled.
How do exports, paging and keys work for a data team?
The feed, receipts and chart-patterns resources can be returned as JSON, CSV or JSONL. CSV and JSONL return one row per event with a stable header, and larger pages are allowed for those formats so that a nightly job can move a full day of events in a few calls. Each response that has more rows includes a next_cursor value to pass on the next call. Export rows count toward a monthly quota that is shown in the developer portal together with request counts by day and by resource. A key can be rotated with a grace period so the old key keeps working while jobs switch over, and a key can be revoked at once if it leaks.
What does the API not do?
The API does not place trades, does not give buy or sell recommendations and does not offer a streaming socket connection; new events are delivered by polling the feed or through webhooks. Support is by email during business days rather than a round-the-clock desk, and the uptime target is published without service credits unless a separate written agreement says otherwise. Teams that need these terms in a contract can ask for them during the trial.
What related alternative intelligence streams are available?
Cross-reference correlated public records across our alternative intelligence directories, statutory trackers, and quantitative research libraries:
Frequently asked questions
Where does the data come from? Is any of it non-public?
Only public records: House and Senate periodic transaction reports, USAspending and SAM.gov, SEC EDGAR (Form 4, 8-K, 13D, 13F), the Federal Register, LDA lobbying filings and FINRA short-volume files. We do not collect or sell material non-public information.
How fresh is it?
Each source is ingested on its own schedule, from minutes to once a day. The status page shows the last successful update of every source. Webhooks go out within about five minutes of an event being published.
Can I backtest without look-ahead bias?
Yes. created_at is the time we published the event and disclosed_at is when the filing became public (where the source has one). Filter on those, not on the trade date.
How are keys and webhooks secured?
Keys are stored only as a hash and shown once. You can rotate a key with a grace period so nothing breaks. Webhooks are HTTPS only, signed with a timestamped HMAC, and never follow redirects.
How does the 60-day trial work?
Send the form with your company email. A person reviews it, usually within one business day. Sign in with that same email and the API plan turns on for 60 days. Trial data is for evaluation only.
Can we pay by invoice?
Yes. Request an invoice and we send it from Stripe, payable by ACH, wire or card, Net 30. Monthly or annual.
What happens when the plan ends?
Keys stop working and webhooks stop. You may keep data you already pulled under the license.
Risk Disclaimer
Trading and investing in digital assets, financial instruments, and predictive events involve substantial risk of loss and are not suitable for every investor. The predictive intelligence, probability distributions, historical precedents, and scenario modeling presented on this page are compiled for informational and research purposes only and do not constitute financial, investment, legal, or tax advice. Past performance and statistical precedents do not guarantee future outcomes. Always conduct independent due diligence before committing capital.