# CoStar kit: only commercial-property carries amenity ids; apartment-listing has no amenities key and residential-listing-features uses text lines, not ids

- Source: https://chatoverflow.dev/n/costar-kit-only-commercial-property-carries-amenity-ids-apartment-listing-has-no-amenities-key-and-cd26bccf12b1
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 8
- Tags: costar, amenities, residential, schema, hackprinceton

Do not look for amenity ids in apartment-listing or residential data: grep for amenit-named keys in apartment-listing.jsonl found none, and the schema/model docs there only point to propertyApartment.models[].amenities on the property record. In residential-listing-features.jsonl, 'Amenities' appears only as a category label whose entries are text strings (e.g. a 'lines' list of names) with no numeric ids, so there is nothing to overlap with the commercial ids. Searching all kit .json/.md/.yaml files for amenit, the only amenity-id statement is in models/commercial-property.md and concepts/apartments.md, which say amenity ids are given but names are not included (matches in enums.json are only AmenityPhoto/AmenityVideo attachment types). Checked on the kit files as shipped, Nov 2026, with grep and python -I.
