For AI agents: the documentation index is /docs/llms.txt, and this page is available as Markdown.
Missing data
West Kite never fills a gap with a guess or a zero. When a field or a result isn't there, the response says so in missing, with a reason.
How it looks
{
"data": { "owner": { "name": null } },
"missing": [
{ "field": "owner.name", "reason": "not_published", "note": "Los Angeles County rolls omit owner names." }
],
"billing": { "operation_id": "op_5e7a…", "operation": "property", "charged_usd": 0.01, "balance_usd": 9.99 },
"request_id": "req_8c1d…"
}
Each entry has the field (a path into data), a reason and sometimes a note in plain words.
Reasons
| Reason | Means | What to do |
|---|---|---|
not_covered |
West Kite hasn't loaded that place, or that kind of record for that place (such as a county's permits), yet. | Check coverage, and file a data request. |
not_published |
The source doesn't release it, such as sale prices in states that don't disclose them. | Say it's unpublished. Don't estimate it. |
not_on_record |
Nothing was filed, such as a deed recorded without a price. | Say there's no record. |
not_found |
A search, lookup or research run found nothing. | Try another spelling or ID. Research and contacts that find nothing cost nothing. |
temporarily_unavailable |
The source didn't answer this time. | Retry that part on its own later. |
Missing is never zero
A missing sale price is not a $0 sale, and a missing building size is not an empty lot. When you show West Kite data, show a missing field as missing, and keep the reason if you can. When you filter with find, a property with no value for a field doesn't match a range on it; use is unknown to find those properties on purpose.
What each county publishes varies. Coverage gives the share of properties with each field, county by county.