anshchokshi

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.

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.