Data APIs on public records

Public records, turned into clean APIs.

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 and change alerts for freight brokers and the software they use. You can get it on RapidAPI, Apify, Zyla and Postman.

See the APIs Read the FMCSA Carrier Check docs

Official sources. Plain JSON. Explainable results.

FMCSA CARRIER CHECK / GET /v1/check200 OK

USDOT 1398624 · PA AF60214

Is this truck good to load?

GOOD

GET /v1/check?usdot=1398624&plate=AF60214&state=PA

01Operating authorityPASS

02Insurance vs. requiredPASS

03Truck matches carrierPASS

04Data sourceWARN

"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.

ONE REQUESTGOOD OR BAD, WITH REASONS

LIVE ON RAPIDAPIAPIFY STOREZYLA API HUBPOSTMAN API NETWORK

01 The APIs

Available now.

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.

LIVEAPI / 01 · TRANSPORTATION

FMCSA Carrier Check API

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, run 100 carriers in a single request, or put your carriers on a watchlist and get change alerts within 24 hours by API pull or signed webhook.

Change alerts within 24 hoursGood/bad pickup checkPlate & VIN to carrierInsurance vs. requiredBatch of 100Daily FMCSA data

Details and docs

GET IT ON

RapidAPIAPI marketplace

ApifyNo-code Actor

Zyla API HubAPI hub subscription

PostmanRun in Postman

API / 02

Next API in progress. Have a public dataset you wish were a clean API? Tell me about it.

02 How they're built

Less noise.
More signal.

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.

Start from official sources

Government datasets and official APIs, read directly. No scraping behind logins, and platform terms taken seriously.

Answer the real question

Normalize messy records into predictable JSON, with explainable flags and verdicts instead of a black-box score.

Keep it current

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

Early research.

Areas under investigation, not products. If one of these is a problem you have, I'd like to hear about it.

EXPLORING

Etsy market signals

How public marketplace signals could help independent sellers spot shifting search terms and crowded categories.

EXPLORING

Mobile app ecosystem

Public signals around app releases, reviews and technology adoption, for sharper competitive research.

04 The standard

Useful data starts
with good judgment.

Responsible sources

Public information and official APIs, with platform terms and access limits taken seriously.

Clear provenance

Every response says where its data came from and when, and what it can and cannot tell you.

Explainable results

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?

Let's talk
about your data.

Questions about an API, higher volumes, or a public dataset you wish had a clean API. Email me directly.

[email protected]