Feed status · checked 2026-11-21

Long Island Rail Road

Based on the feed source on file; publisher ownership is not verified

Service mode Rail

65.5 / 100

unchanged since 2026-11-20

Cataloged in New York.

Feed expiredAccessibility gaps

The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works

Top things to fix

Fix 01

Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.Likely your export tool

Service data ended 13 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the transit vehicles are still running. Riders are told the service does not exist.

This one is about the feed as a whole, so there is no share of it to count.

⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category

Fix 02

Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool

2291 of 2291 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.

Fixing this covers all 2,291 trips in the feed.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 03

Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

This one is about the feed as a whole, so there is no share of it to count.

⏱ A small file for most flat-fare systems.worth about +15 points in its category

Riders and need behind these fixes

  • This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
  • New York as a whole measures moderate on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-11-02.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Finding
Fix 01 in Top things to fix: its feed evidence and the requested change.
Recheck
Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

  1. Fix 01 · Read the fix guide for scorecard_feed_expired

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.

  2. Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_unknown

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.

  3. Fix 03 · Read the fix guide for scorecard_no_fare_data

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility
The feed's last published service date was 13 days ago.
Published accessibility data
Accessibility information is stated for 100% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
No fare information is published in the feed.
Realtime information
One or more realtime feeds were reachable; live-arrival coverage is not known.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Send your vendor a fix request

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

Send the agency a note

Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.

About this feed

Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.

Long Island Rail Road’s published feed lists 13 rail routes, 2,291 scheduled trips and 127 stops. It publishes realtime service alerts; when we checked, it answered. The published file last changed on 2026-10-16.

Score by category

Correctness85.5 / 100

The MobilityData validator flagged 4 kinds of issue across 19 instances (0 error, 17 warning, 2 informational).

Freshness0.0 / 100

Service data ended 13 day(s) ago. Trip planners have likely already dropped this feed.

Rider experience62.5 / 100

100% of stops state wheelchair accessibility (96% marked accessible, 4% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility62.5 / 100

100% of stops state accessibility (96% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Babylon Branch, Oyster Bay Branch, Long Beach Branch).

    Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.

  • 2 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("St. Albans", "St. James").

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.

Realtime quality100.0 / 100

Sampled 3 times: 1 of 1 configured feed healthy.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 127 stops.

Skip to route and stop data

The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • Babylon Branch (green)
  • Port Jefferson Branch (teal)
  • City Terminal Zone (green)
  • Greenport Service (purple)
  • Hempstead Branch (orange)
  • Oyster Bay Branch (green)
  • Ronkonkoma Branch (purple)
  • Montauk Branch (teal)
  • Long Beach Branch (orange)
  • Far Rockaway Branch (brown)
  • West Hempstead Branch (teal)
  • Port Washington Branch (red)
Routes in Long Island Rail Road's feed
RouteTypeLine color
Babylon BranchRailgreen
Port Jefferson BranchRailteal
Belmont ParkRailpurple (no shape in feed)
City Terminal ZoneRailgreen
Greenport ServiceRailpurple
Hempstead BranchRailorange
Oyster Bay BranchRailgreen
Ronkonkoma BranchRailpurple
Montauk BranchRailteal
Long Beach BranchRailorange
Far Rockaway BranchRailbrown
West Hempstead BranchRailteal
Port Washington BranchRailred
List every stop
  • Albertson
  • Islip
  • Inwood
  • Jamaica
  • Kew Gardens
  • Broadway
  • Kings Park
  • Long Beach
  • Lawrence
  • Lindenhurst
  • Long Island City
  • Locust Manor
  • Little Neck
  • Laurelton
  • Locust Valley
  • Lakeview
  • Lynbrook
  • Mattituck
  • Merillon Avenue
  • Medford
  • Bridgehampton
  • Murray Hill
  • Manhasset
  • Mineola
  • Massapequa Park
  • Massapequa
  • Stony Brook
  • Mastic-Shirley
  • Montauk
  • Malverne
  • Nostrand Avenue
  • Nassau Boulevard
  • New Hyde Park
  • Northport
  • Oyster Bay
  • Oceanside
  • Oakdale
  • Bellmore
  • Plandome
  • Patchogue
  • Port Jefferson
  • Pinelawn
  • Port Washington
  • Queens Village
  • Riverhead
  • Ronkonkoma
  • Rosedale
  • Roslyn
  • Rockville Centre
  • St. Albans
  • Sea Cliff
  • Seaford
  • Southold
  • Southampton
  • St. James
  • Stewart Manor
  • Speonk
  • Mets-Willets Point
  • Auburndale
  • Bethpage
  • Smithtown
  • Sayville
  • Syosset
  • Bellport
  • Valley Stream
  • Westbury
  • Woodside
  • Wantagh
  • West Hempstead
  • Woodmere
  • Westwood
  • Wyandanch
  • Yaphank
  • Baldwin
  • Merrick
  • Bellerose
  • Westhampton
  • Penn Station
  • Belmont Park
  • Atlantic Terminal
  • Bayside
  • Bay Shore
  • Babylon
  • Brentwood
  • Centre Avenue
  • Cedarhurst
  • Central Islip
  • Grand Central
  • Elmont-UBS Arena
  • Country Life Press
  • Copiague
  • Carle Place
  • Amagansett
  • Cold Spring Harbor
  • Douglaston
  • Deer Park
  • East Hampton
  • East New York
  • East Rockaway
  • East Williston
  • Forest Hills
  • Flushing Main Street
  • Farmingdale
  • Floral Park
  • Freeport
  • Far Rockaway
  • Gibson
  • Glen Cove
  • Garden City
  • Glen Head
  • Great Neck
  • Greenport
  • Great River
  • Glen Street
  • Greenvale
  • Greenlawn
  • Amityville
  • Hampton Bays
  • Hempstead
  • Hempstead Gardens
  • Hillside Facility
  • Hollis
  • Hunterspoint Avenue
  • Huntington
  • Hicksville
  • Hewlett
  • Island Park

Over time

Overall score across the last 48 checks — unchanged since 2026-11-20.

2026-10-02: 74.92026-10-03: 74.52026-10-04: 74.22026-10-05: 73.92026-10-06: 73.52026-10-07: 73.22026-10-08: 72.92026-10-09: 72.52026-10-10: 72.22026-10-11: 71.92026-10-12: 71.52026-10-13: 71.22026-10-14: 70.92026-10-15: 70.52026-10-16: 70.22026-10-17: 69.92026-10-18: 69.52026-10-19: 69.22026-10-20: 68.92026-10-21: 68.52026-10-22: 68.22026-10-23: 67.92026-10-24: 67.52026-10-25: 67.22026-10-26: 66.92026-10-27: 66.52026-10-28: 66.22026-10-29: 65.92026-10-30: 65.52026-10-31: 65.52026-11-01: 65.52026-11-02: 65.52026-11-04: 65.52026-11-05: 65.52026-11-06: 65.52026-11-09: 65.52026-11-10: 65.52026-11-11: 65.52026-11-12: 65.52026-11-13: 65.52026-11-14: 65.52026-11-15: 65.52026-11-16: 65.52026-11-17: 65.52026-11-18: 65.52026-11-19: 65.52026-11-20: 65.52026-11-21: 65.5
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-10-0274.9 first check
2026-10-0374.5 down 0.4
2026-10-0474.2 down 0.3
2026-10-0573.9 down 0.3
2026-10-0673.5 down 0.4
2026-10-0773.2 down 0.3
2026-10-0872.9 down 0.3
2026-10-0972.5 down 0.4
2026-10-1072.2 down 0.3
2026-10-1171.9 down 0.3
2026-10-1271.5 down 0.4
2026-10-1371.2 down 0.3
2026-10-1470.9 down 0.3
2026-10-1570.5 down 0.4
2026-10-1670.2 down 0.3
2026-10-1769.9 down 0.3
2026-10-1869.5 down 0.4
2026-10-1969.2 down 0.3
2026-10-2068.9 down 0.3
2026-10-2168.5 down 0.4
2026-10-2268.2 down 0.3
2026-10-2367.9 down 0.3
2026-10-2467.5 down 0.4
2026-10-2567.2 down 0.3
2026-10-2666.9 down 0.3
2026-10-2766.5 down 0.4
2026-10-2866.2 down 0.3
2026-10-2965.9 down 0.3
2026-10-3065.5 down 0.4
2026-10-3165.5 no change
2026-11-0165.5 no change
2026-11-0265.5 no change
2026-11-0465.5 no change
2026-11-0565.5 no change
2026-11-0665.5 no change
2026-11-0965.5 no change
2026-11-1065.5 no change
2026-11-1165.5 no change
2026-11-1265.5 no change
2026-11-1365.5 no change
2026-11-1465.5 no change
2026-11-1565.5 no change
2026-11-1665.5 no change
2026-11-1765.5 no change
2026-11-1865.5 no change
2026-11-1965.5 no change
2026-11-2065.5 no change
2026-11-2165.5 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change
  • Realtime quality no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

Feed history by published file
CheckedPublished fileService dates throughGrade at the time
2026-10-16 to 2026-11-21 (34 checks)18a29430ef6a2026-11-08Current rubric: see the trend above
2026-10-14 to 2026-10-15 (2 checks)7d7c3a1bff8d2026-11-08Current rubric: see the trend above
2026-10-13a329f4eb68942026-11-08Current rubric: see the trend above
2026-10-09 to 2026-10-12 (4 checks)06aaaccc4b7f2026-11-08Current rubric: see the trend above
2026-10-088779b9d752f12026-11-08Current rubric: see the trend above
2026-10-06 to 2026-10-07 (2 checks)aaf2e3427fd22026-11-08Current rubric: see the trend above
2026-10-056701d2cef8552026-11-08Current rubric: see the trend above
2026-10-02 to 2026-10-04 (3 checks)2f7d6a2fc12a2026-11-08Current rubric: see the trend above
2026-09-28 to 2026-10-01 (4 checks)2f7d6a2fc12a2026-11-08C, 75.2 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-09-24 to 2026-09-27 (4 checks)0fa41dfe7d992026-11-08C, 76.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-09-21 to 2026-09-23 (3 checks)9ba1290ac81b2026-11-08C, 77.9 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-09-18 to 2026-09-20 (3 checks)c825c5050b732026-11-08C, 78.9 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade

Showing the 12 most recent of 44 periods.

What changed over time

On 2026-10-02 this feed started at grade C. On 2026-10-17 the grade moved from C to D. On 2026-10-09 feed entered the expiry window (30 days of service left). On 2026-11-09 feed expired. As of 2026-11-21 it holds grade D.

A plain-language history of this feed, newest first.

  • 2026-11-09 Feed expired.
  • 2026-10-17 Grade went C to D.
  • 2026-10-09 Feed entered the expiry window (30 days of service left).

Everything we checked

9 findings, ordered by severity.

Show every finding
  • Error1 instance

    Service data ended 13 day(s) ago.

    When the calendar runs out, trip planners stop showing this agency even though the transit vehicles are still running. Riders are told the service does not exist.

    Fix: Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)

    Finding code: scorecard_feed_expired · Read the fix guide for scorecard_feed_expired · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Warning2291 instances

    2291 of 2291 trips don't say whether the vehicle is wheelchair accessible.

    Even with accessible stops, riders need to know the transit vehicle itself can take them.

    Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)

    Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

  • Warning15 instances

    Some files leave out fields that GTFS asks for but does not require.

    Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.

    Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)

    Finding code: missing_recommended_field · Read the fix guide for missing_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    feed_info.txt lists no contact email and no contact URL.

    Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

    Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)

    Finding code: missing_feed_contact_email_and_url · Read the fix guide for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    Some stops exist in the feed but no trip ever stops at them.

    Riders may walk to a stop where no transit vehicle is scheduled to arrive.

    Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

    Finding code: stop_without_stop_time · Read the fix guide for stop_without_stop_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    feed_info.txt is missing its start/end dates

    Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

    Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)

    Finding code: scorecard_missing_feed_info_dates · Read the fix guide for scorecard_missing_feed_info_dates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    The feed contains no fare information.

    Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

    Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)

    Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Info2 instances

    Some files contain columns that are not part of the GTFS spec.

    Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

    Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

    Finding code: unknown_column · Read the fix guide for unknown_column · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

How we measured this

Checked for changes 13 days ago; last changed 14 days ago.

The latest run did not download this feed: the host's robots.txt could not be read, and this scorecard does not request a feed until it can. The grade shown was measured on 2026-11-21.

Measured 4 of 4 score categories from the feed URL on file (publisher not verified).

How we measured this

Confidence in this measurement: high.

  • All four score categories were measured this run.
  • Realtime was sampled in one bounded window of 3 snapshots.
  • The feed was downloaded from the configured feed URL. Publisher ownership of that URL is not verified.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.4, validator 8.0.1.

NTD GTFS readiness Not ready

Resolve this before you certify on the D-10. Service data expired 13 days ago, so FTA would find the link out of date.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Not ready
Service data expired 13 days ago, so FTA would find the link out of date.
agency_id provided Ready
agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
agency_id equals your NTD ID (optional) Not checked yet
This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
shapes.txt covers your trips Ready
All 2291 trips have a shape in shapes.txt.

In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.

A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.

Conformance mark Not yet

Two requirements remain for this feed to earn the conformance mark. Service data expired 13 days ago. States wheelchair access on 100% of stops and 0% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Not yet
Service data expired 13 days ago.
Accessible Not yet
States wheelchair access on 100% of stops and 0% of trips; the mark needs 90% of each.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

  • 1 of 127 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Realtime reliability

The realtime feed responded on 100.0% of 200 checks in the 25 days to 2026-10-20, with lag not reported by the feed.

Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment. The window ends at the newest observation, which is not always today: if the monitor stops, this window stops with it.

Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.

How this agency maps to the standards

The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.

Correctness 86 / 100
GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
Freshness 0 / 100
GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
Rider experience 62 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality 100 / 100
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Part of the New York portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in New York

Other scorecards in New York, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Long Island Rail Road: GTFS feed quality grade D, 65.5 of 100, checked 2026-11-21. GTFS Scorecard.

Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.

Cite this record

This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/metropolitan-transit-authority-mta/2026-11-21.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-11-21. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.