mobilitydatabase.org valid

Mobility Database

The Mobility Database is an open catalog of over 6000 public transit feeds

For agents: Open catalog of over 6,000 public transit feeds with search by country, data type and status, plus a GTFS feature tracker and sitemap for feed pages.

gtfspublic transit feedstransit dataopen data catalogmobility data

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T18:59:46.130Z. Cached copy · Source on mobilitydatabase.org

# Mobility Database

> The Mobility Database is an open catalog of over 6000 public transit feeds
> from more than 100 countries, maintained by MobilityData, a non-profit that
> maintains and develops the GTFS, GTFS-Realtime and GBFS data formats. Every feed entry
> records its provider, location, licence, download history and validation
> results, and the whole catalog is queryable through a free REST API.

## Feed pages: where the substance is

The home page is a landing page. Almost all of this site's content lives on
the ~7000 individual feed pages, one per feed, each fully server-rendered:

    https://mobilitydatabase.org/feeds/{data_type}/{feed_id}

`data_type` is `gtfs` (GTFS Schedule), `gtfs_rt` (GTFS-Realtime) or `gbfs`.
Examples:

- https://mobilitydatabase.org/feeds/gtfs/mdb-3520
- https://mobilitydatabase.org/feeds/gtfs_rt/mdb-1366
- https://mobilitydatabase.org/feeds/gbfs/gbfs-27

Feed ids identify a *feed*, not an agency, and they are not shared across
data types: `/feeds/gtfs/mdb-3520` and `/feeds/gtfs_rt/mdb-3520` are unrelated
feeds, and the second may not exist. Treat ids as opaque strings. To find a
feed's id, search https://mobilitydatabase.org/feeds or query the API — do not
construct ids.

Each feed page states: the provider and whether the feed is official, the
current validation status with a link to the full report, the latest dataset
download, the agency and its timezone, the countries and municipalities
covered, route counts by mode, the producer's own feed URL, the service date
range, which optional GTFS features the feed uses, and the dataset history.
Datasets are refetched once a day at midnight UTC.

Two sub-pages exist per feed:

- `/feeds/{data_type}/{feed_id}/map` — routes and stops on an interactive map

**Every feed page carries a schema.org `Dataset` in JSON-LD** with the feed's
name, description, identifier, creator, licence, `distribution.contentUrl`
(the dataset archive), `dateModified`, `spatialCoverage` as a geo bounding
box, and `variableMeasured`. That block is the authoritative machine-readable
record of a feed — prefer it over scraping the rendered page.

Every feed page is listed in https://mobilitydatabase.org/sitemap.xml.

## What the catalog contains

- **GTFS Schedule** feeds: routes, stops, trips and timetables published by
  transit agencies, with a validation report for each dataset version.
- **GTFS-Realtime** feeds: trip updates, vehicle positions and service alerts.
- **GBFS** feeds: shared bike, scooter and other micromobility systems,
  including station status and vehicle availability.

Feeds are contributed by transit agencies, producers and the community, and
reviewed before they are published. Access to the catalog and the API is free.

## Key pages
…

Related sites

Find similar publishers by meaning →

Other listed sites in Data and analytics. See the whole category →

Machine-readable: GET /v1/resolve?q=mobilitydatabase.org · GET /v1/domain/mobilitydatabase.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for mobilitydatabase.org:
1. POST https://agentwebmap.com/v1/sites/mobilitydatabase.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://mobilitydatabase.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/mobilitydatabase.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/mobilitydatabase.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.