Data APIs on public records
Siftly Data builds small, focused APIs on top of official public data, and right now building APIs is most of what I do. The first one, the FMCSA Carrier Check API, turns federal trucking records into one-call answers for freight brokers and the software they use. You can get it on RapidAPI, Apify, Zyla and Postman.
Official sources. Plain JSON. Explainable results.
USDOT 1398624 · PA AF60214
GET /v1/check?usdot=1398624&plate=AF60214&state=PA
"Good: authority active, insurance OK, truck matches (4 inspections, last seen 2025-12-23). 1 warning."
Abridged from the documented example response. FMCSA public data, for information only.
01 The APIs
Each API is listed on the marketplaces developers already buy from, so you can subscribe, get a key and pay through the one you prefer. Same data, same endpoints everywhere.
Carrier and truck verification
Vet a US trucking carrier in one call. Send a USDOT number, MC docket, company name, license plate or VIN and get clean JSON: operating authority, insurance on file vs. required, roadside inspection history and plain-language risk flags. Check whether the truck at your dock really belongs to the carrier you booked, or run 100 carriers in a single request.
Details and docsNext API in progress. Have a public dataset you wish were a clean API? Tell me about it.
02 How they're built
Public data is full of useful answers. It rarely arrives in a form your code can use. Each Siftly API closes that gap for one specific question.
Government datasets and official APIs, read directly. No scraping behind logins, and platform terms taken seriously.
Normalize messy records into predictable JSON, with explainable flags and verdicts instead of a black-box score.
Data refreshed as often as the source allows, with a freshness timestamp on every response so you know how current an answer is.
03 Also exploring
Areas under investigation, not products. If one of these is a problem you have, I'd like to hear about it.
04 The standard
Public information and official APIs, with platform terms and access limits taken seriously.
Every response says where its data came from and when, and what it can and cannot tell you.
Flags and verdicts that name the rule behind them, never a black-box score you have to take on faith.
Questions, bugs or a data need?
Questions about an API, higher volumes, or a public dataset you wish had a clean API. Email me directly.
[email protected]
