GTFS Scorecard
← All agencies

Feed status · checked 2026-08-01

Beach Cities Transit

Based on the feed this agency publishes

Service mode Bus

68.1 / 100

unchanged since 2026-07-31

Review service end dateAccessibility gapsRealtime not yet published

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.3, validator 8.0.1.

Checked for changes 81 minutes ago; last changed 14 hours ago.

Measured 3 of 4 score categories from the agency's own feed.

How we measured this

Confidence in this measurement: medium.

  • Realtime quality was not measured this run. It does not count against the grade.
  • The feed was downloaded from the agency's own URL.

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

Top things to fix

Fix 01

Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team

202 of 202 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 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

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

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

Fix 03

Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool

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.

⏱ Two fields, set once in export settings.worth about +15 points in its category

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.

Feed evidence
202 of 202 stops don't say whether a wheelchair user can board there.
Next action
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
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. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide

    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. Self-check a feed before you publish.

  2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide

    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. Self-check a feed before you publish.

  3. Add feed_info.txt with feed_start_date and feed_end_date to your export. · Read the fix guide

    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. Self-check a feed before you publish.

Rider view: what this feed publishes

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

Schedule visibility
The feed states that service is published through 2099-12-31. This may be intentional or a placeholder; confirm current service with the transit operator.
Published accessibility data
Accessibility information is stated for 0% 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
Realtime-feed availability and live-arrival coverage are not known from this scorecard.

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.

Score by category

Correctness75.0 / 100

The MobilityData validator flagged 7 kinds of issue across 66 instances (0 error, 58 warning, 8 informational).

Freshness85.0 / 100

Service is published through 2099-12-31. It may be intentional, but confirm the end date before treating the feed as maintained.

Rider experience45.0 / 100

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

Accessibility0 / 100

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

1 accessibility depth signal

  • 198 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Aviation Blvd. / Century Blvd. (SB)", "Catalina Ave. / Torrance Blvd.", "Catalina Ave. / Garnet St.", and more).

    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 qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

Routes and stops

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

This feed has 202 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.

  • 109 (red)
  • 102 (blue)
Routes in Beach Cities Transit's feed
RouteTypeLine color
109Busred
102Busblue
List every stop
  • LAX Transit Center Bay 9
  • Aviation Blvd. / Century Blvd. (SB)
  • Redondo Beach Pier
  • Catalina Ave. / Torrance Blvd.
  • Catalina Ave. / Garnet St.
  • Catalina Ave. / Emerald St.
  • Catalina Ave. / Diamond St.
  • Diamond St. / PCH
  • Diamond St. / Sea Hawk Way
  • Diamond St. / Lucia Ave.
  • Prospect Ave. / Diamond St.
  • Beryl St. / Prospect Ave.
  • Beryl St. / Flagler Ln.
  • 190th St. / Beryl St.
  • Rindge Ln. / 190th St.
  • Rindge Ln. / Ripley Ave.
  • Rindge Ln. / Pullman Ln.
  • Rindge Ln. / Clark Ln.
  • Rindge Ln. / Grant Ave.
  • Rindge Ln. / Carnegie Ln.
  • Artesia Blvd. / Rindge Ln.
  • Artesia Blvd. / Mackay Ln.
  • Artesia Blvd. / Felton Ln.
  • Artesia Blvd. / Inglewood Ave.
  • Artesia Blvd. / Kingsdale Ave.
  • Hawthorne Blvd. / Artesia Blvd.
  • Hawthorne Blvd. / Market Place Drive
  • Hawthorne Blvd. / 182nd St.
  • Artesia Blvd. / Firmona Ave.
  • Artesia Blvd. / Inglewood Ave.
  • Artesia Blvd. / Felton Ln.
  • Artesia Blvd. / Mackay Ln.
  • Vail Ave. / Artesia Blvd.
  • Vail Ave. / Nelson Ave.
  • Vail Ave. / Voorhees Ave.
  • Vail Ave. / Gates Ave.
  • Vail Ave. / Robinson St.
  • Vail Ave. / May Ave.
  • Vail Ave. / Pinckard Ave.
  • Vail Ave. / Warfield Ave.
  • Redondo Beach Ave. / Manhattan Beach Blvd.
  • Redondo Beach Ave. / Santa Fe Ave.
  • Redondo Beach Ave. / Space Park Drive
  • Redondo Beach Green Line Station
  • Redondo Beach Ave. / Marine Ave.
  • Redondo Beach Ave. / Space Park Dr.
  • Redondo Beach Ave. / Manhattan Beach Blvd.
  • Vail Ave. / Warfield Ave.
  • Vail Ave. / Bataan Rd.
  • Vail Ave. / Ernest Ave.
  • Vail Ave. / Robinson St.
  • Vail Ave. / Gates Ave.
  • Vail Ave. / Voorhees Ave.
  • Vail Ave. / Nelson Ave.
  • Vail Ave. / Artesia Blvd.
  • Rindge Ln. / Artesia Blvd.
  • Rindge Ln. / Carnegie Ln.
  • Rindge Ln. / Grant Ave.
  • Rindge Ln. / Clark Ln.
  • Rindge Ln. / Pullman Ln.
  • Rindge Ln. / Ripley Ave.
  • Rindge Ln. / 190th St.
  • Beryl St. / 190th St.
  • Beryl St. / Flagler Ln.
  • Prospect Ave. / Beryl St.
  • Prospect Ave. / Diamond St.
  • Diamond St. / Lucia Ave.
  • Diamond St. / Helberta Ave.
  • Diamond St. / PCH
  • Catalina Ave. / Emerald St.
  • Catalina Ave. / Garnet St.
  • Palos Verdes Blvd / Via Valencia
  • Catalina Ave. / Elena Ave.
  • Catalina Ave. / Avenue I
  • Catalina Ave. / Avenue F
  • Catalina Ave. / Avenue C
  • Catalina Ave. / Knob Hill Ave.
  • Catalina Ave. / Topaz St.
  • Catalina Ave. / Sapphire St.
  • Catalina Ave. / Pearl St.
  • Catalina Ave. / Carnelian St.
  • Beryl St. / Harbor Dr.
  • Hermosa Ave. / Lyndon St.
  • Hermosa Ave. / 2nd St.
  • Hermosa Ave. / 6th St.
  • Hermosa Ave. / 8th St.
  • Hermosa Ave. / 10th St.
  • Hermosa Ave. / 16th St.
  • Hermosa Ave. / 19th St.
  • Hermosa Ave. / 22nd St.
  • Hermosa Ave. / 26th St.
  • Manhattan Ave. / Longfellow Ave.
  • Manhattan Ave. / 1st St.
  • Manhattan Ave. / 4th St.
  • Manhattan Ave. / 10th St.
  • Highland Ave. / 14th St.
  • Highland Ave. / 18th St.
  • Highland Ave. / Marine Ave.
  • Highland Ave. / 26th St.
  • Highland Ave. / 30th St.
  • Highland Ave. / 33rd St.
  • Highland Ave. / Rosecrans Ave.
  • Rosecrans Ave. / Alma Ave.
  • Rosecrans Ave. / Blanche Rd.
  • Rosecrans Ave. / Pacific Ave.
  • Rosecrans Ave. / Walnut Ave.
  • Rosecrans Ave. / Sepulveda Blvd.
  • Parkview Ave. / Village Dr.
  • Apollo St / Rosecrans Ave.
  • Douglas St. / Park Pl
  • Rosecrans Ave. / Nash St.
  • Rosecrans Ave. / Village Dr.
  • Park Pl. / Plaza El Segundo
  • Sepulveda Blvd. / El Segundo Blvd.
  • Grand Ave. / Sepulveda Blvd.
  • Grand Ave. / Kansas St.
  • Grand Ave. / Center St.
  • Grand Ave. / Lomita St.
  • Grand Ave. / Sheldon St.
  • Grand Ave. / Eucalyptus Dr.
  • Main St. / Holly Ave.
  • Main St./ Mariposa Ave
  • Main St. / Oak Ave.
  • Main St. / Walnut Ave.
  • Main St. / Imperial Ave.
  • Imperial Ave. / Eucalyptus Dr.
  • Imperial Ave. / Sheldon St.
  • Imperial Ave. / McCarthy Ct.
  • Imperial Ave. / Center St.
  • California St. / Imperial Ave.
  • Imperial Hwy. / California St.
  • Imperial Hwy. / Sepulveda Blvd.
  • Imperial Hwy. / Hughes Wy.
  • Imperial Hwy. / Nash St.
  • Imperial Hwy. / Douglas St.
  • Aviation Blvd. / Imperial Hwy.
  • Aviation Blvd. / 111th St.
  • Aviation Blvd. / 104th St.
  • Aviation Blvd. / Century Blvd.
  • Aviation Blvd. / 104th St.
  • Aviation Blvd. / 111th St.
  • Imperial Hwy. / Aviation Blvd.
  • Imperial Hwy. / Douglas St.
  • Imperial Hwy. / Nash St.
  • Imperial Hwy. / Hughes Wy.
  • Imperial Hwy. / Sepulveda Blvd.
  • Imperial Ave. / California St.
  • Imperial Ave. / Center St.
  • Imperial Ave. / McCarthy Ct.
  • Imperial Ave. / Sheldon St.
  • Imperial Ave. / Eucalyptus Dr.
  • Main St. / Imperial Ave.
  • Main St. / Walnut Ave.
  • Main St. / Oak Ave.
  • Main St / Mariposa Ave.
  • Main St. / Holly Ave.
  • Grand Ave. / Main St.
  • Grand Ave. / Eucalyptus Dr.
  • Grand Ave. / Sheldon St.
  • Grand Ave. / Lomita St.
  • Grand Ave. / Center St.
  • Grand Ave. / Kansas St.
  • Grand Ave. / Sepulveda Blvd.
  • Sepulveda Blvd. / El Segundo Blvd.
  • Park Pl. / Plaza El Segundo
  • Rosecrans Ave. /Sepulveda Blvd.
  • Rosecrans Ave. / Walnut Ave.
  • Rosecrans Ave. / Pacific Ave.
  • Rosecrans Ave. / Blanche Rd.
  • Highland Ave. / 33rd St.
  • Highland Ave. / 30th St
  • Highland Ave. / 26th St.
  • Highland Ave. / Marine Ave.
  • Highland Ave. / 18th St.
  • Highland Ave. / 14th St.
  • Manhattan Ave. / 10th St.
  • Manhattan Ave. / 4th St.
  • Manhattan Ave. / 1st St.
  • Manhattan Ave. / Longfellow Ave.
  • Manhattan Ave. / 27th St.
  • Hermosa Ave. / 25th St.
  • Hermosa Ave. / 22nd St.
  • Hermosa Ave. / 19th St.
  • Hermosa Ave. / 16th St.
  • Hermosa Ave. / 11th St.
  • Hermosa Ave. / 8th St.
  • Hermosa Ave. / 6th St.
  • Hermosa Ave. / 2nd St.
  • Harbor Dr. / Yacht Club Wy.
  • Beryl St. / Harbor Dr.
  • Catalina Ave. / Beryl St.
  • Catalina Ave. / Carnelian St.
  • Catalina Ave. / Diamond St.
  • Catalina Ave. / Torrance Blvd.
  • Catalina Ave. / Pearl St.
  • Catalina Ave. / Sapphire St.
  • Catalina Ave. / Topaz St.
  • Catalina Ave. / Knob Hill Ave.
  • Catalina Ave. / Avenue C
  • Catalina Ave. / Avenue F
  • Avenue I / Elena Ave.
  • Redondo Beach Transit Center

Over time

Overall score across the last 4 checks — unchanged since 2026-07-31.

2026-07-25: 68.12026-07-30: 68.12026-07-31: 68.12026-08-01: 68.1
Show the numbers
CheckScoreChange
2026-07-2568.1 first check
2026-07-3068.1 no change
2026-07-3168.1 no change
2026-08-0168.1 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

What changed in this feed

Overall grade and score held steady since 2026-07-31.

The feed file was re-published since 2026-07-31.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

Everything we checked

11 findings, ordered by severity.

Show every finding
  • Warning247 instances

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

    Even with accessible stops, riders need to know the bus 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 · See GTFS Schedule reference

  • Warning202 instances

    202 of 202 stops don't say whether a wheelchair user can board there.

    Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

    Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)

    Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning53 instances

    On some trips the stop distances run a little past the end of the route line.

    The stop and shape distance values don't quite line up, so any math that uses them can drift.

    Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)

    Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning2 instances

    Some route long names repeat the route's short name inside them.

    Apps show both names together, so riders see the number twice, like '5 5 Downtown'.

    Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)

    Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules

  • Warning1 instance

    feed_info.txt does not state when this feed starts and ends.

    Without stated dates, apps can't warn anyone before your data goes stale; it just disappears one day.

    Fix: Fill in feed_start_date and feed_end_date in feed_info.txt. (Two fields, likely set once in your export settings.)

    Finding code: missing_feed_info_date · See MobilityData GTFS Validator rules

  • Warning1 instance

    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 · See MobilityData GTFS Validator rules

  • Warning1 instance

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

    Riders may walk to a stop where no bus 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 · See MobilityData GTFS Validator rules

  • 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 · See MobilityData GTFS Validator rules

  • 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 · See GTFS Best Practices

  • Info5 instances

    Service extends far in the future (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: service_extends_far_in_the_future · See MobilityData GTFS Validator rules

  • Info3 instances

    The feed includes a file that is not part of the GTFS spec.

    Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.

    Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)

    Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules

NTD GTFS readiness Ready

Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Ready
The published window is current, but its service end date is unusually distant; confirm that date is intentional.
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 247 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

This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
The published window is current, but its service end date is unusually distant; confirm that date is intentional.
Accessible Not yet
States wheelchair access on 0% 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 202 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.

Clears the Google and Apple Maps four-week coverage bar. This feed clears the four-week coverage window, but its service end date is unusually distant. Confirm that date is intentional before treating it as evidence of ongoing maintenance. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.

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 75 / 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 85 / 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 45 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Not yet published
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.

Beach Cities Transit GTFS data quality grade: D

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/beach-cities-transit-1999/2026-08-01.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-08-01. 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.