Update to SPACEXPLORATION

{
  "description": "Find and compare commercial real estate on SPACEXPLORATION — industrial, office, retail, multifamily, and land, for sale or lease, anywhere in the US. Use when the user wants to search for commercial property, filter by price, size, cap rate, location, or building features, look up a specific listing, compare listings side by side, or check the public data on any US building by its address (flood zone, hazard risk, EPA records, demographics, county record), listed or not. Searching needs no account; a building lookup asks the user to sign in to SPACEXPLORATION in the browser.",
  "included_files": [],
  "name": "search-listings",
  "skill_md_contents": "---\nname: search-listings\ndescription: Find and compare commercial real estate on SPACEXPLORATION — industrial, office, retail, multifamily, and land, for sale or lease, anywhere in the US. Use when the user wants to search for commercial property, filter by price, size, cap rate, location, or building features, look up a specific listing, compare listings side by side, or check the public data on any US building by its address (flood zone, hazard risk, EPA records, demographics, county record), listed or not. Searching needs no account; a building lookup asks the user to sign in to SPACEXPLORATION in the browser.\n---\n\n# Search SPACEXPLORATION listings\n\nThe user's explicit instructions take precedence over this skill.\n\nSPACEXPLORATION is an MLS for commercial property. Every read tool works without signing in, except looking up a building by address: the first time it runs, the user is asked to sign in to SPACEXPLORATION in the browser.\n\n## Choose a starting point\n\n- **The user asks in plain language** (\"warehouses near Denver under $5M with dock doors\"): call `interpret_search` with their sentence as `prompt`. Pass the `filters` it returns to `search_listings`. If it also returns `bounds`, pass those as well. Bounds hold the \"near <place>\" part, and without them the search covers the whole country.\n- **You need precise or repeated control:** call `get_registry` once and build `filters` yourself. Anonymous callers can make about 6 `interpret_search` calls per minute, so do this for follow-up refinements too.\n\n## Build filters from the registry\n\n`get_registry` returns `attributes` and `sort_options`. Each attribute's `field` is the only valid filter key. Shape each value by the attribute's `filter`:\n\n| `filter` | Filter value |\n| --- | --- |\n| `range` | `{\"min\": …, \"max\": …}`. Either bound is optional. Dates take ISO dates, e.g. `{\"min\": \"2027-01-01\"}` |\n| `any_of` | array of the attribute's `values`, e.g. `[\"industrial\", \"office\"]`. Where `values` are `{value, label}` pairs, send the `value` |\n| `boolean` | `true` or `false` |\n| `equals` | a single exact value |\n\n- `applies_to` and `applies_to_listing_type` say which property and listing types a field is meaningful for. For example, cap rate applies to sale listings and lease structure to lease listings. Filtering on a field that doesn't apply silently excludes every other type.\n- Location: `state` takes two-letter codes (`[\"CO\"]`), and `city` and `county` take exact names. Use them when the user names a place and you have no `bounds`; without a location filter or `bounds` the search covers the whole country.\n- `sort` must be one of `sort_options`, e.g. `price:asc`, `attr_cap_rate:desc`, or `views_30d:desc` for popular listings.\n- `query` is free text matched against address, city, and keywords. Use it for a street address or a term that isn't a registry field.\n\n```json\n{\n  \"filters\": {\n    \"property_type\": [\"industrial\"],\n    \"listing_type\": [\"sale\"],\n    \"price\": { \"max\": 5000000 },\n    \"attr_industrial_dock_doors\": { \"min\": 1 }\n  },\n  \"bounds\": { \"sw_lat\": 39.4, \"sw_lng\": -105.3, \"ne_lat\": 40.1, \"ne_lng\": -104.6 },\n  \"sort\": \"price:asc\"\n}\n```\n\n## Read results\n\n`search_listings` returns `hits`, `facets` (counts per value, useful for suggesting refinements), `found`, `page`, and `last_page`. Pass `page` to page through results; there are 24 hits per page.\n\nEach hit carries a `hashid`, the listing page `url`, and two timestamps: `listed_at` (when it went live) and `updated_at` (when it last changed). Call `get_listing` with the `hashid` for the full record: pricing, every populated attribute with its label and unit, parcel and public-record data, photos, and documents. Broker contact details appear only when the caller is allowed to see them.\n\nLink the user to a listing with its `url`. Don't build the link yourself.\n\n## Look up a building by address\n\nWhen the user asks about a specific building, on the market or not (\"is 910 Elysian Fields Ave in a flood zone?\", \"what do we know about this property?\"), call `look_up_parcel` with its full street address, street number included. The first time it runs, the user is asked to sign in to SPACEXPLORATION in the browser. A road, a town, or a partial address is refused, so ask for the street number.\n\nIt returns the building page `url` to share, `details` keyed by registry path (FEMA flood zone, natural hazard risk, EPA records nearby, Census demographics, access and amenities), `public_record` (the county's owner, values, taxes, tax lots, and recorded sales, each figure with a numbered source) where research has found it, and any live `listings` in it (pass a `hashid` to `get_listing`).\n\nA building looked up for the first time fills in over a minute or more. While `status.gathering` or `status.researching_county_record` is true, follow `status.note`: check on it with `get_parcel` and the returned `parcel.hashid` instead of repeating the lookup. `get_parcel` starts nothing and works without signing in.\n\n## Answer questions about SPACEXPLORATION\n\nAsked how SPACEXPLORATION works, what it covers, or another question about the service itself rather than a property? Call `get_faq`, answer from it, and link the entry's `url`.\n\n## Report honestly\n\n- Say how many listings matched (`found`), and when a search came back empty, say which filter was most restrictive.\n- When recency matters, say when a listing was listed or last updated.\n- Present only values the tools returned. A missing attribute means the listing doesn't state it. Don't fill it in.\n- For a building, `public_record` cites its sources by number: name the county source when you quote a figure, and say a field is unknown when it is missing rather than estimating it.\n- Some attributes are computed from public sources: flood zone, census demographics, walk and transit scores, proximity, market medians, and `attr_record_*` assessor data. When those matter to the decision, say they come from public data, not from the broker.\n"
}