Rendered at 02:24:19 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
srikanthkasa 5 hours ago [-]
the problem usually isn’t missing facts. it’s that null means different things in different counties — no flood map vs no flood risk, wrong parcel, owner fields that don’t map cleanly.
if the API returns absent/failed instead of making the model guess, that’s actually a really good design choice.
curious how often those cases show up on normal residential parcels vs the messier commercial/infill sites.
ansh_chokshi 3 hours ago [-]
in our fetch api every field comes with ok / absent / failed. it never returns a bare null and lets you/your agent assume. credit is not charged in case the api returns absent value.
for ask api, the null is shown to the model as value: NULL plus an instruction — "acknowledge the gap explicitly. do not state, estimate, or infer a value for it from general knowledge or from the coordinate." so models never make any data up.
empty fields are rare on houses and commercial lots (~5%) and common on rural land (~29%), but on rural land empty usually means "nothing's there," while on houses and lots it usually means "the county didn't publish it.
sgtwompwomp 6 hours ago [-]
Awesome work. If I understand correctly, your service essentially runs a bunch of web agents to maintain this dataset and keep it up to date and accurate, and we access through your API / MCP?
ansh_chokshi 5 hours ago [-]
Thank you! and correct, we have long running agents that Source → Crawl → Evaluate → Index → Retrieve → Contract this data.
O(1 crawler) for the web vs O(fields × jurisdictions) for real-world data. So we have to build a lot of unique crawlers.
cornholio 5 hours ago [-]
It would be good to also have a non-LLM version of the pitch, for some people building in the space it's a bad signal. It's associated with zero value "let my agent build something over the weekend" projects that all make these grandiose claims.
if the API returns absent/failed instead of making the model guess, that’s actually a really good design choice.
curious how often those cases show up on normal residential parcels vs the messier commercial/infill sites.
for ask api, the null is shown to the model as value: NULL plus an instruction — "acknowledge the gap explicitly. do not state, estimate, or infer a value for it from general knowledge or from the coordinate." so models never make any data up.
empty fields are rare on houses and commercial lots (~5%) and common on rural land (~29%), but on rural land empty usually means "nothing's there," while on houses and lots it usually means "the county didn't publish it.
O(1 crawler) for the web vs O(fields × jurisdictions) for real-world data. So we have to build a lot of unique crawlers.