gov.congress-amendment

Look up or list US Congressional amendments via Congress.gov. Pass congress + type + number to fetch a single amendment with full sponsor + action history. Or filter list by congress + type + date range. Amendment types: hamdt=House Amendment, samdt=Senate Amendment, suamdt=Senate Unprinted Amendment.

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

Overview

The congress amendment API is a pay-per-call gov endpoint built for AI agents and autonomous software. Look up or list US Congressional amendments via Congress.gov.

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 amendment 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
congressinteger
min 1 · max 200
typestring
one of: hamdt | samdt | suamdt
numberinteger
min 1
fromDatestring
match ^\d{4}-\d{2}-\d{2}$
toDatestring
match ^\d{4}-\d{2}-\d{2}$
limitinteger
min 1 · max 250
offsetinteger
min 0

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/gov/congress-amendment?congress=1&type=hamdt&number=1&fromDate=2024-01-01&toDate=2024-01-01&limit=25&offset=0'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/gov/congress-amendment?congress=1&type=hamdt&number=1&fromDate=2024-01-01&toDate=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-amendment?congress=1&type=hamdt&number=1&fromDate=2024-01-01&toDate=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.congressAmendment({
  "congress": 1,
  "type": "hamdt",
  "number": 1,
  "fromDate": "2024-01-01",
  "toDate": "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_amendment(congress=1, type="hamdt", number=1, fromDate="2024-01-01", toDate="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-amendment",
    "arguments": {
      "congress": 1,
      "type": "hamdt",
      "number": 1,
      "fromDate": "2024-01-01",
      "toDate": "2024-01-01",
      "limit": 25,
      "offset": 0
    }
  }
}

Response

FieldTypeDescription
okboolean
one of: true
itemsarray
totalintegerTotal matching rows upstream; null when unknown.
sourceobject
metaobject
Example response datajson
{
  "ok": true,
  "items": [
    {}
  ],
  "total": 1,
  "source": {
    "provider": "example",
    "url": "example",
    "license": "example"
  },
  "meta": {
    "mode": "lookup"
  }
}

FAQ

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