law.federal-register

Search the US Federal Register — proposed rules, final rules, notices, and presidential documents. Filter by free-text term, document type (RULE/PRORULE/NOTICE/PRESDOCU), agency slug (e.g., epa, fda, sec), and publication date range. Returns document_number, type, title, abstract, FR citation, agencies, publication_date, effective_on, comments_close_on, htmlUrl, pdfUrl, rawTextUrl. Public-domain US government data. Real-time — published daily, past LLM training cutoff.

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

Overview

The federal register API is a pay-per-call law endpoint built for AI agents and autonomous software. Search the US Federal Register — proposed rules, final rules, notices, and presidential documents.

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 federal register data source for an agent tool-use loop, an MCP host, or a backend that needs law data on demand without onboarding to yet another vendor portal.

Use cases

Parameters

NameTypeDescription
qrequiredstring
min 1 chars · max 500 chars
typestring
one of: RULE | PRORULE | NOTICE | PRESDOCU
agencystring
match ^[a-z0-9-]{2,60}$
sincestring
match ^\d{4}-\d{2}-\d{2}$
untilstring
match ^\d{4}-\d{2}-\d{2}$
limitinteger
min 1 · max 20

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/law/federal-register?q=example&type=RULE&agency=example&since=2024-01-01&until=2024-01-01&limit=10'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/law/federal-register?q=example&type=RULE&agency=example&since=2024-01-01&until=2024-01-01&limit=10' \
  -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/law/federal-register?q=example&type=RULE&agency=example&since=2024-01-01&until=2024-01-01&limit=10'
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.law.federalRegister({
  "q": "example",
  "type": "RULE",
  "agency": "example",
  "since": "2024-01-01",
  "until": "2024-01-01",
  "limit": 10
})

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.law.federal_register(q="example", type="RULE", agency="example", since="2024-01-01", until="2024-01-01", limit=10)

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": "law.federal-register",
    "arguments": {
      "q": "example",
      "type": "RULE",
      "agency": "example",
      "since": "2024-01-01",
      "until": "2024-01-01",
      "limit": 10
    }
  }
}

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": {
    "query": {
      "term": "example",
      "type": "example",
      "agency": "example",
      "since": "example",
      "until": "example",
      "limit": 1
    }
  }
}

FAQ

Do I need an API key to use the federal register API?
No. law.federal-register 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 federal register API cost?
$0.0010 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 federal register 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 law.federal-register 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: federal register api · law federal register api · federal register api for ai agents · x402 law api · federal register api no api key · pay per call federal register api · law api