
Nico Poland
I enjoy building small tools that perform structured, niche tasks. I <3 data parsing.
npolandata
Joined September 2026
ACTOR STATS
4 public Actors
8 total users
1 monthly user
>99% runs succeeded
I build small tools that do one job properly.
Most of them turn official public records into clean, typed rows: property assessments, contractor licences, vehicle safety recalls. Some never touch a network at all. What they have in common is how they are built, not what they are about.
One job each. A tool that answers one question is faster, easier to trust, and much easier for an agent to pick correctly than a toolkit with twelve switches.
The boring parts get done. Dates normalised to ISO 8601, even when a source uses two different formats in two endpoints. Whitespace collapsed. Missing values left missing rather than blanked, because "not recorded" and "empty" are different facts. Source, licence and timestamp on every row, so attribution survives an export to CSV.
Limits up front. Every README says what the tool does not cover, how stale the data can get, and where the source itself has gaps. Sample outputs are copied from real runs, never written by hand. If something only holds for one state, or one year, it says so.
You pay for results. Charging is per record delivered. Failed runs cost nothing. Rows that come back saying "no match" or "that code is not valid" are free, because you should not have to pay to be told your input was wrong. And there is no per-run start fee beyond Apify's own $0.00005, which matters a lot if you are calling one lookup at a time.
No logins, no CAPTCHA solving, nothing behind a paywall. No personal contact details, no reverse lookup from a person to their records, and no un-redacting what a publisher chose to redact. These tools read business and property records, not people.
Open an issue on the tool. Sources change shape without warning, and I would much rather hear it from you than read it in a rating.