get_active_sessions
ChatGPTReturns all currently active legislative sessions across all US states. Use this to discover valid session identifiers before filtering search_legislation results by session.
get_legislation_analytics
ChatGPTFetch proprietary FiscalNote analytics for one or more US bills by their IDs. Accepts up to 200 bill IDs and returns scored insights such as likelihood of passage and other predictive signals. Only available for US legislation.
get_legislation_events
ChatGPTFetch committee hearings and committee markups for one or more US bills by their IDs. Accepts up to 200 bill IDs and an optional date range to filter events. Returns event metadata including event type, date, committee, and associated bills. Only available for US legislation.
get_legislation_votes
ChatGPTFetch all recorded committee and chamber votes for one or more US bills by their IDs. Accepts up to 200 bill IDs and returns vote outcomes, vote counts, and how individual members voted. Only available for US legislation.
pn_get_document_text
ChatGPTFetch the full text content of a legislative or regulatory document. IMPORTANT: Only call this tool if a documents[] array was present in a prior tool response AND the specific document object contains a pn_doc_path field. Do not call this tool if pn_doc_path is absent. Pass the pn_doc_path value exactly as returned — it will start with /fn-document-service/. Note: sources[] entries do not have a pn_doc_path and cannot be fetched with this tool. Returns extracted plain text suitable for summarization or analysis.
search_legislation
ChatGPTSearch for legislation. Supports keyword queries, locality codes, status, sponsor, date range, and pagination. Issue and label IDs must be retrieved first from the appdata/issues endpoint. IMPORTANT: For non-US localities, locality_code must include BOTH the bare ISO code AND its "PS-" prefixed variant (e.g., ["GB", "PS-GB"] for the UK; ["EU", "PS-EU"] for the EU). US localities (e.g. "US", "US-CA") do not need the prefix. Returns legislation metadata (title, status, sponsors, actions, etc.) but not the organization-specific issues, labels, or notes. To fetch full details for known IDs, use search_legislation_by_id instead.
search_legislation_by_id
ChatGPTFetch full details for one or more legislation records by their IDs. Accepts up to 200 IDs in a single request. Returns the complete legislative record including title, status, sponsors, actions, and related PolicyNote data. Supports BRIEF, DEFAULT, and FULL fieldsets to control response verbosity. Use this when you already have legislation IDs (e.g., from a prior search_legislation call).
search_regulation
ChatGPTSearch for regulatory documents. Supports keyword queries, locality codes, regulation type, issuing agency, date ranges, and pagination. Issue and label IDs must be retrieved first from the appdata/issues endpoint. The type filter accepts: "comments", "dockets", "public_inspection_desk", "reg_notices", "reg_materials", or "other". IMPORTANT: For non-US localities, locality_code must include BOTH the bare ISO code AND its "PS-" prefixed variant (e.g., ["GB", "PS-GB"] for the UK). US localities do not need the prefix. Returns regulation metadata but not the organization-specific issues, labels, or notes. To fetch full details for known IDs, use search_regulation_by_id instead.
search_regulation_by_id
ChatGPTFetch full details for one or more regulatory documents by their IDs. Accepts up to 200 IDs in a single request. Returns the complete regulatory record including title, agency, document type, and related PolicyNote data. Use this when you already have regulation IDs (e.g., from a prior search_regulation call).