# Amtrak

**Canonical:** https://apis.io/providers/amtrak/  
**Website:** https://www.amtrak.com/  
**APIs profiled:** 1

Amtrak (the National Railroad Passenger Corporation) is the federally chartered operator of the United States national intercity passenger rail network, headquartered in Washington, D.C. It runs the Northeast Corridor including Acela, the state-supported corridors, the long-distance network, and the Amtrak Thruway Connecting Service bus network, and its published GTFS feed covers 61 routes, 646 stops, 2,948 trips and 20 operating agencies across the United States and into Canada. In the distribution chain Amtrak sits as a GDS-intermediated supplier of its own inventory: its content reaches third-party booking tools through Travelport Universal API, through Sabre, Apollo and Worldspan on the RailAgent channel, and through rail aggregators including SilverRail, Travelfusion and RailKey Technologies, alongside its own amtrak.com, mobile app and call centre. Its API posture is honestly stated as one open-standard data feed and nothing else. The only machine-readable contract Amtrak publishes is a static GTFS schedule archive at content.amtrak.com, which is completely ungated - no key, no registration, no click-through - but which Amtrak advertises nowhere: there is no developer portal, no documentation page, no OpenAPI, no AsyncAPI, no GraphQL, and no published terms of use for the feed. Everything transactional is closed. The developer., docs., data. and partners. subdomains of amtrak.com do not resolve, developers.amtrak.com resolves only to a Microsoft Entra application proxy, api.amtrak.com answers 401 on every path from Akamai NetStorage, and www.amtrak.com returns 403 to every non-browser client, so no first-party terms of service could be retrieved programmatically. A developer who wants shopping, booking, payment, ticketing or servicing does not sign up; they are accredited through Travelport or an aggregator, complete an Amtrak test-case worksheet, pass a three-week UAT, and commit to supporting Amtrak refund fees and eVoucher issuance before production credentials are issued.

## Kin Score — 21.2 / 100 (emerging)

Scored 2026-08-20 under rubric 0.12.0. Trend: flat (+0.0 from 21.2).

| Facet | Score |
|---|---|
| Discoverability | 75.9 |
| Contract Quality | 8.5 |
| Governance | 4.5 |
| Contract Governance | 4.5 |
| Operational Transparency | 2.6 |
| Developer Ergonomics | 13.7 |
| Commercial Clarity | 21.1 |
| Access Clarity | 21.1 |

Regulatory layer — **Government & Public Sector**: 46.3 (matched via tags).

## Agent readiness — 9.6 (agent-aware)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | yes |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | derived |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## APIs (1)

- **Amtrak GTFS Schedule Feed** — Amtrak's complete national timetable published as a static General Transit Feed Specification archive, served from content.amtrak.com with no registration, no API key, no click-...

## Security (2)

- **Amtrak Authentication** — none · 1 scheme
- **Amtrak Domain Security** — TLSv1.3 · HSTS · DNSSEC · DMARC

## Tags

Travel, United States, Rail, Passenger Rail, Transit, GTFS, Open Data, Booking, Distribution, GDS, Corporate Travel, Travel Agents, Loyalty

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/amtrak/). Scores are computed from the provider's own public artifacts under a published rubric.