
OpenFolio
API for Public Records
For the last few months I’ve been building OpenFolio, a single API and MCP server over US public and government records: state business registrations, property and parcel records, liens, licenses, permits, government contracts and spending, nonprofit filings, and more. Right now it’s 80M+ records across 27 states and growing.
The hard part, and the reason this doesn’t already exist, isn’t collecting the data. It’s the join. The same business shows up as an LLC in a state registry, an owner on a county parcel, a vendor in federal spending, and a licensee in a permit system, and none of those records share an ID. OpenFolio resolves them into one entity. In our data, one construction company resolves across 16 separate datasets. That entity resolution is the whole product.
It’s MCP-native, so you can point a Claude or ChatGPT agent straight at it and have it pull ground-truth public records mid-task, no scraping, no schema-wrangling. There’s also a REST API and Python/JS SDKs.
Free tier is 500 credits, no card. I’d love feedback from other builders: what public-record data would you actually want joined and queryable, and what would you build on it?
About
It’s something I wish existed. I’d spent months doing this internally for a separate project, which is when I realized how much easier it would’ve been if I’d had an api to call.

5 Comments
This data can be super valuable. I'm interested to take a closer look at your solution. If you'd like, I can do a live video review of OpenFolio with realtime reactions and feedback. I do these videos for free, as a way to connect with more founders. I send a 2 minute preview. To unlock the full video, you only need to give feedback to another product on BetaBloom. It's a pretty good deal I think. Sound good?
Sure let’s connect. That would be interesting.
Did you get a chance to watch the video review? Was it helpful?
Here is a free video review with feedback. Let me know if this is helpful. https://betabloom.app/v/1ydiBQh5_MZdLjs_vkcwqcnXOwamlSoh
The distinction between collecting records and resolving them into a single entity is what stood out.
That changes the product from being a data source into an interpretation layer over fragmented public records.