Skip to content

Add Bargo Congress Trades API to Market Data & Data Sources - #535

Open
bargo-ai wants to merge 1 commit into
wilsonfreitas:mainfrom
bargo-ai:add-bargo-congress-trades-api
Open

Add Bargo Congress Trades API to Market Data & Data Sources#535
bargo-ai wants to merge 1 commit into
wilsonfreitas:mainfrom
bargo-ai:add-bargo-congress-trades-api

Conversation

@bargo-ai

@bargo-ai bargo-ai commented Aug 2, 2026

Copy link
Copy Markdown

Adding the Bargo Congress Trades API under Market Data & Data Sources. I'm the developer behind Bargo, so flagging that up front.

It's a free API over U.S. House and Senate STOCK Act securities transaction disclosures, normalized so both chambers return the same shape. Each record carries member and chamber, ticker and asset description, transaction type, the disclosed value range, transaction and disclosure dates, a link to the official filing, and price-performance fields where available. Six endpoints: trades, trades by ticker, members, a single member, aggregate stats, and health.

Works keyless (30 requests / 100 rows per day per IP); a free key raises that to 100 requests / 1,000 rows. No paid tier gates the data. There's also a hosted MCP server for agent use.

Official Python and TypeScript clients are open source in the linked repo, published as bargo-congress on PyPI and @bargo-ai/congress on npm and JSR.

On the guidelines:

  • One-sentence description ending with a period, tags in separate backticks, https only.
  • GitHub repo included as the [GitHub](...) suffix per the "project with website and GitHub repo" format. Happy to move this to Commercial & Proprietary Services if you'd rather it sit there — the API is free but Bargo is a commercial product, so your call.
  • Repo is active (commits this week) and the README has usage examples for both clients.

Worth noting the data is disclosure-based, not real-time: STOCK Act filings can legally lag a trade by up to ~45 days.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Copy link
Copy Markdown
Owner

Thanks for the contribution. The linked repository contains lightweight client packages rather than substantive implementation of the underlying Bargo service, so this entry should move to Commercial & Proprietary Services. Please describe the documented free limits accurately—keyless and free-key allowances separately—and retain links to stable pricing, API documentation, and provenance information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants