gov.fec-expenditures

Search FEC Schedule B — every itemized disbursement (spend, vendor payment, operating expenditure, contribution out, transfer) made by a federal political committee (>157M rows). Filter by committeeId, recipient name / city / state, disbursement purpose category (Administrative / Fundraising / Media / Polling / Salary / Travel / Operating / Contribution / Loan / etc.), description text, amount range, cycle, date range. Sort by date or amount. Every row carries: who got paid, when, how much, for what, with link to underlying PDF. The natural pair with /api/gov/fec-contributions for following the money on both sides of any federal committee.

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

Overview

The fec expenditures API is a pay-per-call gov endpoint built for AI agents and autonomous software. Search FEC Schedule B — every itemized disbursement (spend, vendor payment, operating expenditure, contribution out, transfer) made by a federal political committee (>157M rows).

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 fec expenditures 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
committeeIdstring
match ^C\d{8}$
recipientNamestring
min 1 chars · max 120 chars
recipientCitystring
min 1 chars · max 80 chars
recipientStatestring
min 2 chars · max 2 chars · match ^[A-Za-z]{2}$
disbursementPurposeCategorystring
min 1 chars · max 80 chars
disbursementDescriptionstring
min 1 chars · max 160 chars
minAmountnumber
min 0
maxAmountnumber
min 0
twoYearTransactionPeriodinteger
min 1980 · max 2100
minDatestring
match ^\d{4}-\d{2}-\d{2}$
maxDatestring
match ^\d{4}-\d{2}-\d{2}$
perPageinteger
min 1 · max 100
pageinteger
min 1
sortFieldstring
one of: disbursement_date | disbursement_amount
sortDirectionstring
one of: asc | desc

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/gov/fec-expenditures?committeeId=example&recipientName=example&recipientCity=example&recipientState=xx&disbursementPurposeCategory=example&disbursementDescription=example&minAmount=0&maxAmount=0&twoYearTransactionPeriod=1980&minDate=2024-01-01&maxDate=2024-01-01&perPage=25&page=1&sortField=disbursement_date&sortDirection=asc'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/gov/fec-expenditures?committeeId=example&recipientName=example&recipientCity=example&recipientState=xx&disbursementPurposeCategory=example&disbursementDescription=example&minAmount=0&maxAmount=0&twoYearTransactionPeriod=1980&minDate=2024-01-01&maxDate=2024-01-01&perPage=25&page=1&sortField=disbursement_date&sortDirection=asc' \
  -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/fec-expenditures?committeeId=example&recipientName=example&recipientCity=example&recipientState=xx&disbursementPurposeCategory=example&disbursementDescription=example&minAmount=0&maxAmount=0&twoYearTransactionPeriod=1980&minDate=2024-01-01&maxDate=2024-01-01&perPage=25&page=1&sortField=disbursement_date&sortDirection=asc'
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.fecExpenditures({
  "committeeId": "example",
  "recipientName": "example",
  "recipientCity": "example",
  "recipientState": "xx",
  "disbursementPurposeCategory": "example",
  "disbursementDescription": "example",
  "minAmount": 0,
  "maxAmount": 0,
  "twoYearTransactionPeriod": 1980,
  "minDate": "2024-01-01",
  "maxDate": "2024-01-01",
  "perPage": 25,
  "page": 1,
  "sortField": "disbursement_date",
  "sortDirection": "asc"
})

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.fec_expenditures(committeeId="example", recipientName="example", recipientCity="example", recipientState="xx", disbursementPurposeCategory="example", disbursementDescription="example", minAmount=0, maxAmount=0, twoYearTransactionPeriod=1980, minDate="2024-01-01", maxDate="2024-01-01", perPage=25, page=1, sortField="disbursement_date", sortDirection="asc")

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.fec-expenditures",
    "arguments": {
      "committeeId": "example",
      "recipientName": "example",
      "recipientCity": "example",
      "recipientState": "xx",
      "disbursementPurposeCategory": "example",
      "disbursementDescription": "example",
      "minAmount": 0,
      "maxAmount": 0,
      "twoYearTransactionPeriod": 1980,
      "minDate": "2024-01-01",
      "maxDate": "2024-01-01",
      "perPage": 25,
      "page": 1,
      "sortField": "disbursement_date",
      "sortDirection": "asc"
    }
  }
}

Response

FieldTypeDescription
okboolean
one of: true
itemsarray
totalintegerTotal matching rows upstream; null when unknown.
sourceobject
pageobject
Example response datajson
{
  "ok": true,
  "items": [
    {}
  ],
  "total": 1,
  "source": {
    "provider": "example",
    "url": "example",
    "license": "example"
  },
  "page": {
    "number": 1,
    "size": 1,
    "pages": 1
  }
}

FAQ

Do I need an API key to use the fec expenditures API?
No. gov.fec-expenditures 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 fec expenditures 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 fec expenditures 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.fec-expenditures 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: fec expenditures api · gov fec expenditures api · fec expenditures api for ai agents · x402 gov api · fec expenditures api no api key · pay per call fec expenditures api · gov api