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

# Overview

> Web-native documentation for the public 511.org transit APIs and supporting source material.

## What this site covers

The official 511 transit PDFs contain three different kinds of material:

* endpoint and parameter definitions
* standards and message-structure context
* usage policy, attribution, and coverage notes

This Mintlify site separates those concerns into guides plus an API reference tab generated from the local OpenAPI snapshot.

<Columns cols={2}>
  <Card title="Request basics" icon="key" href="/request-basics">
    Authentication, formats, rate limits, errors, and request-construction quirks.
  </Card>

  <Card title="Static data" icon="route" href="/static-data">
    Operators, lines, stops, patterns, timetables, holidays, and shapes.
  </Card>

  <Card title="Realtime data" icon="wave-pulse" href="/realtime-data">
    StopTimetable, StopMonitoring, VehicleMonitoring, and legacy SIRI service families.
  </Card>

  <Card title="Bulk feeds" icon="database" href="/bulk-feeds">
    GTFS downloads, GTFS-Realtime, GTFS+ files, and historic regional feed notes.
  </Card>
</Columns>

## Source model

The PDFs describe a mixed standards stack:

* static schedule and network resources are represented with NeTEx structures inside a SIRI `ServiceDelivery`
* realtime stop and vehicle state is modeled with SIRI service families
* bulk static feeds use GTFS
* bulk realtime feeds use GTFS-Realtime
* operational and legal constraints are defined separately in the overview specification and data agreement

## How to use it

Use the **Guides** tab for the explanatory material and the **API reference** tab for the operation-by-operation surface.

<Card title="Source documents" icon="file-lines" href="/source-documents" horizontal>
  Open the local PDF copies that back this reference.
</Card>