Public records, without the scraper.
Federal registers, procurement, and open-data portals, as structured APIs with published availability signals. These are the cleanest sources on the web to depend on, and what compliance, procurement, and public-records products run on.
What teams build first
Three workflows, one stable interface.
Compliance change monitoring
Watch a regulation, docket, or guidance page and get told when it changes, with a diff and the source it came from. The clearest recurring pain for regulatory and compliance teams.
eCFR · regulations · agency registers
See the eCFR schema →Procurement & vendor tracking
Track new solicitations, award changes, and vendor status across federal and state/local procurement. Federal is well-served; the state and local long tail is where scrapers fall over.
USAspending federal awards
See the awards schema →Public records & open data
Query structured records across federal, state, and city open-data portals, the same JSON shape whether it's a federal dataset or a municipal Socrata API. Build the workflow once instead of once per portal.
Federal · state · city open-data portals
Browse the open-data sources →How it works
From a public site to structured JSON.
Find the source in the catalog, call the hosted API with the endpoint and params, and get back structured JSON. No HTML to parse, no scraper to babysit. These are real calls, with their real responses.
Compliance · Track current CFR titles and freshness
POST api.everfetch.tech/v1/fetch
{
"site": "www.ecfr.gov",
"endpoint": "titles"
}
→ 200 OK
{
"titles": [
{
"number": 1,
"name": "General Provisions",
"latest_amended_on": "2022-12-29",
"up_to_date_as_of": "2026-06-10"
},
{
"number": 2,
"name": "Federal Financial Assistance",
"latest_amended_on": "2026-04-09",
"up_to_date_as_of": "2026-06-10"
}
]
}Procurement · Search recent federal awards
POST api.everfetch.tech/v1/fetch
{
"site": "api.usaspending.gov",
"endpoint": "award_search",
"params": {
"start_date": "2025-10-01",
"end_date": "2026-06-01",
"award_type_codes": ["A","B","C","D"],
"page": 1,
"limit": 10
}
}
→ 200 OK
{
"results": [
{ "Award ID": "Z506", "Recipient Name": "THE BOEING COMPANY", "Award Amount": 76851.78 },
{ "Award ID": "Z35J", "Recipient Name": "HAMILTON SUNDSTRAND CORPORATION", "Award Amount": 116509.50 }
]
}Why public records
The data scrapers should be able to read, and can't.
Availability you can inspect
Each endpoint can publish hosted availability and verification signals. Coverage varies by source and is still expanding.
Provenance on every response
Each entry carries its source, endpoint surface, and last-verified time. You can trace a value back to where it came from, which is what compliance and audit work requires.
A clean legal posture
Public records and factual interoperability metadata about public endpoints. We publish a takedown process and an exclusion list, and never catalog what we have been asked to leave alone.
One shape across jurisdictions
The same structured JSON whether you are reading a federal register or a city open-data portal, so you build the workflow once instead of per portal.
Need a source we don't cover yet?
Tell us the portal, the records you need, and the shape you want back. We run paid source pilots: a fixed-fee integration of the sources you depend on, which then enter the catalog as monitored connectors. Secretary-of-State business filings and multi-state KYB are an active area we expand through these pilots — tell us which states and records you need.