Congress.gov API: schema fixes, client-generation improvements and early planning for v4
Oct 6, 2026
CRS representatives said they updated the congress.gov OpenAPI specification to harmonize timestamps and response schemas, added operation IDs to improve client generation, and signaled early planning for API v4; MCP (model context protocol) integration is on the roadmap.
The full story
William Blackerby, librarian and legislative data specialist on the congress.gov team, described recent API work focused on the OpenAPI specification. He said the team addressed inconsistencies in timestamp formats, added missing response schemas and operation IDs, and tested changes against tools to reduce client-generation errors.
Blackerby warned that some necessary changes may require substantial adjustments and could break existing clients, so the team is beginning version-4 planning without a firm release date. "Please check the GitHub issue tracker for updates, and please keep the issues coming," he said, urging developers to report usage and API needs. Moderators and other staff confirmed that MCP wrappers and agent-focused interfaces are on the road map but require backend changes and resources to implement.
Written with AI from the event video and transcript. Check it against the source ↓
