> ## Documentation Index
> Fetch the complete documentation index at: https://qwady.wiki/llms.txt
> Use this file to discover all available pages before exploring further.

# Transit Lines

> Transit line filtering is not currently available

`transitLines` is not a current Borough search parameter.

This page is kept so older references resolve cleanly, but line-by-line transit filtering is not part of the live contract today.

## What to use instead

* `minTransitScore` for building-level transit accessibility filtering
* `areas` for neighborhood and borough scoping
* building score detail endpoints when you need the current transit score itself

## Current status

These requests are common, but they are not current Borough filters:

* `transitLines`
* `prewar`
* view-style amenity enums such as `CITY_VIEW` or `WATER_VIEW`

## Related: transit score

Instead of line filtering, you can filter by transit accessibility score:

```bash theme={null}
# Listings with excellent transit access
curl "https://borough.qwady.app/v1/search/rentals?minTransitScore=80"
```

Transit scores (0-100) are available on building detail responses via `GET /v1/building/{id}/scores`. The score is computed from MTA GTFS stop data based on:

* **Proximity** (50 points): distance to the nearest transit stop, whether subway, bus, commuter rail (LIRR/Metro-North), or ferry
* **Density** (50 points): number of stops within 400m radius

See [Building Scores](/borough/enrichment) for details on how scores are computed.
