Public-record data tools

The tools, as a register.

Each tool does one thing against public records and hands back clean rows. Every row carries the source it came from, so you can check the work. You pay per result, by the thousand. A run that finds nothing costs nothing.

22tools in the register
per 1,000how each tool meters
$0.00an empty run
sourceon every row
How a tool runs

One contract, every tool.

The same contract holds for every entry, whether it touches DNS, a registry, or a federal dataset.

R-01

One job, one input shape

You hand a tool the one input it asks for: a list of domains, a ZIP, a VIN, a date window. No tool tries to be three tools.

in: one list • out: rows
R-02

Clean rows, not a blob

Output is a flat table you can load straight into a sheet, a database, or the next tool. Field names are stable.

format: CSV or JSON
R-03

A source on every row

Each row names where it came from. If we cannot point to a source, the row does not ship. We do not guess a value to fill a gap.

field: source_url
R-04

Pay for results, not attempts

You are metered on rows delivered, by the thousand. A failed lookup is our cost to carry, not yours.

meter: per 1,000
A sample of the register

A few of the tools, and what they read.

Twenty-two tools ship today against public records. Each links to its own listing; ask for an API key to run any of them.

ToolWhat it readsPrice
T-01Bulk DNS LookupA, AAAA, MX, NS, TXT, CNAME, SOA for a whole list of domains, with SPF and DMARC parsed out.$0.40 / 1k
T-02RDAP Domain LookupRegistration data over RDAP: registrar, status codes, public create and expiry dates.$0.80 / 1k
T-03Verified B2B Email FinderBusiness emails published on a company’s own pages, verified for deliverability before they ship.per lead
T-04VIN DecoderDecodes a VIN to its specs against the public NHTSA dataset.per result

Ask for the full register and an API key