gov.congress-filings

Track US House members' financial-disclosure filings — including Periodic Transaction Reports (PTRs), the STOCK Act filings where members must disclose their stock trades within 45 days. Defaults to PTRs; pass type=annual|candidate|amendment|all to see other disclosure kinds. Filter by member name (q), 2-letter state, filing year, or filing-date range (dateFrom/dateTo). Each result gives the member, state + district, filing type (with a readable label), the filing/disclosure date, and a direct link to the source document (docUrl). The envelope total is the full count matching your filter — so q=Pelosi or year=2026 answers 'how many PTRs did they file'. Covers 2008→present (~8,200 PTRs), refreshed daily so new filings appear within ~a day. Note: by law trades are disclosed up to 45 days after they happen — this is current-to-the-filing, not real-time. Data: US House Clerk (public domain).

price
$0.0012 USDC per call
method
GET/api/gov/congress-filings
payment
x402 v2 · USDC on Base (EIP-3009) or Solana (SPL transfer)
auth
None. Sign the payment, retry with PAYMENT-SIGNATURE.

Overview

The congress filings API is a pay-per-call gov endpoint built for AI agents and autonomous software. Track US House members' financial-disclosure filings — including Periodic Transaction Reports (PTRs), the STOCK Act filings where members must disclose their stock trades within 45 days.

There is no signup and no API key. An agent (or any HTTP client) hits the endpoint, receives an x402 "402 Payment Required" challenge, signs a sub-cent USDC payment on Base or Solana, and retries — the data comes back on the paid request. That makes it a drop-in congress filings data source for an agent tool-use loop, an MCP host, or a backend that needs gov data on demand without onboarding to yet another vendor portal.

Use cases

Parameters

NameTypeDescription
qstring
min 1 chars · max 80 chars
statestring
min 2 chars · max 2 chars
typestring
min 1 chars · max 40 chars
chamberstring
one of: house | senate
yearinteger
min 2008 · max 2100
dateFromstring
match ^\d{4}-\d{2}-\d{2}$
dateTostring
match ^\d{4}-\d{2}-\d{2}$
limitinteger
min 1 · max 100
offsetinteger
min 0 · max 100000

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/gov/congress-filings?q=example&state=xx&type=example&chamber=house&year=2008&dateFrom=2024-01-01&dateTo=2024-01-01&limit=25&offset=0'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/gov/congress-filings?q=example&state=xx&type=example&chamber=house&year=2008&dateFrom=2024-01-01&dateTo=2024-01-01&limit=25&offset=0' \
  -H 'PAYMENT-SIGNATURE: <base64-json-payload>'

# Or use the canonical runner (handles probe → sign → retry):
#   EVM_PRIVATE_KEY=0x... node --env-file=.env.local \
#     --experimental-strip-types scripts/x402-pay.ts \
#     'https://2s.io/api/gov/congress-filings?q=example&state=xx&type=example&chamber=house&year=2008&dateFrom=2024-01-01&dateTo=2024-01-01&limit=25&offset=0'
TypeScript / Node — @2sio/sdktypescript
import { TwoS } from '@2sio/sdk'

const client = new TwoS({
  privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})

const result = await client.gov.congressFilings({
  "q": "example",
  "state": "xx",
  "type": "example",
  "chamber": "house",
  "year": 2008,
  "dateFrom": "2024-01-01",
  "dateTo": "2024-01-01",
  "limit": 25,
  "offset": 0
})

console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)
Python — 2siopython
import os
from twosio import TwoS

client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])

result = client.gov.congress_filings(q="example", state="xx", type="example", chamber="house", year=2008, dateFrom="2024-01-01", dateTo="2024-01-01", limit=25, offset=0)

print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)
MCP — Claude Desktop / AgentKit / any MCP hostjson
// 1. Add @2sio/mcp to your MCP host config (Claude Desktop example below).
//    EVM_PRIVATE_KEY funds x402 payments per call.

// claude_desktop_config.json
{
  "mcpServers": {
    "2sio": {
      "command": "npx",
      "args": ["-y", "@2sio/mcp"],
      "env": { "EVM_PRIVATE_KEY": "0x..." }
    }
  }
}

// 2. Once the server is running, agents call this tool via standard MCP:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "gov.congress-filings",
    "arguments": {
      "q": "example",
      "state": "xx",
      "type": "example",
      "chamber": "house",
      "year": 2008,
      "dateFrom": "2024-01-01",
      "dateTo": "2024-01-01",
      "limit": 25,
      "offset": 0
    }
  }
}

Response

FieldTypeDescription
okboolean
one of: true
itemsarray
totalintegerTotal matching rows upstream; null when unknown.
sourceobject
Example response datajson
{
  "ok": true,
  "items": [
    {
      "docId": "example",
      "chamber": "example",
      "memberName": "example",
      "state": "example",
      "district": "example",
      "filingType": "example",
      "filingTypeLabel": "example",
      "filingYear": 1,
      "filingDate": "example",
      "docUrl": "example",
      "tradesParsed": false
    }
  ],
  "total": 1,
  "source": {
    "provider": "example",
    "url": "example",
    "license": "example"
  }
}

FAQ

Do I need an API key to use the congress filings API?
No. gov.congress-filings is x402-native — there is no signup and no API key. Your client makes the call, receives a 402 with payment requirements, signs a USDC payment, and retries. Funds come from a wallet you control.
How much does the congress filings API cost?
$0.0012 USDC per call, charged per request. There are no monthly fees, seats, or minimums — you pay only for the calls you make.
Can I try the congress filings API for free first?
Yes. Add ?trial=1 (or the header X-2s-Trial: 1) to get a free real call per endpoint per hour, so you can verify the response shape before wiring payment.
Which networks and tokens are supported?
USDC on Base (via EIP-3009 transferWithAuthorization) or Solana (SPL transfer), using the open x402 payment protocol.
How do I call gov.congress-filings from an AI agent or MCP host?
Use @2sio/sdk (TypeScript), 2sio (Python), or the @2sio/mcp server for any MCP host — each handles the probe → sign → retry loop for you. See the code samples on this page.

Discovery

Related: congress filings api · gov congress filings api · congress filings api for ai agents · x402 gov api · congress filings api no api key · pay per call congress filings api · gov api