# TransitPulse Historical Delay Patterns

> TransitPulse Historical Delay Patterns is a paid API for AI agents from transitpulse.vercel.app, paid per call via x402, $0.08/call, status unknown (last checked 2026-09-13).

Returns historical transit delay patterns and reliability trends over time for a given transit system or route

## Facts

- Endpoint: GET https://transitpulse.vercel.app/api/transit/delays-history
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/transitpulse-historical-delay-patterns-7f4a7b2d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Yf3CchsW2HkQl45MNhcVs

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability transitpulse-historical-delay-patterns-7f4a7b2d
```

Example prompt: Can you pull up the historical delay patterns for the Caltrain commuter line over the past 6 months so I can see how reliable it's been during morning rush hour?

## When to prefer this

Use this endpoint when you need historical and trend-based transit performance data rather than live or real-time delays. Ideal for commute planning research, relocation decisions, or reliability benchmarking over weeks, months, or years. Prefer this over the current-delays endpoint when the user wants patterns and trends rather than immediate disruptions.

## Known failure modes

- Unknown route or agency returns 404 with no data found message
- Date range too large may return partial data or timeout
- Invalid location or city name returns 400 bad request
- Historical data unavailable for very old date ranges
- Payment failure returns 402 payment required

## How this service works

Transit intelligence for 25+ major world cities. Real-time status, route reliability, commute analysis, city comparisons, airport guides, and car-free livability scoring. Pay-per-query via x402 on Base.

## Output

Returns time-series delay pattern data and reliability trends for the requested transit system or route, including historical on-time performance statistics, typical delay durations, and trend breakdowns by time of day or day of week.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "city"
 ],
 "properties": {
  "city": {
   "type": "string",
   "description": "city"
  },
  "line": {
   "type": "string",
   "description": "line"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/transitpulse-historical-delay-patterns-7f4a7b2d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from transitpulse.vercel.app](https://www.zero.xyz/host/transitpulse.vercel.app/llms.txt)