KeyVex Bills API

The Bills API from KeyVex — 1 operation(s) for bills.

GitHub OpenAPI

Operations 1

GET /v1/bills Returns congressional bill metadata from api.congress.gov #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/keyvex-com:keyvex-com-bills-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

keyvex-com-bills-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: KeyVex Bills API
  version: 0.102.0
  termsOfService: https://keyvex.com/terms
  description: 'US public financial-disclosure data — congressional trades, insider filings (Form 4), lobbying, Treasury auctions, member profiles. Requires an API key — create a free one at https://keyvex.com and send it as the header `x-api-key: `. A free key returns most public-record datasets (one year of history; no market-price data and a few heavy datasets are on paid plans only), capped at 60 requests/day; paid plans raise the caps. The daily allowance resets at midnight Eastern.'
servers:
- url: https://api.keyvex.com
security:
- ApiKeyAuth: []
tags:
- name: Bills
paths:
  /v1/bills:
    get:
      operationId: get_bills
      summary: Returns congressional bill metadata from api.congress.gov
      description: 'Returns congressional bill metadata from api.congress.gov. Use this when the user asks about: bills introduced this Congress, the status of a specific bill, House vs Senate bill volume, what bills mention a topic, or to bridge from a roll-call vote (legislation_type + legislation_number) to the underlying bill. Source: api.congress.gov v3 (Library of Congress). Covers ALL bill types: HR (House Bill), S (Senate Bill), HRES (House Simple Resolution), SRES (Senate Simple Resolution), HJRES (House Joint Resolution), SJRES (Senate Joint Resolution), HCONRES (House Concurrent Resolution), SCONRES (Senate Concurrent Resolution). v1A returns metadata only: title, type + number, originating chamber, latest action (date + text), and links. Sponsors, cosponsors, full action history, bill text, and CRS summaries live at `api_url` (structured JSON) and `congress_gov_url` (public HTML). Agents follow those for prose detail. Bill identifiers are stable composite keys formatted as {congress}-{TYPE}-{number}, e.g., ''119-HR-134'', ''119-S-1234'', ''118-HJRES-5''. Use bill_id for the fastest direct lookup. Pure-publisher posture: KeyVex returns what''s in the public record. No legislative outcome predictions, no ''likely to pass'' signals.'
      parameters:
      - name: bill_id
        in: query
        required: false
        description: Composite bill identifier ('{congress}-{TYPE}-{number}', e.g., '119-HR-134'). Direct doc lookup, fastest path.
        schema:
          type: string
      - name: congress
        in: query
        required: false
        description: Congress number (e.g., 119 = January 2025 onward; 118 = January 2023 - January 2025).
        schema:
          type: integer
      - name: bill_type
        in: query
        required: false
        description: Type code. HR/S are bills; HRES/SRES are simple resolutions (single-chamber, non-binding); HJRES/SJRES are joint resolutions (both chambers, can become law); HCONRES/SCONRES are concurrent resolutions (both chambers, non-binding).
        schema:
          type: string
          enum:
          - HR
          - S
          - HRES
          - SRES
          - HJRES
          - SJRES
          - HCONRES
          - SCONRES
      - name: title
        in: query
        required: false
        description: Case-insensitive substring against bill title. Useful for topic searches ('artificial intelligence', 'border security', etc.).
        schema:
          type: string
      - name: origin_chamber
        in: query
        required: false
        description: Filter to bills originating in one chamber.
        schema:
          type: string
          enum:
          - House
          - Senate
      - name: since
        in: query
        required: false
        description: 'Latest-action date lower bound (ISO YYYY-MM-DD inclusive). Useful for ''what''s moved recently''. NOTE: this filters the most-recent floor/committee action, which can move with activity even on a bill introduced a year ago. For ''introduced in the last N months'' questions, use introduced_since instead.'
        schema:
          type: string
      - name: until
        in: query
        required: false
        description: Latest-action date upper bound (ISO YYYY-MM-DD inclusive).
        schema:
          type: string
      - name: introduced_since
        in: query
        required: false
        description: Introduction-date lower bound (ISO YYYY-MM-DD inclusive). The right filter for 'bills introduced in the last N months' — distinct from since/until, which track latest action. Older bill records may have an empty introduction_date if they were ingested before that field was added; those will be excluded from introduced_since/introduced_until results until the bill is re-scraped.
        schema:
          type: string
      - name: introduced_until
        in: query
        required: false
        description: Introduction-date upper bound (ISO YYYY-MM-DD inclusive).
        schema:
          type: string
      - name: sort_by
        in: query
        required: false
        description: 'Sort key. Default: latest_action_date (most recently active first). Use introduction_date to sort by when the bill was originally introduced.'
        schema:
          type: string
          enum:
          - latest_action_date
          - update_date
          - introduction_date
      - name: sort_order
        in: query
        required: false
        description: 'Default: desc.'
        schema:
          type: string
          enum:
          - asc
          - desc
      - name: limit
        in: query
        required: false
        description: Maximum bills to return. Default 50, max 500.
        schema:
          type: integer
      responses:
        '200':
          description: 'JSON envelope: { results: [...], count, has_more }.'
        '400':
          description: Invalid parameter.
        '401':
          description: Missing or invalid API key.
        '402':
          description: This tool requires a higher plan (upgrade_required). Retrying will not help.
        '429':
          description: Tier rate/quota limit reached (rate_limited). Retry-After points at the reset.
      tags:
      - Bills
components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key